Release of the Demand Plan to SNP 
Purpose
This process makes the demand plan available to the supply chain planner if the supply chain planner does Supply Network Planning using liveCache orders. The supply chain planner can then use the demand plan as a basis for making sourcing, deployment and transportation decisions. From a technical point of view, you are copying data from liveCache time series objects to a forecast category in the liveCache orders.
If Supply Network Planning is done in liveCache time series, see
Copy Management.In a separate process the supply chain planner releases the SNP plan to Demand Planning. When you do this, data of particular categories in the SNP plan, which has been created or changed by the supply chain planner, is copied to a predefined key figure in a DP planning book. Here, you can do reporting on the released data and, in particular, compare the original "unconstrained" demand plan with the "constrained" SNP plan. For more information, see
Release of Supply Network Plan to Demand Planning.Prerequisites
Result: Example 1
You create a demand plan in months in Demand Planning. The storage buckets profile contains weeks and months. The technical periods in which the data is stored are as follows:
Time span of technical period |
Number of days in technical period |
Planned demand quantity |
Monday and Tuesday, |
2 |
40 |
Wednesday, March 1 through |
5 |
100 |
Monday, March 6 through |
7 |
70 |
Monday, March 13 through |
7 |
70 |
Monday, March 20 through |
7 |
70 |
Monday, March 27 through |
5 |
50 |
Saturday and Sunday, |
2 |
20 |
For the release to Supply Network Planning, you specify no planning buckets profile and no daily buckets profile. You specify a release horizon from March 1 through March 31. The system reads the following data and releases it to Supply Network Planning in the same buckets. The ship-from calendar of the location determines which days are workdays in Supply Network Planning. In this example, all days from Monday through Friday are always workdays.
From date |
To date |
Planned demand quantity |
March 1 |
March 5 |
100 |
March 6 |
March 12 |
70 |
March 13 |
March 19 |
70 |
March 20 |
March 26 |
70 |
March 27 |
March 31 |
50 |
Result: Example 2
You create a demand plan in months in Demand Planning. The storage buckets profile contains weeks and months. The technical periods in which the data is stored are as in example 1 above.
For the release to Supply Network Planning, you specify no planning buckets profile and a daily buckets profile with 12 days. You specify a release horizon from March 1 through March 31. The system reads the following data:
From date |
To date |
Planned demand quantity |
March 1 |
March 5 |
100 |
March 6 |
March 12 |
70 |
March 13 |
March 19 |
70 |
March 20 |
March 26 |
70 |
March 27 |
March 31 |
50 |
The following demands are released to Supply Network Planning. The ship-from calendar of the location determines which days are workdays in Supply Network Planning. In this example, all days from Monday through Friday are always workdays.
Bucket |
Planned demand quantity |
March 1 |
20 |
March 2 |
20 |
March 3 |
20 |
March 4 |
20 |
March 5 |
20 |
March 6 |
10 |
March 7 |
10 |
March 8 |
10 |
March 9 |
10 |
March 10 |
10 |
March 11 |
10 |
March 12 |
10 |
March 13 through 19 |
70 |
March 20 through 26 |
70 |
March 27 through 31 |
50 |
Result: Example 3
You create a demand plan in months in Demand Planning.
For the release to Supply Network Planning, you specify a planning buckets profile containing months only but no daily buckets profile. You can specify a planning buckets profile only when releasing data online. You specify a release horizon from March 1 through March 31. The system reads the following data and releases it to Demand Planning in the same bucket.
From date |
To date |
Planned demand quantity |
March 1 |
March 31 |
360 |
Result: Example 4
You create a demand plan in months in Demand Planning.
For the release to Supply Network Planning, you specify a planning buckets profile containing months only, as well as a daily buckets profile containing 12 days. You can specify a planning buckets profile only when releasing data online. You specify a release horizon from March 1 through March 31. The system reads the following data:
From date |
To date |
Planned demand quantity |
March 1 |
March 31 |
360 |
The following demands are released to Supply Network Planning. The shipping calendar of the location determines which days are workdays in Supply Network Planning. In this example, all days from Monday through Friday are always workdays.
Bucket |
Planned demand quantity |
March 1 |
360/31 = 11.6 |
March 2 |
360/31 = 11.6 |
March 3 |
360/31 = 11.6 |
March 4 |
360/31 = 11.6 |
March 5 |
360/31 = 11.6 |
March 6 |
360/31 = 11.6 |
March 7 |
360/31 = 11.6 |
March 8 |
360/31 = 11.6 |
March 9 |
360/31 = 11.6 |
March 10 |
360/31 = 11.6 |
March 11 |
360/31 = 11.6 |
March 12 |
360/31 = 11.6 |
March 13 through 31 |
360 - (12 * 11.6) = 220.8 |
The number of decimal places to which the system rounds depends on the number of decimal places defined for the unit of measure in Customizing.

In mass processing, the release horizon is given by the horizon attached to the data view you specify in the mass processing activity and job.
The Period split on the SNP2 tab of the product master record also determines the results of the release to SNP. For more information, see the F1 Help of this field.
If you plan in weeks in Supply Network Planning, the system aggregates the daily quantities into weekly buckets.
If you require a time split other than the ones illustrated above, use functional enhancement APODM010 (transaction CMOD); for example, if you want to create demand quantites in Supply Network Planning on the 1st and 15 th of every month.