Aggregated Safety Stock Planning 

Use

In aggregated planning in Supply Network Planning (SNP), you can execute safety stock planning on the basis of aggregated data as a preliminary step to actual SNP planning. Since safety stock planning occurs at header location product level, all necessary data such as master, demand, and historical data must also be available at this level. You can have the system automatically aggregate some of this data from sublevel to header level, or you can provide the data at header level yourself.

The following describes which data you can have the system aggregate and which settings you need to make. For more information about safety stock planning in SNP, see Safety Stock Planning.

Prerequisites

·        You have made the general settings required for executing safety stock planning in SNP. For more information, see Standard Safety Stock Planning and Extended Safety Stock Planning.

·        Since safety stock planning occurs at location product level, you have created a location product hierarchy. For more information, see Master Data Setup for Aggregated Planning.

·        You use the standard planning book 9ASNPAGGR intended for aggregated planning, or your own planning book based on it.

If you want to use other safety stock methods in addition to the standard safety stock methods SB, SZ, and SM, you have added two liveCache time series key figures for the planned safety stock and the safety days’ supply to the planning book. For more information, see SAP Note 858794.

Features

Standard Safety Stock Planning

For standard safety stock planning at aggregated level, the system a can aggregate master data and demand data as follows:

·        Safety stock and safety days’ supply: You define this data either time-independent in the location product master data or time-dependent in interactive SNP planning.

In the master data of the location product hierarchy, you can define at header location product level that the system automatically aggregates the data from the sub location product level to the header location product level (Agg. Proc.SDS and Agg. Proc.SFT fields). Various procedures are available for aggregation, such as average and total.

So that the time-dependent data can be automatically aggregated, it has to be saved in time series key figures in liveCache. Aggregation is only temporary, meaning the aggregated data is not saved permanently.

The aggregated data is only available for the SNP planning procedures SNP heuristic and SNP optimizer, and for the SNP mode of Capable-to-Match planning (CTM). Production planning and detailed scheduling (PP/DS) and the PP/DS mode of CTM planning cannot access the data. For these applications, you must provide the data at header location product level manually.

·        Demand data: The demand data is used by the safety stock methods based on the safety days’ supply (SZ, SM, MZ, and MM). You provide this data in an order key figure in liveCache.

In the planning area on the Key Figures tab page, you can specify that the data saved in the key figure is automatically aggregated from the sub location product level to the header location product level. For this, specify either value 1 or 2 in the Aggregation field.

·        Safety stock methods (SFT methods): The system cannot automatically aggregate this master data, meaning you must define it for the header location product.

If you want to plan at both aggregated level and detailed level in an SNP planning process, you should define the SFT methods identically at both levels. If you only want to plan at aggregated level, it is not necessary to do so, since the system then only considers the data of the header location product.

Extended Safety Stock Planning

For extended safety stock planning at aggregated level, the system can aggregate demand forecast data and historical data as follows:

·        Demand forecast data: You provide the demand forecast data in an order key figure in liveCache.

In the planning area on the Key Figures tab page, you can specify that the data saved in the key figure is automatically aggregated from the sub location product level to the header location product level. For this, specify either value 1 or 2 in the Aggregation field.

·        Historical data: You provide the historical demand data and the historical replenishment lead time (RLT) data in liveCache in time series key figures.

In the master data of the location product hierarchy, you can define at header location product level that the system automatically aggregates the data from the sub location product level to the header location product level (Hist.RLT Data and Hist.Dmnd Data fields).

Aggregation occurs by adding the demand forecasts / actual demands period by period or by finding the average of the RLT forecasts / actual RLT period by period.

·        Location product master data: The system cannot automatically aggregate the master data delivery service level, target days’ supply, forecast error, or SFT methods. This means that you have to define them for the header location product.

Activities

...

       1.      You execute standard or extended safety stock planning as described in Standard Safety Stock Planning or Extended Safety Stock Planning. The system saves the results for standard safety stock planning in an auxiliary key figure (for example, SAFTY) and, for extended safety stock planning, in a liveCache time series key figure (for example, 9ASAFETY).

       2.      You then execute an SNP, CTM, or PP/DS planning run at aggregated level. The system uses the safety stock data it calculated or that you provided as a basis for planning and creates planned orders and stock transfers accordingly for covering the planned safety stock requirement.

For more information, see Aggregated Planning.

       3.      You execute SNP disaggregation in which the orders are disaggregated from header location product level back to sub location product level. For more information, see SNP Disaggregation.

It is not possible to disaggregate the calculated safety stock values directly. However, this is not necessary because the safety stock planning results only enter SNP planning at header level as entry information.