Single-Store Vendor Order 

Use

Seasonal Procurement supports a single-level cross-docking procedure with prepacking, in which exactly one external vendor order is generated for each store. (This is referred to as the CDP process in the following.) This procedure simplifies goods movement in the distribution center (DC). At the same time, it increases the number of purchase orders in the system as the requirements of different stores can no longer be grouped together, for example, in a collective purchase order.

This process runs according to the push principle, in which assortment planning defines the order quantities for external procurement. The system uses the collective number to recognize the articles that are relevant for this process and distinguish them from vendor orders that are processed in the standard way without a cross-docking procedure with prepacking.

Seasonal Procurement also supports single-store purchase orders that are generated from the allocation table or using the collective purchase order. For more information, see Single-Recipient POs from Allocation Table and Collective PO.

Prerequisites

The following prerequisites should be pointed out:

·        You use cross-docking with prepacking in purchase order processing and have created a distribution profile for the cross-docking process in the article master in the Distribution Center view.

·        You have configured the CDP process in Customizing for Seasonal Procurement under PO Processing → General Settings → Maintain Creation of Single-Store Purchase Orders.

·        You have assigned additionals to the article including the method SLS: Pre-Packing in the article master (for example, in transaction MM42) under Additional Data.

·        In the vendor master, the Cross-Docking - Relevant for Collective Numbering indicator is set for the relevant vendors.

·        An additionals article must be assigned to the article to be procured. This is a dummy article in the CDP process.

Process Flow

...

       1.      Operational assortment planning and control (OAPC) generates a price-shop report that contains the following data:

¡        DC and store plus distribution data (this indicates which quantities of which articles are planned for which store.)

¡        Vendor ID

¡        Collective number

       2.      The order list copies the data from the price-shop report and uses the collective number to check whether you are using the standard process or the process described here for vendor orders with cross-docking with prepacking.

The order list groups the items into grouped purchase order documents (GPOD) or purchase orders according to the grouping criteria (for example, store and collective number).

       3.      The system generates a grouped purchase order document for each store. These all have the same collective number (header characteristic). Depending on the criteria used, the grouping process can also generate several GPODs for the same store.

A purchase order item with an order quantity of 1000 is processed as follows, for example:

Collective Number	Order Number	Order Item	Distribution Center	Store	Quantity
00001	12301	10	DC1	Store1	200
00001	12302	10	DC1	Store2	500
00001	12303	10	DC1	Store3	300

 

       4.      Once the grouped purchase order document has successfully passed the OTB check, the system generates a vendor order for each store. These vendor orders can contain any number of article items that are relevant for the cross-docking process with prepacking.

It is possible to change the document then with regard to quantity, unit of measure, price, and delivery date.

       5.      The system generates stock transport orders from the normal purchase orders so that the goods can be delivered to the stores.

Constraints

·        A mass change of prices in all single-store vendor orders is not possible.

·        The cross-docking process with prepacking is only intended for planned procurement items and not for items that were manually added to the order list, the grouped purchase order document, or the purchase order.

·        An allocation table cannot be generated for single-store vendor orders that were created using this process, nor is subsequent distribution possible.

·        There is no synchronization between the single-store external purchase order and the stock transport order.

·        The stock transport orders created by the process each use the same quantity and unit of measure as the associated normal purchase order. There can therefore be no quantity optimization with regard to the stock transport order.

·        The document items always contain only one schedule line.

·        All store orders in a group must contain identical data for the distribution center, purchasing organization, company code, and document type.

·        In the case of generic articles, the single-store external purchase order only contains items for variants, not for the header articles.

See also:

Functions of the Single-Store Vendor Order