Planning Horizons

PP/DS Horizon in Calendar Days

Use

You specify a location-product-specific PP/DS horizon here.

If you do not enter any value for the PP/DS horizon or if you enter the duration '0', the system automatically uses the SNP production horizon as the PP/DS horizon. Therefore, the PP/DS horizon is as long as the SNP production horizon. This means the planning intervals for SNP and PP/DS are sequenced with no gaps or overlaps.

If the SNP production horizon also has a duration of 0, the system uses the PP/DS horizon from the planning version.

Notes

• You can use the PP/DS firming horizon within the PP/DS horizon to firm (short-term) planning for planning with procurement planning heuristics.

• Supply Network Planning (SNP) is permitted to plan outside of the SNP production horizon only. If the SNP production horizon is smaller than the PP/DS horizon, the planning horizons of SNP and PP/DS overlap. SNP and PP/DS can both use this overlapping period for planning.

SNP Production Horizon

Horizon in which Supply Network Planning (SNP) and Capable-to-Match (CTM) do not plan production.

Use

You divide the areas of responsibility for planning between the SNP production horizon and the PP/DS Horizon: You plan production with SNP or CTM outside of the SNP production horizon; planning is bucket-oriented and usually stretches over the medium-term horizon. In the short-term horizon, that is the PP/DS horizon, you plan production in more detail using automatic Production Planning and Detailed Scheduling (PP/DS). You can manually create PP/DS orders outside of the PP/DS horizon. Therefore, the SNP production horizon is only relevant for SNP and CTM and does not cause constraints on order generation at PP/DS level.

If the SNP production horizon is shorter than the PP/DS horizon, the planning areas overlap. This means that planning tasks require full reconciliation.

Use in SNP

SNP does not create any planned orders in the Production (planned) key figure, but moves production to the first day after this horizon. SNP deletes all unfixed SNP planned orders from previous planning runs within this horizon. The horizon starts on the system date (or date defined in the Planning Start Date field of the planning book or using the PDATE user exit for background processing).

Use in CTM

CTM does not generate or delete any planned orders within this production horizon. The horizon starts on the system date (or the date you specified as the planning start in the CTM profile). If no value has been specified here, CTM takes into account the PP/DS Horizon in the planning version.

Use in PP/DS

If you do not enter any value for the PP/DS horizon or if you enter the duration '0', the system automatically uses the SNP production horizon as the PP/DS horizon. Therefore, the PP/DS horizon is as long as the SNP production horizon. This means the planning intervals for SNP and PP/DS are sequenced with no gaps or overlaps.

For more information, see Adjusting the PP/DS Horizon.

Note

If you want to plan the receipts created in SNP or CTM in detail, convert the SNP or CTM orders into PP/DS orders.

Dependencies

In the Fix Production field, you can specify that SNP is to consider all SNP planned orders from previous planning runs as fixed in this horizon and therefore does not delete them.

You use the Period Category field to specify that the SNP production horizon is defined in calendar days, weeks, or months. This setting can influence data consistency, particularly regarding integration of SNP planned orders with SAP R/3.

Example

Situation at the start of the month:

• The production horizon is 15 days long.

• Distribution demands arise at a plant on the 10th and 20th of the month.

• The target days' supply at the plant is zero.

Result: Production for the distribution demands is planned for the 15th and the 20th of the month. The demands within the SNP production horizon are planned including due date overruns in Supply Network Planning.

Supply Network Planning: Forecast Horizon in Days

Horizon in calendar days during which the forecast is not considered as part of the total demand.

Use

Within this horizon, Supply Network Planning (SNP) does not take the forecast into account when calculating total demand. Outside of this horizon, the system calculates total demand using either the forecast or sales orders (whichever value is larger), and the other demands (dependent demand, distribution demand, planned demand, and confirmed demand).

Dependencies

If you have defined a requirement strategy on the Demand tab page of the location product master, the system calculates the total demand outside of the forecast horizon either as a total of the forecast and sales orders (strategy 20, Planning with Final Assembly) or only uses the forecast (strategy 10, Make-to-Stock Production).

The SNP and deployment optimizers only take into account the forecast horizon if you have set the Forecast Horizon indicator on the Integration tab page of the SNP optimizer profile or SNP deployment optimizer profile.

Example

The situation at the start of the month is as follows:

• Demand of 10 pieces is forecast for the 10th, 20th, and 30th of the month.

• There are sales orders of 5, 5, and 15 pieces respectively on the 10th, 20th, and 30th of the month.

• No requirements strategy has been specified in the location product master.

• The defined forecast horizon is 15 days.

Result: After the planning run, the following is displayed in the Total Demand key figure in interactive Supply Network Planning: 5 pieces on the 10th, 10 pieces on the 20th, and 15 pieces on the 30th of the month.