SAP Note 159937 - Checklist for requirements consumption
and reduction in APO
Note Language: English Version: 16 Validity: Valid Since 14.08.2008
Summary
Symptom
For problems with the requirements consumption and requirements reduction,
you should check the following details first and, if necessary, specify
them in the customer problem.
Other terms
Reason and Prerequisites
Solution
1. In general, only sales orders created in R/3 or by a corresponding BAPI
in APO are consumed.
The requirements are not consumed if sales orders or forecast orders are
created using the report /SAPAPO/SJKTST01.
During consumption, the system refers to the requirements class from R/3
that is displayed in APO as a check mode. A consumption indicator must be
maintained in check mode.
If the system cannot find a requirements class in R/3, you can use the
check mode from the product master (ATP).
2. Before a requirements consumption can take place, a requirements
strategy must be maintained in the product master and a release from DP to
SNP must occur.
An assignment indicator is maintained for the requirements strategy.
The assignment indicator is used to determine the relevant
forecast orders and to consume the sales orders (the forecast order
assignment indicator and the sales order consumption indicator must be the
same).
If an assembly consumption is executed, the assembly indicator must be set
in the product master. The same applies to stock transfer requirements.
3. Consumption takes place in APO when the order is entered or released to
SNP.
The consumption of different requirements elements (sales order, dependent
demand and so on) depends on the ATP categories specified in the category
group of the strategy.
During subassembly planning with a planned order and production order, in
particular, you should check the category group of the strategy to see
whether all of the relevant categories exist.
Relevant categories are maintained in the table /SAPAPO/ATP03 and depend on
the MRP element (DELKZ) and the category type (ATPCATTYP, receipt,
requirement and so on).
In addition, only the withdrawable material reservations are important when
you take material reservations into account.
10.11.2010 Page 1 of 3
SAP Note 159937 - Checklist for requirements consumption
and reduction in APO
You should therefore set the following categories in the case of a scenario
with production orders and subassembly planning.
AY(secondary requirement), AN, AR, AT (material reservation) AV, AX
(dependent reservation).
4. You can use transaction /SAPAPO/DMP1 to check the consumption status.
5. The consumption process in APO uses the entire forecast period. The
consumption behaves differently here to the consumption in R/3. If, for
example, a month is set as the time buckets profile in Demand Planning, the
entire month is used in consumption. The consumption is for an exact day if
"Day" is set in the time buckets profile. In this context, refer to point
6.
In addition, you have the option to enhance the customer exit
EXIT_/SAPAPO/SAPLAPO_EXIT_001 (SAP enhancement APODM017). The "To" date
must correspond with the "From" date used in the release of the forecast
from DP to SNP. Use the following date fields in the customer exit
interface:
LINE_BUCKET_START
LINE_BUCKET_END
You must also set the time to 23:59:59. You must adjust the following
fields:
REQUESTED_TIME_START
REQUESTED_TIME_END
All of these fields are contained in the structure SCHEDULE_LINE_TAB.
6. Calendar days are used for consumption.
The standard SAP system response deviates from the R/3 system in this
case also.
7. Forecast requirements with the strategy 30 and 40 are ignored in SNP;
that is, only forecast requirements with final assembly (make-to-stock
production) are taken into account.
Before the planning product can also be used in SNP, copy the strategy 40
with the blank planning segment indicator (stock).
8. APO must contain the appropriate product hierarchy before you can use
consumption with planning products in APO.
You can ensure that this hierarchy exists by transferring the planning
materials from R/3 (the conversion factor is ignored in APO) or by creating
the product hierarchy directly in APO.
9. During goods issue for the delivery in R/3,
the forecast is always reduced to the date requested by the customer.
In addition, overdeliveries are ignored.
10.11.2010 Page 2 of 3
SAP Note 159937 - Checklist for requirements consumption
and reduction in APO
Header Data
Release Status: Released for Customer
Released on: 14.08.2008 14:19:42
Master Language: German
Priority: Recommendations/additional info
Category: Consulting
Primary Component: SCM-APO-FCS-CSP Forecast Consumption
The Note is release-independent
Related Notes
Number Short Text
568506 Collective consulting note on consumption of forecasts
Attributes
Attribute Value
Transaction codes BAPI
Transaction codes HIER
10.11.2010 Page 3 of 3
