SNP Disaggregation 

Use

You can execute this function within aggregated planning in Supply Network Planning (SNP). It disaggregates the results of heuristic- or optimization-based planning that you have performed at header location product level of a location product hierarchy, to the level of the individual sub products.

Features

SNP disaggregation disaggregates the planning result saved in the distribution receipt (planned) , distribution demand (planned) , Production (planned) or Dependent Demand key figures, to the individual sub products. The aggregated value for the header location product is displayed in the Aggregated Distribution Receipt or Aggregated Distribution Demand (Planned) key figures, and in the Aggregated Production (Planned) or Aggregated Dependent Demand key figures after disaggregation in interactive Supply Network Planning. The disaggregated value for the individual sub products is again displayed in the non-aggregated key figures, such as Distribution Receipt (Planned) and so on (when you select the individual sub product).

If you display the detail view of the aggregated key figures with a right mouse click, you will see a list of orders that the system created for the sub products of the header product. You can change this order data.

Disaggregation Methods

You can choose between two disaggregation methods or combine both methods.

·        Disaggregation According to Demands

Values are disaggregated from header product level to sub product level according to fair share distribution or push distribution principles that are also used by deployment. With fair share distribution, if demand exceeds supply, the system distributes the supply evenly over the individual sub products according to their demand. With push distribution, the procedure is similar but is used when supply exceeds demand.

SNP disaggregation determines disaggregation demand; in other words, the demand of the sub products, based on the NETDM auxiliary key figure or a user-defined auxiliary key figure (see Prerequisites for Aggregated Planning). The system calculates the net demand saved in the NETDM key figure at sub product level using the Net Demand (Disaggregation) macro, while taking the stock level changes into account. It ignores the demand from earlier periods (shown in the Supply Shortage key figure) and only considers the demand starting with the period containing the value to be disaggregated.

·        Disaggregation According to Quota Arrangements

Values are disaggregated from header product level to sub product level according to quota arrangements that you have defined for the sub products. You define these quota arrangements either time-independent in the master data of the product hierarchy or location product hierarchy, or time-dependent in a time series key figure. You specify the time series key figure in the disaggregation settings. You can either use an existing (not yet used) key figure of your planning area, or create a new key figure and assign it to your planning area and planning book. For more information, see Planning Area Administration.

·        Method Combination

Select the Disaggregation According to Quota Arrangements method and specify a horizon. The system performs disaggregation according to demands for orders within the horizon, and disaggregation according to quota arrangements for orders outside the horizon. This is useful, for example, if you have more exact demand information for a timeframe in the near future than for a later timeframe.

Disaggregation Modes

You can specify how the system processes the orders within a certain period (bucket) during disaggregation. The following disaggregation modes are available:

·        Period-Based (Bucket-Oriented) Disaggregation

Within one period, the system adds up all order quantities from orders at header product level that have the same source of supply, and disaggregates this total quantity to the sub products.  In so doing, the system applies the minimum lot sizes and the rounding values to the total quantity of one period.

·        Order-Based Disaggregation

The system disaggregates each order that exists at header product level to the sub products. It applies the minimum lot sizes and rounding values to the order quantity of each individual order.

When creating orders at sub product level, the order-based disaggregation mode creates a unique reference to the original order at header product level. This reference is represented by the order group number. You can see this number in the detailed display for the orders in interactive planning and use it to understand the correlation between the orders. For this you must have specified in Customizing for SNP that you want the system to use the order group (see Prerequisites for Aggregated Planning).

You can change the order group number for an order and thus assign the order to another order group. Data such as the fixing indicator and availability date/time are automatically adjusted to the data of the order group.

Scope of Planning

You can execute location or network disaggregation.

·        Network disaggregation: The value stored at header product level is automatically disaggregated at all locations in the distribution network where the chosen header product and sub products exist.

·        Location disaggregation: The value stored at header product level is only disaggregated at the selected locations for the selected products.

If you have determined the low-level codes before executing network or location disaggregation, the system automatically processes the locations in a specific sequence, so that it can correctly determine the disaggregation demand. The system begins with the final location of the supply chain where the demand exists at sub product level (a distribution center, for example).

Disaggregation Time Frame

You can define a special disaggregation horizon, meaning a timeframe in which the system reads the aggregated orders at header product level and creates the disaggregated orders at sub product level. The horizon commences on the start date for disaggregation.

Like the SNP heuristic and SNP optimizer, SNP disaggregation also considers the following SNP horizons of the header location product:

·        SNP production horizon

·        Extended SNP Production Horizon

·        SNP stock transfer horizon

For this reason, you should always run SNP disaggregation on the same day as the SNP (heuristic or optimizer) planning run. Otherwise, the receipts generated in the planning run could be moved to horizons in which the system can no longer disaggregate them. An exception is if you enter (or use a user exit to specify) a start date for disaggregation. In this instance, the horizons are not taken into account during disaggregation.

Delete Orders at Header Level

You can configure how you want the system proceed after disaggregation with the orders at header location product level. This refers to the values saved in the Distribution Receipt or Distribution Demand (planned) and Production (planned) or Dependent Demand key figures. You can specify that the system deletes, reduces, or does not change the orders. Note the following:

·        Reduce: The system reduces the orders at header product level by the total of disaggregated orders at sub product level in the respective period. There might be a remainder if you have defined different rounding values or minimum lot sizes for the sub products and header product in the product master data (see Master Data Setup for Aggregated Planning). This remainder is then displayed in the Distribution Receipt or Distribution Demand (Planned) and Production (Planned) or Dependent Demand key figures in interactive planning.

·        Do not change: The values saved in the Distribution Receipt or Distribution Demand (planned) and Production (planned) or Dependent Demand key figures are retained. The system takes these values into account when it calculates the total receipt/demand, thus calculating them twice. This can cause problems when the data is processed further; in other locations, for example.

The system deletes or reduces the orders in the disaggregation horizon. You should mainly use the option of retaining the orders for simulation purposes.

Log

If you run SNP disaggregation in the background, the system generates an application log. It contains, among other things, detailed information about the disaggregated planned orders and stock transfers. For more information, see Application Logs.

Activities

You can execute SNP disaggregation both in interactive SNP and as a background job. To execute it in interactive planning, select Location Disaggregation Network Disaggregationin planning book 9ASNPAGGR and data view SNPAGGR(1). To make the settings, choose  with quick info Init.Screen for (Dis-)Aggr.

To execute it in the background, from the SAP Easy Access screen, choose Supply Network Planning → Planning → Supply Network Planning in the Background → SNP Disaggregation.