Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions⤷
VZ (Package) Application development R/3 RV central functions
Basic Data
| Data Element | KOMTH |
| Short Description | Product allocation: Selection of product allocation methods |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | FLAG | |
| 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 | Method |
| Medium | 18 | Prod all. methods |
| Long | 24 | Prod. alloc. methods |
| Heading | 0 |
Documentation
Definition
During product allocation, the order quantity can be settled against the allocation amount using one of two different methods. You use the indicator for the product allocation method to determine which method is to be used. You have the following options:
- If you do not set the indicator, the system continues to use the method that has been available since 3.0F for product allocation (discrete ATP-check).
This method settles the confirmed quantity in the sales document against the product allocation quantity. This is only carried out on the basis of the product allocation quantities for current and future periods (unused allocation quantities for periods in the past are not taken into account). The date with which the periods are determined is the confirmed delivery date in the schedule line, independent of whether it is determined by the availability check (ATP) or not.
Example:
Product allocation quantities:
January February March April May
50 50 50 50 50
If an order for 150 pieces is made on March 1st, then the product allocation check proposes 50 pieces for March, 50 pieces for April and 50 pieces for May. The free quantities from January and February are not considered.
If you use this method, then the following functions for product allocations are not available:
- Consumption interval: Option for defining a number of periods in the past and the future that are to be used for consumption.
- Product allocation step: Option for defining several product allocation steps with different info structures. The only allowed hierarchy step value is 0.
- If you set the indicator, then the system uses the standard product allocation method, available as of 4.0A, which uses cumulative ATP checking logic.
With the help of the standard ATP checking logic, the quantity to be consumed is validated against the remaining free allocation quantity. Unused allocation quantities of previous periods are added to the values in the current period in order to calculate the available product allocation quantity.
Example:
Product allocation quantities:
January February March April May
50 50 50 50 50
A customer places an order for 150 pieces on March the 1st. The product allocation check first of all cumulates the unused product allocation quantities from previous periods (50 pieces for January + 50 for February) and determines a total amount available of 150 pieces. The result of the check is that 150 pieces are confirmed for the date.
Note: The date, with which the periods are determined, is the update date in the corresponding activation rule for the product allocation information structure. Only three different dates are allowed: Delivery date, material availability date and planned goods issue date.
The following additional product allocation functions are also available:
- Consumption interval: Option to define a number of periods in the past and the future to be used as a consumption interval. This is a part of the cumulation logic, which defines how many previous and future periods are to be considered for the check against unused allocation quantities.
- Product allocation step: Option to define several product allocation steps with different checking logic. With this function, you could carry out the following checks:
1st step: Check order quantity against plant capacity
over the relevant periods
2nd step: Check order quantity against the allocation
quantities allowed for the customer
Note
A single information structure can be for several product allocation procedures. All procedures that are assigned to an information structure must have the same product allocation indicator. This means that an information structure supports either a discrete or a cumulative check. A structure can only be used once within a procedure.
History
| Last changed by/on | SAP | 20130529 |
| SAP Release Created in |
