Show TOC Entering content frame

Process documentation Release of the Demand Plan to SNP Locate the document in its SAP Library structure

Purpose

This process makes the demand plan available to the supply chain planner if the supply chain planner performs Supply Network Planning using liveCache orders. The process also makes the data available in Production Planning and Detailed Scheduling (PP/DS), depending on the horizons that have been maintained for the products involved. (For more information, see the input help for the SNP Prod. Hor. field of the location product master – SNP 2 tab.) In SNP, the supply chain planner can then use the demand plan as a basis for making sourcing, deployment, and transportation decisions. The actual production is then planned in PP/DS.

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 performed in liveCache time series, see Structure linkCopy Management.

In a separate process, the supply chain planner releases the SNP plan to Demand Planning. The data of particular categories in the SNP plan, which has been created or changed by the supply chain planner, is thereby copied to a predefined key figure in a DP planning book. Here, you can perform reporting on the released data and, in particular, compare the original "unconstrained" demand plan with the "constrained" SNP plan. For more information, see Transfer of the SNP Planning Results.

Prerequisites

·        You have created product master records for your products.

·        You have created location master records for your locations.

·        You have set up your supply chain models.

·        If you are using Structure linkdescriptive characteristics, you need to have previously created a Structure linkconsumption group and assigned it to the relevant products.

·        If applicable, you have defined the location split for the release to Supply Network Planning. For more information, see Structure linkLocation Split.

·        If applicable, you have defined a product split. For more information, see Structure linkProduct Split.

Process Flow

There are two methods for releasing data to SNP:

...

·        Online

You can release small amounts of data using an online transaction. For more information, see Releasing the Demand Plan Online.

·        In the background

You plan mass releases as background jobs that can then be executed when there is little system activity. For more information, see Releasing the Demand Plan with Mass Processing.

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,
February 28 and 29

2

40

Wednesday, March 1 through
Sunday, March 5

5

100

Monday, March 6 through
Sunday, March 12

7

70

Monday, March 13 through
Sunday, March 19

7

70

Monday, March 20 through
Sunday, March 26

7

70

Monday, March 27 through
Sunday, March 31

5

50

Saturday and Sunday,
April 1 and 2

2

20

For the release to Supply Network Planning, you do not specify a planning buckets profile or a daily buckets profile. You specify a release horizon from March 1 through March 31. The system reads the following data and releases it in the same periods 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 Sunday are 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

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 do not specify a planning buckets profile; you specify 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 shipping calendar of the location determines which days are workdays in Supply Network Planning. . In this example, all days from Monday through Sunday are workdays.

Period

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

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 in the same period to Supply Network Planning.

From-Date

To-Date

Planned Demand Quantity

March 1

March 31

360

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 Sunday are workdays.

Period

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.

Note

In mass processing, the release horizon is given by the horizon attached to the data view that you specify in the mass processing activity and job.

The Period Split on the SNP2 tab page of the product master record also determines the results of the release to SNP. For more information, see the input help for 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 APODM017 (transaction CMOD); for example, if you want to create demand quantities in Supply Network Planning on day one and day 15 of every month.

Two Business Add-Ins (BAdIs) are also available for the release function:

·        Change Data During Release to SNP

·        Set Requirements Strategy During Release

For more information, see the Implementation Guide (IMG) for Demand Planning under Business Add-Ins ® Release to SNP.

 

 

 

Leaving content frame