Show TOC Start of Content Area

Process documentation Opportunistic Cross-Docking   Locate the document in its SAP Library structure

Purpose

In the opportunistic cross-docking process, the system generates a cross-docking decision during the process of TO creation ( after the arrival of the incoming stock or release of the outgoing document).

Note

Opportunistic cross-docking involves one-step cross-docking execution only.

 

Prerequisites

...

You have done the following:

       1.      Enabled opportunistic cross-docking in Customizing for Logistics Execution Warehouse Management Cross-Docking General Settings Maintain Warehouse Level Settings

       2.      Defined warehouse movement types as being relevant for cross-docking in Customizing for Logistics Execution Warehouse Management Cross-Docking General Settings Define Cross-Docking Relevancy for Movement Types

       3.      Ensured that the Consider Pre-Alloc. Stock indicator is not set in Customizing for Logistics Execution Warehouse Management Activities Transfers Define Movement Types

       4.      Entered 1 (for inbound documents) or 2 (for outbound documents) in the TO Creation field (Screen Control) for your warehouse in Customizing for Logistics Execution Warehouse Management Activities Transfers Define Movement Types

       5.      Enabled one of the following, in the case of opportunistic cross-docking for inbound documents (HU-managed environment):

¡        Partial posting goods receipt at movement type level in Customizing for Logistics Execution Warehouse Management Interfaces Shipping Define Shipping Control Define Shipping Control at the Movement Type Level (enter 4 in field)

¡        Posting goods receipt before TO creation in Customizing for Logistics - General Handling Unit Management Basics Delivery Define Sequence of Transfer Order – Goods Receipt

       6.      Enabled posting goods receipt before TO creation in Customizing for Logistics - General Handling Unit Management Basics Delivery Define Sequence of Transfer Order – Goods Receipt, in the case of opportunistic cross-docking for outbound documents

       7.      Entered B in the Method field (Blocking logic) for your warehouse in Customizing for Logistics Execution Warehouse Management Master Data Define Control Parameters for Warehouse Number

       8.      Ensured that automatic confirmation is not set (HU-managed environment only) by doing at least one of the following in Customizing for Logistics Execution Warehouse Management Activities Confirmation Storage Type:

¡        Setting the Confirmation putaway indicator for the goods issue storage type (e.g. 916)

¡        Setting the Confirm stck removal indicator for the goods receipt storage type (e.g. 902)

 

Process Flow

 

Inbound Document

Outbound Document

1.

An inbound document is created.

The stock arrives at the goods receipt area (storage type 902) and goods receipt is performed if posting is allowed before TO creation.

An outbound document is released.

2.

You create a putaway TO for each of the document items.

During TO creation, the system checks whether a cross-docking decision already exists for each document item.

3.

If a decision already exists, see step 3 onwards in Planned Cross-Docking.

4.

If a decision does not already exist, the system analyzes whether there are any available cross-docking opportunities.

...

                            a.      The system searches for any open picking TO items from storage to the goods issue area (storage type 916), according to the following criteria:

                                                  i.       TO item status is not confirmed and TO item is not locked by any resource.

                                                ii.       TO item contains the same material, quantity, plant and storage location (usually in terms of full loads) as the putaway TO item to be created.

                                               iii.       The stock category of the TO item is Available Stock.

                            b.      The system evaluates further criteria, such as FIFO and batch requirements.

If a decision does not already exist, the system analyzes whether there are any available cross-docking opportunities:

...

                            a.      The system searches for any open putaway TO items from the goods receipt area (storage type 902) to storage, according to the following criteria:

                                                  i.       TO item status is not confirmed and TO item is not locked by any resource.

                                                ii.       TO item contains the same material and a lower or same quantity as the picking TO item to be created.

                                               iii.       The stock category of the TO item is Available Stock.

                                               iv.       The handling unit (HU) of the TO item is posted (in HU-managed environment only)

                            b.      The system evaluates further criteria, such as FIFO and batch requirements.

5.

If the system finds a suitable picking TO item, it does the following:

...

                            a.      Cancels the picking TO item

                            b.      Creates a putaway TO item to the goods issue area

                            c.      Updates the outbound document, for which the picking TO item was cancelled, with the new cross-docking putaway TO item

If the system finds a suitable putaway TO item, the system does the following:

...

                            a.      Cancels the putaway TO item

                            b.      Creates a picking TO item to the goods issue area, with the source of the cancelled putaway TO item (goods receipt area) as its source

                            c.      Updates the inbound document, for which the putaway TO item was cancelled, with the new cross-docking picking TO item

6.

The newly-created putaway/picking TO item is now connected to both the inbound and outbound documents.

 

End of Content Area