Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
SD-CAS-BD (Application Component) Basic Data⤷
VIV (Package) Introductory guide R/3 procedures
IMG Activity
| ID | SIMG_CFMENUOLSDOV3Z | Specify Hierarchy |
| Transaction Code | S_ALR_87006124 | IMG Activity: SIMG_CFMENUOLSDOV3Z |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUOLSDOV3Z | Specify hierarchy |
| Customizing Activity | SIMG_CFMENUOLSDOV3Z | Specify hierarchy |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUOLSDOV3Z |
In this IMG activity, you assign an info structure to each of the product allocation determination procedures. You can display the suitable statistical structures.
The system uses both the assignment of the info structure to the product allocation determination procedure and the product allocation object to determine the planning hierarchy in which the product allocations are stored, relevant for the check.
You can specify a formatting character for each info structure and this is used to form the key for general entries (default entries). Once the planning hierarchy has been created, you can expand the planning hierarchy with general entries using the node 'Permit collective product allocation in info structures'. This creates a default entry for every node in the hierarchy.
Indicator for product allocation method
Set this indicator to define which of the two available methods you want to use for offsetting the order quantity against the product allocation quantity. They are as follows:
- If you do not set the indicator, the system will use the 3.0F product allocation method (discrete ATP check).
Using this method, the system offsets the quantity confirmed in the sales document against the product allocation quantity. It uses only the product allocation quantities from current and future periods (unused product allocation quantities from past periods are not taken into account). The update date in the relevant activation rule of the product allocation information structure is used to to determine the periods. The system only allows three dates: delivery date, material availability date, and planned goods issue date.
Example:
Product allocation quantities:
January February March April May
50 50 50 50 50
If a customer places an order on 03/01 for 150 PCS, ATP proposes 50 PCS for March, 50 PCS for April, and 50 PCS for May. The remaining unused quantities from January and February are not taken into account.When you use this method, note that you cannot use the following product allocation functions:
- Consumption periods: Here you can define a number of past and future periods that should be used as the valid consumption period.
- Allocation steps: Here you can define several product allocation steps with different info structures. The only valid hierarchy step value is 0.
- If you set the indicator, the system uses the standard product allocation method available as of 4.0A. This method involves a checking logic that corresponds with the ATP cumulation logic.
In this method, the system uses the standard ATP checking logic to offset the quantity against the unused product allocation quantities. The system includes unused product allocation quantities from previous periods when calculating the available product allocation quantity for the current period.
Example:
Product allocation quantities:
January February March April May
50 50 50 50 50
If a customer places an order on 03/01 for 150 PCS, ATP first cumulates the unused product allocation quantities from past periods (50 PCS for January and 50 PCS for February) to calculate the available product allocation quantity as 150 PCS. As a result of this check, 150 PCS are confirmed for the relevant date.Note:
Furthermore, you can use the following additional product allocation functions:
- Consumption periods: Here you can define a number of past and future periods to be used as the valid consumption period. This is then integrated into the cumulation logic in order to identify how many prior or future periods should be taken into account for unused product allocation quantities.
- Allocation steps: Here you can define several product allocation steps with different checking logic. You can use this function to perform the following checks, for example:
Step 1: Check order quantity against plant capacity
for the relevant periods
Step 2: Check order quantity against the customer's
permitted product allocation quantities
Note
You can use a single info structure for several product allocation determination procedures. However, all procedures assigned to an info structure must have the same product allocation indicator. This means that an info structure supports either discrete or cumulative ATP. Furthermore, you can use a structure only once in one procedure.
Note
You must use the same formatting character for each info structure, even if the info structure is assigned to different determination procedures. If an info structure has been assigned several times, assignment is permitted with or without a formatting character. However, deviating formatting characters for the same info structure are not allowed.
Activities
- Assign info structures to the product allocation determination procedures.
- Specify for which combination you want to use the formatting character.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_CFMENUOLSDOV3Z | 0 | HLA0006562 | Availability Check |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| V_T190H | V - View | OV3Z | 0000000000 | Maintain product allocation hierarchy |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
