Summary
Symptom
You can execute the release from Demand Planning (DP) to Supply Network Planning (SNP) in two different ways.
- Technical process: The system reads all data specified in the selection at the same time, then the system generates or changes the forecast orders sequentially for ea ch product location combination.
- Application: Only for a few product location combinations, because otherwise memory problems (liveCache Heapmemory) can occur. You should not use this transaction or this report for mass release.
- Period of the release:
The period is determined using the FROM and TO dates. If no FROM date is specified, the system uses the respective current date.
- Periodicity of the release (for example week or month):
The periodicity is (optionally) defined using the planning buckets profile (refer to Transaction /SAPAPO/TR30). You can only use planning buckets profiles that are compatible with the storage buckets profile of the planning area (refer to Transaction /SAPAPO/TR32). If the storage buckets profile consists, for example, of weeks and months, you can use all planning buckets profiles for the release that consist of weeks and months, however, you cannot use planning buckets profiles with a periodicity 'Day' or 'Fiscal year variant'. If no planning buckets profile is specified, the system uses the shortest periodicity possible for the release - the technical periods. If, for example a storage buckets profile uses weeks and months, the technical periods comprise a week/month average, for which weeks that are in two different months are divided into two technical periods.
The system aggregates the data on a time basis according to the planning buckets profile or it reads the data in the technical periods. If a daily buckets profile (a planning buckets profile with periodicity 'Day' only) is used, the system can break down the data read into days (refer to the documentation or F1 help). The daily buckets profile takes effect from the beginning of the release period (see above), even if this is in the past.
If this function is not sufficient, you can use the /SAPAPO/SDP_RELDATA BAdI. You can use this BadI, for example, to break down the data from months to weeks if the data in the DP exists only in months, but if you need it in weeks in the SNP.
- As of SCM 5.0, you can also use Transaction /sapapo/sdp_split to define period split profiles, which allow a certain number of periods to be split into a more precise periodicity than the release periodicity. You can use a distribution function to change the weighting of some time periods. If required, the period can be split into several stages. For example: monthly data => weekly data => daily data. There is just one prerequisite: The starting periodicity must be the same as the release periodicity.
- Performance: for many product location combinations, use DP mass processing.
- Technical process: The system reads the data for each product location combination (if no location distribution is used), then the system creates or changes the forecast orders for each product location combination
- Application: Mass release
- Period of the release:
Corresponds to the period defined by the planning folder/data view used. Note that the system still ignores offsets from the planning book definition during the transfer.
- Periodicity of the release (for example week or month):
The periodicity is defined using the planning buckets profiles (buckets profile ID Future/Past) of the planning book/data view used. Release in technical periods is not possible in mass processing (unless the storage buckets profile of the planning area uses days or it consist s of only one periodicity).
Optionally you can specify a daily buckets profile in the release profile (see also Transaction /SAPAPO/MC8S). The daily buckets profile takes effect from the beginning of the release period (see above), even if this is in the past.
If this function is not sufficient, you can use the /SAPAPO/SDP_RELDATA BAdI. You can use this BadI, for example, to break down the data from months to weeks if the data in the DP exists only in months, but if you need it in weeks in the SNP.
- You can also use Transaction /sapapo/sdp_split to define period split profiles, which allow a certain number of periods to be split into a more precise periodicity than the release periodicity. You can use a distribution function to change the weighting of some time periods. If required, the period can be split into several stages. For example: monthly data => weekly data => daily data. There is just one prerequisite: The starting periodicity must be the same as the release periodicity.
- Performance:
To achieve good performance, you should use a planning book/data view especially optimized for the release. Additional information: Note 398726
The use of a daily buckets profile has a negative impact on performance.
/sapapo/mc90
/SAPAPO/RTSOUTPUT_FCST
Release, 28000
/sapapo/sdp_split
Consulting
Header Data
| Release Status: | Released for Customer |
| Released on: | 16.02.2006 15:42:11 |
| Master Language: | German |
| Priority: | Recommendations/additional info |
| Category: | Consulting |
| Primary Component: | SCM-APO-FCS-RF Release |
| Secondary Components: | SCM-APO-SNP Supply Network Planning (SNP) |
| SCM-APO-FCS Demand Planning | |
| SCM-APO-FCS-MAP Mass Processing |
Affected Releases
|
Related Notes
| 1003965 - Wrong Period Split results when releasing from DP to SNP. #2 | |||
| 546079 - FAQ: Background jobs in Demand Planning | |||
| 398726 - DP 3.0: performance planning book/data view |
No comments:
Post a Comment