You are on page 1of 7


April 1, 2008 jiteshdua

Retailers often have to centrally distribute merchandise among a large number of recipients (for example, stores). One example would be fashion merchandise or promotional items. Using allocation tables, you can plan the distribution of this type of merchandise and then trigger the necessary goods movements. You can have the merchandise delivered directly from the vendor to the recipient, from the vendor to a distribution center and then to the recipient, or from a distribution center to a recipient. After you have completed the planning stage, you can then have the system automatically create documents for procuring or delivering the goods. Allocation table - wa01, wa02, wa03 Allocation Rule - wa21, wa22, wa23 Follow-on documents - wa03, wa08 Components of an Allocation Table The allocation table in made up of various components. The following is a short description of the main ones:

Allocation Table Header

An allocation table has one header. The header contains information such as the allocation table number, the organizational levels for which it is valid (purchasing organization and purchasing group) and a header text.

Allocation Table Item

An item is assigned to the header.

Each allocation table can have a number of items. An item contains information such as the items category, the article number, the planned quantity, the allocation rule or site group used and the item status.

Site Group

A site group is assigned to an allocation table item. The information displayed on the site group includes the number of the site group, the number of sites assigned to it, the quotas and the planned quantities.


A site is assigned to a site group. The information displayed on the site includes the number of the site, the planned quantity for the site and supply source.

Distribution Center

A distribution center is assigned to one or more sites. The information displayed on the distribution center includes the number of the distribution center, the planned quantity and the external vendor supplying the distribution center.

Delivery Phase for a Site or Distribution Center

A delivery phase is assigned to a site/distribution center. The information displayed on the delivery phase includes the delivery date, the order date and the delivery quantity. Allocation Table Set-Up The following is a simplified example of how an allocation table can be set up. Allocation rule 17 is used to determine how merchandise in a particular merchandise category is split up among the sites in site group R0021. The merchandise is split up in the ratio 6:4

between the two sites R151 and R152 in the site group. Variants 1 and 2 are to be allocated for the generic article 1.

Item 10

Article Single article 1

Alloc. rule 17

Site group


Quantity 2000

R0021 R151 R152 20 Generic article 1 17 R0021 R151 R152 30 Variant 1 of item 20 17 R0021 R151 R152 40 Variant 2 of item 20 17 R0021 R151 R152 Synchronising Allocation table for Order changes -

2000 1200 800 1000 1000 600 400 700 700 420 280 300 300 180 120

You usually define allocation tables at an early stage in your business processes because you plan and order fashion goods, for example, with a long lead time. If your requirements change after you have created a purchase order but before the goods are delivered, for example, due to new stores opening, you can change the existing purchase order.

The system updates allocation-relevant changes in purchase orders to the relevant allocation tables. Integration You make changes to allocation-relevant purchase order items in purchase order processing for Seasonal Procurement. A log provides you with information about changes and about the synchronization of the allocation table. The system synchronizes an allocation table in the background when purchase orders are changed. Prerequisites You have generated a vendor order (Seasonal Procurement) as a follow-on document for an allocation table, manually created an allocation table with reference to a purchase order (Seasonal Procurement), or generated an allocation table with reference to a purchase order based on operational assortment planning and control. Apart from the vendor order there are no other follow-on documents for recipients of the corresponding allocation table item. Direct delivery orders cannot be synchronized. The purchase order item that you change must be uniquely linked to a delivery phase of the distribution center for an allocation table, otherwise synchronization is not possible. Features When the following data is changed, the system updates the changes to the allocation table: Purchase order quantity and order unit Delivery date in distribution center Distribution center

Flag for allocation table relevance Deletion of a purchase order item You can use a Business Add-In (BAdI) to specify that when the allocation table is synchronized, the data for the distribution center be adjusted, but not the data for the recipient. For more information, see Customizing for Logistics General under Merchandise Distribution - Allocation - Allocation Table - Business Add-Ins for the Allocation Table BAdI: Synchronizing Allocation Table for Changes to PO Items. Activities If you change purchase order items in purchase order processing for Seasonal Procurement and confirm your changes, the system first simulates synchronization of the corresponding allocation items. The changes are only effective in the database once you have saved them. In both cases, you can check the results of changes in a log. Synchronization is performed in several steps: 1. The system checks whether follow-on documents exist for recipients of the allocation table item. If they do, the system cannot change the allocation table and it issues a message to purchase order processing stating this. 2. The system copies the changes in the purchase order item to the distribution center of the relevant allocation table item. 3. The system copies changes that are relevant for the allocation table item from the purchase order item. While changes to the delivery date are not relevant, changes to quantities, for example, are.

