Hierarchy
EA-RETAIL (Software Component) SAP Enterprise Extension Retail⤷
MM-CBP (Application Component) Consumption-Based Planning (See Also PP-MRP)⤷
WSRP (Package) Retail: Store Replenishment
Basic Data
| Data Element | WSRP_DECATPQTY |
| Short Description | Determime Planned Issues and Receipts Using ATP |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1_X | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | ATP |
| Medium | 20 | Issues/Receipts ATP |
| Long | 40 | Determine Receipts/Issues (via ATP) |
| Heading | 50 | Determine Receipts/Issues (via ATP) |
Documentation
Definition
Indicator for determining planned issues and receipts using ATP (ATP = Available to Promise).
If you choose to determine the planned issues and receipts, you must also determine the current stock.
Supplementary Documentation - WSRP_DECATPQTY0001
Use
In the three-step replenishment method, planned issues and receipts using ATP (Available to Promise) are defined during requirements calculation or when the data for the calculation is defined. This means, therefore, that you can either set the indicator when the requirements calculation data is defined or when the requirements calculation itself actually takes place.
If the indicator is set for defining data for the requirements calculation, the system temporarily stores planned issues and receipts using ATP for the requirements calculation. This means that performance is optimized when the planned issues and receipts are calculated during requirements calculation is run.
If the planned issues and receipts are calculated using ATP when the requirements calculation data is determined, the documents are not included if they were generated between the definition of the requirements calculation data and the requirements calculation itself. This is the case even if the documents would normally be included.
Planned issues and receipts only need to be defined when data for the requirements calculation is generated or for the requirements calcultion itself, if you specifically want to include the data when you are calculating your replenishment requirements.
Dependencies
Example
Supplementary Documentation - WSRP_DECATPQTY0002
Use
Three-step replenishment method
In the three-step replenishment method, you can calculate planned issues and receipts using ATP (Available to Promise) when you define the requirements calculation data or when running the requirements calculation itself. This means that the indicator can be set when the data for the requirements calculation is defined or when the requirements calculation is run.
If you set the indicator when the data for calculating the requirements is defined, the planned issues and receipts calculated with ATP for the requirements calculation are stored temporarily, thereby ensuring that performance is good when the planned issues and receipts are calculated.
If the planned issues and receipts are calculated using ATP when the data for the requirement calculation is generated, the documents that are normally taken into consideration in calculation are not included, even if they when generated between the generation of the data for the requirement calculation and the calculation actually being run.
Planned issues and receipts only have to be calculated for determining the data for calculating requirements or when the calculation itself is run, if you also want to include them in the calculation of the replenishment requirements.
In the two-step method, the planned issues and receipts only need to be calculated when the replenishment requirement is calculated if this data is to be taken into consideration.
Dependencies
Example
History
| Last changed by/on | SAP | 20011002 |
| SAP Release Created in | 46C |
