Skip to Content
Author's profile photo Sridhar Jayavarapu

Overview on Allocation Table process

Allocation Table process:

I would like to share some knowledge about to process Allocation table required configuration and creating follow-on documents from Allocation Table.

Use of Allocation Table:

Allocation Tables are one of the retail functionalities which support ‘Push’ processes used to centrally distribute articles among a large number of stores.  This is commonly used for promotional activities, fashion articles, and article introduction.

Allocation table supports the following scenarios:

  • Articles directly delivered from the Vendor to stores.
  • Articles delivered directly from the vendor to the distribution centres and then ‘immediately’ to the stores.
  • Allocation table is fully integrated with SAP Cross-Docking and Flow Through functionalities. All scenarios are fully integrated with SAP Consignment, SAP Returns, and SAP Promotion functionalities.

Allocation table also offers various ways to split the stock among different sites.  It can be done manually, with pre-defined Allocation Rules, or based on historical sales (Allocation Strategies):

Manual Split:  Sites and quantities are manually specified.

Site Groups:  Standard site groups can be included in order to have the system proposing the sites. Then, quantities can be manually split.

Recipient Determination:  By specifying the distribution centre, the system can propose all the stores that are supplied by that distribution centre. Then, quantities can be split.

Allocation Rule: This is a separate object that contains the sites and the proportion of the merchandise each is to receive.  Once used in the Allocation Table, the system proposes the receiving sites and quantities are automatically split based on the quotas.

Allocation Strategy:  This option is an alternative to Allocation Rules and works together with Site Groups and Recipient Determination options.  It also works for sites that have been manually entered.  It allows specific requirements to be met in the allocation process through the use of different allocation algorithms:

  • Equal allocation: The allocation item quantity is split up equally among all the sites.
  • Replenishment: Allocation based on a simplified stock check. The maximum stock level in the Article Master is compared with the SOH (Stock -On-hand) in the receiving site and the planned quantity to be ordered / delivered is calculated from the difference.
  • Returns: It determines the SOH in the stores and enters this as the planned quantity for the receiving sites. This is not required for Produce and Petrol.
  • BW – Quotas: The strategy accesses the sales history available in SAP BW, and returns a quota for each site.
  • BW – Top Down: The planned quantity for the article is manually specified, and then the strategy provides planned quantities for the receiving sites based on the sales history available in SAP BW.
  • BW – Bottom Up: The strategy accesses the sales history available in SAP BW, and returns the planned quantity for each site.  The planned quantity for the article is the result of the cumulated quantities of the receiving sites.


Allocation table creation WA01

Generating Follow –On Documents WA08

Allocation Table configuration:

Configuration Path:

Define Item Category:

SPRO -Logistics – General-Merchandise Distribution-Allocation- Item Categories of Allocation Table

Define Item Categories.JPG

Define Allocation Table Type  :

SPRO -Logistics – General Merchandise Distribution AllocationAllocation Table Types

Allocation Table types.JPG

Allocation Table Creation process :

Transaction WA01

Allovcation Table Creation 1.JPG

Store quantities

Store Quantities.JPG

Checking Errors

Allocation Table Creation.JPG

Follow On documents Generation through WA08 transaction

Vendor Purchase Order Creation

wa08 1.JPG

wa08 2.JPG

wa08 3.JPG

Vendor Purchase Order

wa08 4.JPG

Store Stock Transport Orders generation

wa08 5.JPG

wa08 6.JPG

wa08 7.JPG

Based on selection parameter in WA08 ether we can create  Vendor Seasonal Purchase Order or  Vendor Classic Purchase Order.


We can split Warehouse orders based on below selection parameters.

wa08 8.JPG

Hope this document helpful.

References :

Allocation: Allocation Strategy (SAP Library – SAP´┐ŻRetail)

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Joao Sousa
      Joao Sousa

      How does this integrate with the WM cross-docking decisions? I have an allocation table, both purchase orders and deliveries are created.

      Cross-docking is configured and working fine for planned and opportunistic cross-docking, and picking for deliveries is getting the pallets from the corresponding inbound deliveries.

      For allocation tables this is not working. When I pick the delivery, the TO gets the warehouse storage instead of the pallets waiting in the 902 interface. As far as I can see this happens because there isn't cross docking decision linking the inbound and outbound documents.

      Author's profile photo Sridhar Jayavarapu
      Sridhar Jayavarapu
      Blog Post Author

      Sorry Joao,We are using third party Warehouse System not .SAP warehouse management.In our case the goods receipts happen against inbound delivery then they will split the qty and distribute to each stores through Outbound delivery.