Ansicht
Dokumentation

Merchandise Distribution ( RELNLO_MDS_40CWARVER_ISR )

Merchandise Distribution ( RELNLO_MDS_40CWARVER_ISR )

General Material Data   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Merchandise Distribution

Description

  • General information on Merchandise Distribution
  • Planning merchandise distribution using a collective purchase order
  • Integration of Merchandise Distribution and Allocation
  • Distributing merchandise
  • Automatically adjusting distribution at goods receipt

  • Manually adjusting distribution following goods receipt

  • Automatically triggering subsequent processing at goods receipt

  • Manually triggering subsequent processing following goods receipt

General information on Merchandise Distribution

The Merchandise Distribution functions enable you to manage all the steps in the distribution process from planning to shipping, as smoothly and efficiently as possible. Merchandise can be cross-docked in the distribution center, enabling you to move goods faster through the warehouse and thus reduce the cost of storing and processing them.

Planning merchandise distribution using a collective purchase order

You can plan merchandise distribution using a collective purchase order. A collective purchase order is made up of a selection of issue documents (warehouse orders and/or sales orders) in which all items relevant for a vendor have been determined and aggregated for each material and vendor. Distribution data is kept in the system for each collective purchase order.

Using collective purchase orders is an easy method of grouping together all the recipient requirements that exist in the system in the form of warehouse orders or sales orders in the one purchase order for a vendor (pull-method). The distribution data the system keeps enables you to then coordinate and monitor the distribution of the goods among the recipients.

When collective purchase orders are generated for sales orders, the sales order is blocked with a blocking reason. The blocking reason you use can be entered in Customizing in the step Plant Profiles for Merchandise Distribution.

Make sure that the following Customizing settings are made for the blocking reason:

  • Block for delivery-due list
  • No other blocks set

Integration of Merchandise Distribution and Allocation

If you use allocation tables to plan the movement of merchandise from a vendor to a distribution center and then to a store, the system keeps distribution data on this. This data is then used to adjust distribution after the goods have been received, and to coordinate how the merchandise is distributed in the distribution center.

Once follow-on documents have been generated for an allocation table, the planning phase is complete. All the processes that follow are run in the same way as if you had planned using a collective purchase order.

Distributing merchandise

In distributing merchandise, the distribution center moves merchandise from the goods receipt area to the goods issue area. At goods receipt, a reference is created to the distribution data in the system. You can bring the distribution data into line with the quantities actually delivered either manually or have the system do it for you automatically. The system then generates follow-on documents for picking and shipping, or changes existing documents. You can also trigger subsequent processing manually or have the system do it for you automatically.

The following processing methods are available for distributing merchandise in the distribution center:

Cross-docking enables you to move merchandise through the distribution center without repacking it.

Flow-through enables you to move merchandise that has to be repacked through the distribution center. The goods are repacked after receipt, picked for the recipients in accordance with the distribution data and then transported to the goods issue area.

After goods receipt, distribution data is used to generate deliveries for each recipient. The merchandise is then picked for the deliveries.

In this case, after goods receipt the materials are distributed one after the other among the recipients based on distribution orders. A delivery is generated for every handling unit (such as a pallet) that is filled during picking. Deliveries are thus generated continually during picking.
Storage locations used for merchandise-driven flow-through must be managed in Lean-WM. See the IMG section Lean WM.

When merchandise is being distributed, it may have to be put into storage for a time. You can use this method if merchandise cannot be moved through the warehouse within a few days and has to remain in storage for longer.

You are advised to set up different storage locations for each processing method you use for receiving goods in a plant. You can define default values for the storage locations in Customizing. Please read the IMG section Storage location determination.

  • Automatically adjusting distribution at goods receipt

When goods are received for a purchase order for which distribution data has been maintained in the system, the data has to be updated to reflect the quantities actually delivered (adjusted). You can configure the system so that the system makes this adjustment automatically.
SAP Retail contains standard procedures you can use to adjust a distribution in the case of overdeliveries or underdeliveries. You can also include your own methods of adjustment. You do this in Customizing by assigning a function module you created in the adjustment profile.
See the IMG section Adjustment profiles per processing method.

  • Manually adjusting a distribution following goods receipt

You can configure the system so that the distribution can be adjusted manually online after the goods receipt has been posted.

  • Automatically triggering subsequent processing at goods receipt

You can configure the system so that, after the distribution has been brought into line with the quantities actually delivered at goods receipt, the system automatically triggers subsequent processing. It generates documents for picking and/or shipping, or adjusts existing ones. Depending on the processing method you use, these are either distribution orders or deliveries.
Generating documents at this point rather than at an earlier point has the advantage that the quantities actually delivered are known and do not have to be changed at any point.
A distinction can be made among the following instances:

  • Generation of deliveries

For cross-docking and recipient-driven flow-through, deliveries are generated after the distribution has been adjusted.
This is not the case if you planned using an allocation table, as deliveries without reference are already generated as follow-on documents for the allocation table. Here, these deliveries are used and no new deliveries generated.

  • Generation of distribution orders

For merchandise-driven flow-through, distribution orders are generated after the distribution has been adjusted. Distribution orders are used to coordinate and monitor the distribution of the individual merchandise among the recipients. The deliveries are generated continually as the handling units are filled. This enables the goods to be processed continuously and group different materials in the one delivery for a recipient.

  • Changing existing deliveries.

If you planned distribution using an allocation table and deliveries have already been generated for the allocation table prior to goods receipt, the system automatically adjusts the deliveries in line with the quantities actually delivered.

  • Manually triggering subsequent processing following goods receipt

You can configure the system so that subsequent processing can be started online following the goods receipt posting.

Damage caused to data by errors

Software/hardware requirements

Installation information

Effects on System Administration

Effects on Customizing

See the IMG section

Effect on batch input

Changes to the Interface

Changes in procedure

Procedure for removing dataset errors

Dependent functions

Planning

Further notes






ABAP Short Reference   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 11386 Date: 20240603 Time: 180031     sap01-206 ( 136 ms )