Enterprise Resource Planning Blogs by Members
Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today!
Showing results for 
Search instead for 
Did you mean: 
Former Member


The requirement from the business was to have different levels of allocation for the same material for different countries. For example, Korea needed to do the allocation for materials at sales office and plant level whereas Pakistan wanted the allocation for the same materials at customer group level.
It might also happen that business may need different planning time fence for different countries for allocation consumption. For example, one country
requires allocation consumption to be checked on weekly basis whereas other countries need them on a monthly basis.
With the Standard SAP, the above requirements are not feasible as the Product allocation procedure assigned to the material is at Basic data1 level which is
common to all different sales orgs.


For the above requirement, the below can be implemented:


1. Info-structure definition MC21: Info-structure definition should be done by defining the characteristics and key figures. For our understanding and business case as mentioned above, 2 info structures have been defined – S860 and S861 for Korea and Pakistan respectively as below:
2. Update group OMOG: The update group should be defined with the correct application (01 for Sales and distribution). This would be later on used
    for defining the update rules for the specific info-structure.
3. Create Update rules MC26: Update rules need to be defined for the data which needs to be updated automatically in the info-structure. In case needed, a formula or a requirement routine can be assigned for the spcific key figures.

4. Define Planning Type MC8A: A planning type describes a customized planning table. You use planning types to create and store important data from any information structure. Planning type Z_S860 and Z_S861 are created for the respective info structures.
5. Product Allocation Configuration: All the required setup as per standard product allocation setup should be completed. The most important setup is to add the 2 info structures in the product allocation procedure as below:

OV3Z - Assigning Procedure to Information structure
OV4Z - Control Product Allocation
Other configurations needed are:
  1. OV5Z – Consumption periods
  2. OVZ0 - Activate Allocation for Requirement Class
  3. OVZ8 - Activate Allocation for Schedule Line Category
  4. MC61 – Create Planning Hierarchy
  5. OV7Z - Generate Masking Character
  6. MM02 – Assign Product Allocation Procedure on Basic
    Data 1 Tab
6. Development in SAP Enhancement: SAP has provided a specific enhancement point where based on specific conditions, specific step in the product allocation procedure can be ignored so that the system checks the allocation quantity in the required info-structure only.
With the above coding, for a specific sales org, we can delete a specific step from the product allocation procedure so that the system checks the allocation
quantity from the relevant info-structure only.


2 sales orders are created - 1 for sales order 4500 and another for sales org 4460 for the same material. For Sales Org 4500, the product allocation quantity should be checked in info-structure S860 whereas for the sales org 4460, the allocation quantity should be checked in info-structure S861.
1. Order 1 – for sales org 4500:
    The product allocation quantity is taken from the info-structure S860.
2. Order 2 – for sales org 4460:
    The product allocation quantity is taken from the info-structure S861.
Labels in this area