Using Supply Calculations to Understand Planning Levels

We know what we have, and we know what we want. Now we just need a clear path to get from one to the other. We need a configuration path to get from PERPRODCUST to PERLOCRES. To plan correctly, we need to start at the end.

We can plan backwards from the end, the Capacity Overload Alert. What do we need to know to determine if there is an overload? We need to know how much capacity we have (Capacity Supply) and how much capacity we need (Capacity Demand). If the Capacity Demand is larger than the Capacity Supply then we have an overload in that period.

The next question is, where does Capacity Supply come from? It is stored in the work center on the ECC/SAP HANA side; therefore, we can say that it comes from master data. There should be an interface that will load that data into SAP IBP. The other important question is what is the planning level of that data? It will have the planning level PERLOCRES the same as the Capacity Overload Alert.

Where does Capacity Demand come from? It is calculated from the demand at the location and the capacity consumption. We also need to identify the planning levels of these. Since each product can consume a different amount of time on the resource the planning level of capacity consumption must be PERPRODLOCRES. The Demand by Location is the total demand that is to be produced on the resource regardless from which customer it originated. That means that the planning level of Demand by Location is PERPRODLOC summed across Customers.

The next step is to determine where Capacity Consumption comes from. In ECC/SAP HANA it is stored in the routing as time on the resource so it also comes from master data.

Where does Demand by Location come from? It is calculated as the percentage of Consensus Demand that this location will provide. Therefore, we need to include this calculation as well. The final step is to take the Consensus Demand Qty* Sourcing Ratio to determine the portion of demand supplied by this location. We use a sourcing ratio here just in case we have multiple sources, but in the case of a single source, the ratio could be 1.

Once we get the path drawn, it becomes obvious which key figures are needed, as they are listed on the path. It is also obvious which planning levels are needed. Master Data Types that are needed for this calculation were loaded at the beginning of the course.

Finally, since both Capacity Supply and Capacity Consumption are rather constant over time they become ideal candidates for attributes defined as key figures and we will create compound master data types to handle this. As attributes are defined as key figures, we can choose to handle them as master data and load one value for each location resource combination. Once we get the CI-DS data load setup and load a value for each period, this will be replicated to every period or we can choose to handle them as key figures. For testing, managing them as master data is preferable, and it involves much less work to create a data file.