Hierarchy
⤷ CRM-CIC (Application Component) Interaction Center WinClient
⤷ CO (Package) R/3 Application development: PP Production orders
Basic Data
Data Element | PP_ATPMG |
Short Description | ATP quantity/available quantity |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | MENGV13 | |
Data Type | QUAN | Quantity field, points to a unit field with format UNIT |
Length | 13 | |
Decimal Places | 3 | |
Output Length | 18 | |
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/av.qty |
Medium | 15 | ATP/avail.qty |
Long | 20 | ATP/avail.qty |
Heading | 20 | ATP/avail.qty |
Documentation
Definition
The following quantities are displayed in this field, depending on the type of availability check:
- Availability check according to ATP (available to promise) logic:
ATP quantity from every receipt that is still available for further requirements.
The calculation of the ATP quantity is carried out as follows:
A new receipt first of all has the full quantity received as the ATP quantity. In the availability check using ATP logic only receipt elements that are before a requirement are taken into account. A requirement first reduces the next receipt back (and thus its ATP quantity). If a remaining quantity is open from this receipt then this remaining quantity stays as the ATP quantity and a further requirement can be met using this.
If a receipt is not sufficient then further receipts and thus their ATP quantity is reduced until the requirements are completely fulfilled.
If no further ATP quantity is available for the requirement or if the requirement can only be partly met then the quantity not met is entered in the requirements line as a negative ATP quantity.
- Availability check against planning (planned independent requirements):
The available (remaining) quantity of the planned independent requirements that has not yet been settled against the dependent requirements/reservations.
When checking against planning, the system only checks against open quantities of components from planned independent requirements.
So in this type of check no ATP quantity is calculated but instead the quantity that is not yet settled against the planned independent requirements and so is available for further dependent requirements/reservations.
History
Last changed by/on | SAP | 19961029 |
SAP Release Created in |