Logistics Execution: Yard Management and Cross-Docking

Delivery Creation

Cross-Docking Decision Creation (Manual) & Location Scheduling

Cross-Dock Decision Creation (Automatic) & Location Scheduling

Exchange of Information with Business Partner

Check-In of Pre-Scheduled Vehicle

Check-In of Unscheduled Vehicle

Movement of Vehicle Directly to Scheduled Door

Movement of Vehicle to Parking Space and Then Door

Unloading or Loading and Check-out of Vehicle

 One-Step Cross-Docking Execution

Two-Step Cross-Docking Execution

Vehicle-Document Assignment and Location Scheduling

Movement to Door and Loading of Empty Vehicle

Pick-Up of Trailer by Vehicle

Defining Cross-Docking Relevancy for Movement Types

Procedure

Navigation

Menu path Transa

Customizing for Logistics Execution Warehouse Management Cross-Docking General SPRO

Settings Define Cross-Docking Relevancy for Movement Types

1. Set the CD Relevant indicator for the following warehouse movement types:

Movement Type Description

101 Goods receipt for pur.or.

255 GI general

501 GR without purchase order

601 GI to delivery note

Delivery Creation
Purpose

The starting point of each scenario variant is the creation of an inbound

and outbound delivery with matching materials and quantities.

Process Flow
1. After receiving details from the Business Partner picking up the
goods pursuant to the outbound delivery, an office worker creates an
outbound delivery in SAP R/3 Enterprise Shipping.

2. The manager assigns an empty vehicle ( transport equipment,

such as a trailer), currently in your yard, to the outbound delivery
(variant 2 only).
 3. A worker creates a picking transfer order (TO) for the outbound
delivery (variant 3 only).

4. After receiving details from the Business Partner delivering the

goods pursuant to the inbound delivery (such as via ASN), the office
worker creates an inbound delivery in SAP R/3 Enterprise Shipping.

Cross-Docking Decision Creation (Manual) & Location Scheduling

Purpose

You can manually link the item of the inbound delivery to the item of the
outbound delivery so as to create a cross-docking decision.

The creation of the decision includes scheduling of both the inbound and
outbound doors for the vehicles to be unloaded and loaded, pursuant
to cross-docking execution.

Process Flow
1. Using the cross-docking planning tool in SAP R/3 Enterprise
Cross-Docking, the manager manually links the item of the inbound
delivery with the item of the outbound delivery.

2. SAP R/3 Enterprise Yard Management checks if locations can be

scheduled for the inbound and outbound deliveries, and reports the
results to SAP R/3 Enterprise Cross-Docking.
 3. If locations can be scheduled, the manager saves the cross-
docking plan to create the cross-docking decisions in SAP R/3
Enterprise Cross-Docking.

4. For each decision, doors are scheduled in SAP R/3 Enterprise

Yard Management for dummy vehicles created and assigned to the
deliveries.

5. The deliveries are updated with the scheduled doors in SAP R/3
Enterprise Shipping.

Cross-Dock Decision Creation (Automatic) & Location Scheduling

Purpose

You can force the system to create its own cross-docking decisions,
based on an optimization algorithm, linking the items of inbound deliveries
to items of outbound deliveries, so as to create one or more cross-docking
decisions.

Assuming that the system creates a cross-docking decision linking the

inbound delivery item with the outbound delivery item, you will then have
to manually schedule locations for the decision via the cross-docking
monitor.

Process Flow

1. The manager opens the cross-docking monitor in SAP R/3

Enterprise Cross-Docking, and executes planning in the background.
 2. The system creates decisions based on an optimization
algorithm. In this case, a decision linking the items of the created
inbound and outbound deliveries is created.

3. After the decision is created, the manager attempts to

schedule locations for the decision (via the Schedule cross-docking
monitor method). Assuming scheduling is possible, SAP R/3 Enterprise
Yard Management does the following:

Assigns a dummy vehicle to the inbound delivery and

schedules a location for it

Schedules a location for the vehicle that you already assigned

to the outbound delivery

4. The deliveries are updated with the scheduled doors in SAP R/3
Enterprise Shipping.

One-Step Cross-Docking Execution

Purpose

After the delivery is unloaded and the goods are placed in the relevant
staging area, you post goods receipt and the system creates a cross-
docking decision pursuant to opportunistic cross-docking. You execute
cross-docking in one-step, resulting in the goods being placed in the
outbound staging area (storage type 916), awaiting loading and subsequent
pick-up by the outbound delivery Business Partner.

Process Flow
1. A worker posts goods receipt for the unloaded goods in the
staging area (storage type 902) in SAP R/3 Enterprise Warehouse
Management System.
 2. The worker creates a putaway transfer order (TO) for the inbound
delivery item.

3. During TO creation, SAP R/3 Enterprise Cross-Docking searches

for any open picking TO items from storage to the goods issue area
(storage type 916) that contain the same material, quantity, plant and
storage location as the putaway TO item to be created, as well as
other criteria.

The system identifies the previously created picking TO for the

outbound delivery.

4. The system cancels the picking TO item from storage to 916, and
creates a putaway TO item from storage type 902 to storage type 916.

5. A worker move the goods to storage type 916 and confirms the
TO, in SAP R/3 Enterprise Warehouse Management System.

Two-Step Cross-Docking Execution

Purpose

After the delivery is unloaded and the goods are placed in the relevant
staging area, you post goods receipt and execute two-step cross-docking.
This results in the goods being placed in the outbound staging area
(storage type 916), awaiting loading and subsequent pick-up by the
outbound delivery Business Partner.

Process Flow
1. A worker posts goods receipt for the unloaded goods in the
staging area (storage type 902) in SAP R/3 Enterprise Warehouse
Management System.

2. The worker creates a putaway transfer order (TO) for the inbound
delivery item.

During TO creation, SAP R/3 Enterprise Cross-Docking fetches the

previously created decision according to the document item, and
determines the destination as the cross-docking storage type.

3. A worker moves the goods to the cross-docking storage type and

confirms the TO, in SAP R/3 Enterprise Warehouse Management
System.

4. A worker creates a picking TO for the outbound delivery item.

SAP R/3 Enterprise Cross-Docking automatically determines the

source of the TO as the cross-docking storage type.

5. The worker move the goods to storage type 916 and confirms the
TO, in SAP R/3 Enterprise Warehouse Management System.