Note 403050 - Consulting note: Release from DP to SNP

Note 403050 - Consulting note: Release from DP to SNP

Summary

Symptom

You can execute the release from Demand Planning (DP) to Supply Network Planning (SNP) in two different ways.

1.) Transaction /SAPAPO/MC90 or report /SAPAPO/RTSOUTPUT_FCST

• 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.

2.) Release within the 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.

Other terms

/sapapo/mc90
/SAPAPO/RTSOUTPUT_FCST
Release, 28000
/sapapo/sdp_split

Solution

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

Software Component Release From Release To Release And subsequent SAP_APPL 46C 46C 46C SAP_APO 30 30A 30A SAP_APO 310 310 310 SCM 400 400 400 SCM 410 410 410 SCM 415 415 415 SCM 500 500 500 SCM 510 510 510

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

Note 546079 - FAQ: Background jobs in Demand Planning

ummary

Symptom

This note contains frequently asked questions/answers on the subject of
the mass processing in Demannd Planning

Other terms

FAQ, Q+A, /SAPAPO/MC8D, /SAPAPO/MC8E, /SAPAPO/MC8F, /SAPAPO/MC8G,
/SAPAPO/MC8K, /SAPAPO/MC90, SM37

Solution

QUESTIONS OVERVIEW
Q1: How should I define an "Aggregational level" in background job?
Q2: What should I put in a "Selection" field in background job?
Q3: Why can I observe a "difference" in results of interactive planning and background job?
Q4: How can I increase performance of the background job?
Q5: How should I define a macro in background job?
Q6: How should I define a release of planned demand to SNP in background job?
Q7: How should I define a transfer of planned demand to R/3 in background job?

QUESTIONS & ANSWERS
Q1: How should I define an "Aggregation level" in background job?
A1: Select the characteristics that correspond to the aggregation
level on which you want the job to be carried out. The aggregation
level can make a big difference to the job results. When you run
the job at aggregated level (eg. you want to run a forecast
for a Sales Organization -> aggregation level = Sales Organisation)
only the aggregated data of the Sales Org. will be taken for the
forecast and than the forecast will be disaggregated to the
detailed level (eg. products) according to your aggregation/
disaggregation method defined for each key figure during definition
of planning area.
Use navigational attribues in selection and aggregation level when
you what to restrict processed data without implicit using of
characteristics.
Do not select characteristics which are not included in a
Selection for which you run the job.
For additional information please refer to the note 374681
and to online documentation (http://help.sap.com)

Q2: What should I put in a "Selection" field in background job?
A2: You can run the job for the characteristic value combinations in a
selection(s) you created earlier in the Shuffler (Interactive
Demand Planning). It is advisable to select value(s) for the
characteristic which was meant as display characteristic in the
selection.

Q3: Why can I observe a "difference" in results of Interactive Planning
and background job?
A3: There are several issues which can make you think that there are
differencies between online and batch results.
1) The selection you entered along with the aggregation level
are used as a basis for the individual, dynamically created
selections(!), which are used for calling the forecast.
In interactive planing, the selection is used directly for the
forecast. Consequently, you might be comparing the results from
different selections.
Example:
You want to do forecast for product A. The forecasting method
is defined as HISTORY + 1 = FUTURE.
Your selection consist of 3 characteristics:
1) Sales Org. 1000
2) Division, 01 02
3) Product A B A B
History (detailed level): 10 20 30 40

The online forecast for product A looks like:
(10+30) + 1 = 41(!)
In background job with the aggregation level Sales Org., Division
and Product the forecast will be done for 2 combinations:
[10 + 1 = 11] + [30 + 1 = 31] = 42(!)