4. The system transfers changes that are relevant for recipients for the individual allocation items . You can use a BAdI to deactivate synchronization of recipient data. 5. It is possible that after the system transfers changes from the purchase order item to the allocation table items, these allocation table items will be incomplete. To ensure that the items are complete again and you are able to generate follow-on documents, you must post process incomplete allocation table items in the item overview of the allocation table. Deleting Allocation Table

Choose the Delete Allocation Table screen. 1. In the Deletion for frame, choose Alloc tbl. 2. Enter the required criteria for selecting the allocation tables to be deleted, for
example purchasing organization, purchasing group or the allocation table number 3. Enter the status of allocation tables you want to select. A distinction is made between:

Status Not active

An allocation table has this status if no follow-on documents have been generated for it. This type of deletion is used in cases where you have just created an allocation table but you realize immediately that it is not required (because the data entered was not correct or the allocation is not needed after all) and can be deleted.

Status Done

An allocation table has this status if all follow-on documents have been generated for it.

5. Choose Program
We are required to implement product allocation functionality in SAP R/3 (Enterprise Version). We tried to do the elaborate steps as per the implementation guide but are not successful. Can you kindly help by giving the simple steps for implementation.

Please see if the following helps: Configuration Overview; Allocation Specific Usage 1.Allocation Procedure (OV1Z) The product allocation procedure is the parent of the entire allocation process. All materials that are to be included in the allocation scheme are required to have an allocation procedure assigned to it in the material master. In addition, as of release 4.0, it is in the procedure that the method of allocation is defined. The user has the opportunity to set an indicator to identify their choice of two different methods (discrete and cumulative allocation) to evaluate the quantities to be considered for product allocation. 2.Allocation Object (OV2Z) The allocation object is the root level of the allocation process where actual data is entered and planned in LIS. The object allows the user to further break down a procedure into smaller parts for future validation of components comprising a specific material 3.Allocation Hierarchy Mapping (OV3Z) Primarily, this transaction permits the assignment of an allocation procedure to an LIS information structure. Secondly, a character is assigned to the information structure to permit collective planning. Finally, the user can assign a step level to the procedure and information structure to sequence the order in which allocation quantities are checked. This functionality allows the user the opportunity to check product allocation against several product allocation scenarios, before the required quantity is confirmed 4.Define Consumption Periods (OV5Z) The allocation consumption periods functionality is only valid if the allocation method flag has been set (OV1Z). If you have de-selected the method field, this functionality is not available. The consumption window indicates the number of past and future periods to be used in the allocation check. 5.Control Product Allocation (OV4Z) In order for the allocation process to function properly, allocation control records are created primarily to map allocation procedure steps to their corresponding objects so that the allocation data records can be located for validation. Secondly, validity periods must be established to indicate when the allocation control records are active. Finally, the user has the option of establishing a conversion factor per allocation control record to accommodate BOM listings of constrained materials 6.Activate Allocation for Requirement Class (OVZ0) In order to turn on allocation in the standard order processing functionality, the requirements class must have a flag indicating that allocation is relevant. 7.Activate Allocation for Schedule Line Category (OVZ8) In order to turn on allocation in the standard order processing functionality, the schedule line must have a flag indicating that allocation is relevant 8.Create Planning Hierarchy (MC61) In order to adequately establish allocation quantities, the user must initially determine the level at which the allocation is to take place and the aggregation factor of the allocation quantities. In this step, the levels for the collective allocation search procedure are also identified. 9.Generate Masking Character (OV7Z) Upon completion of the level determination for the planning hierarchy, the collective allocation masking character must be generated to allow aggregation indicators to be established. This transaction simply reads the hierarchy established in the planning table and then generates a collective mask character for each level of the hierarchy 10.Modify Planning Hierarchy (MC62) This step is a repeat of MC61 where the initial hierarchy was established. In order to complete the hierarchical set up, the collective allocation (mask character) hierarchy must now be maintained with the appropriate aggregation factors 11.Allocation Procedure Assignment to Material Master (MM02) At the root level of the allocation process are the materials. Each material that is to be considered in allocation scenario must be mapped to an allocation procedure. In order entry, then, when a material is entered with a valid allocation procedure in the material master, the allocation data is verified prior to confirming the line item ordered 12.List of Suitable Structures (OV9Z) This report is used to identify potential LIS information structures that can be used in the product allocation process. This report simply reads through the data dictionary and selects all the active information structures that contain the field product allocation object (KONOB) as the first field. This data can then be utilized in the mapping transaction (OV3Z) to link the allocation procedure step to an information structure (previous step).