Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
LO-LIS (Application Component) Logistics Information System (LIS)⤷
MC0C (Package) Customizing Logistics Information System
IMG Activity
| ID | OLIS_OV7Z | Create characteristics for remainder allocations |
| Transaction Code | S_ALR_87000647 | IMG Activity: OLIS_OV7Z |
| Created on | 19981222 | |
| Customizing Attributes | OLIS_OV7Z | Create characteristics for remainder allocations |
| Customizing Activity | OLIS_OV7Z | Create characteristics for remainder allocations |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | OLIS_OV7Z |
In this step, you maintain a block allocation for characteristic values for which no specific allocation is defined. SAP recommends you carry out this step if you intend to plan product allocation quantities.
The system then adds the characteristic value '#' to every level of the planning hierarchy except the top one. This top level is represented by the characteristic "product allocation object". Thus, it acts as a container for all characteristic values that are not specified by name in the planning hierarchy.
You quantify the allocations by defining proportional factors in the planning hierarchy.
When the system carries out allocations checking, it works from the bottom of the planning hierarchy upwards. With information structure S140, it checks whether an allocation has been maintained for the sold-to party for which the order has been taken. If not, it moves up one level and checks to see whether the customer belongs to a customer group for which an allocation has been maintained. If no allocation has been maintained for characteristic values at the lower levels, the system arrives at the "product allocation object" characteristic value at the top of the planning hierarchy and derives the allocation from the proportional factor from the appropriate container. If a valid combination of characteristic values is found but the allocation has already been used up, then the container is not used.
Thus you can assign allocations to only the most important customers without having to create separate master records for each of the less important characteristic values (i.e. customers).
Activities
- Enter the information structure on which your product allocation planning is based.
The standard information structure provided by SAP for product allocation is S140.
- If you want the results to be saved on the database, select Change database.
- Select Program -> Execute.
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 2 | Optional 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 | OLIS_OV7Z | 0 | HLA0006700 | Planning |
| SIMG | OLIS_OV7Z | 1 | O HLA0001840 | |
| SIMG | OLIS_OV7Z | 2 | O HLA0006664 |
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 |
| IMGDUMMY | D - Dummy object | OV7Z | LIS_SOPKON | Create characteristics for remainder allocations |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