2) In both cases (online and batch) the system uses
the corrected history for the calculation of the forecast.
During batch processing the system does not save the values
for corrected history if the planning book definition for this key
figure is 'not ready for input'. During interactive planning the
system allows to save the data in this line of the planning book.
For additional info please refer to notes 357789, 372939
and to online documentation (http://help.sap.com)

Q4: How can I increase a performance of background job?
A4: Because you generally do not need all data of the planning area and
because in general you need different data for different planning
processes, please maintain a specific planning book and data view
for your background job. The planning book should consist only of
the key figures which are necessary, and the time buckets in data
view should be restricted to the date you need for the job.
Horizon of the planning book must be greater than the horizons in
the forecast profile.
The time period units of the planning book and forecast profile
must be identical because you are not allowed to use planning books
with mixed period units in the background processing (note 357789).
If you set Generate log indicator for your jobs you have to delete
the log periodically. If you do not do this, performance will
deteriorate noticeably! You should regulary use the transaction
/SAPAPO/MC8K (Demand Planning -> PLanning -> Demand Planning in
Background -> Delete Job Log (note 512184). You can easily check
the size of the log by checking the table /SAPAPO/LISLOG.
For some cases (e.g. loading planning areas) you can divide a job
in smaller parts (new jobs) and run it in parallel. The same
objects cannot be processed by the parallel processes (locking
problems). There must be a separation using suitable selection
restrictions in the characteristics combinations (note 428102)

Q5: How should I define a macro in background job?
A5: Before you execute your own macro in the job, you must make sure
that you have implemented all macros that provide your own macro
with data. You must remember that standard macros in Interactive
Planning (start, level and default macro) are not automatically
executed in background job. You must choose proper aggregation
level with data to be changed by the macro.
You define an activity to run a macro for background job with
transaction SAP menu -> Demand Planning -> Environment ->
Current Settings -> Define Activities for Mass Processing
When a macro run didn't change a value (the same value already
existed) you will of course not need to store any data either.
For this reason, the message "Data were stored" will not appear
in the log. In other words, the message "Data were stored" will
only appear if new data have in fact been saved.
For additional info please refer to note 412429.

Q6: How should I define a release of planned demand to SNP in
background job?
A6: You should define an activity and a release profile (/SAPAPO/MC8S)
for mass processing to release a demand from DP to SNP.
The period of the release is defined by future and history time
time buckets profile maintained in the used dataview.
When you want to release data with offset periods you have to use
BAdI /SAPAPO/SDP_RELDATA bacause offset field of the dataview
is not taken into account for release!
After every release all SNP data of the product in the location
are deleted and only the just released data exist in SNP afterwards
You define the periodicity of the release (e.g. weeks, months) with
time buckets profile used in the dataview. When your time bucket
consist of 2 weeks and 3 months and when the time bucket is used
as history bucket and future bucket your data will be released in
this way:
M3 M2 M1 W2 W1 today W1 W2 M1 M2 M3
For additional info please refer to note 403050.
[online you can use trx: /SAPAPO/MC90 or report
/SAPAPO/RTSOUTPUT_FCST, only for small number of data(!)]

Q7: How should I define a transfer of planned demand to R/3 in
background job?
A7: You should define an activity and transfer profile (/SAPAPO/MC8U)
for mass processing to release a demand from APO DP to R/3. The
Requirements Type determines the planning strategy to be used for a
material requirement in R/3 (e.g. VSE "Planning w/o final assembly"
or VSF "Planning with final assembly"). It is not possible to
transport and save PIR on R/3 side without requirements type.
The requirements type must be transported from APO or if it is not
filled on APO side, then it must be customized on R/3 side
(material master). If you transport forecast from APO to R/3, data
on both sides must
be consistent after transport -> all transported PIR must be saved
on R/3 side or stay in outbound (inbound) queue.
When you want to change data before transfer you can use
BAdI /SAPAPO/IF_EX_SDP_RELDATA.
[You can use trx /sapapo/dmp2 to transfer data from SNP to R/3]

Header Data

Release Status:	Released for Customer
Released on:	13.02.2003 17:42:47
Master Language:	English
Priority:	Recommendations/additional info
Category:	FAQ
Primary Component:	SCM-APO-FCS-MAP Mass Processing
Secondary Components:	SCM-APO-FCS Demand Planning
	SCM-APO-FCS-MAC MacroBuilder

Affected Releases

Software Component Release From Release To Release And subsequent SAP_APO 30 30A 30A SAP_APO 310 310 310 SCM 400 400 400 SCM 410 410 410 SCM 500 500 500 SCM 510 510 510

Related Notes

	864950 - Performance problems in DP mass processing
	512184 - Background processing: Periodically delete job log
	412429 - Defining jobs with macros
	403050 - Consulting note: Release from DP to SNP
	398726 - DP 3.0: performance planning book/data view
	390055 - Mass processing: Alerts are not generated
	389641 - Background jobs in Demand Planning with CBF characteristics
	374681 - Selections in mass processing
	372939 - APO consulting: Compare forecast in interactive & batch mode
	357789 - Consulting: Horizons forecast and planning folder
	356407 - Poor performance for alert macros in batch

Optimized Purchasing

Source of Supply: Info Record, Contract Item, or Scheduling Agreement Item.