101311601EWM/SCWM/PRDI/SCWM/PRDOadvanced

EWM Opportunistic Cross-Docking: From Goods Receipt Straight to Goods Issue

Goods arriving on an inbound delivery are needed by an open outbound delivery. Instead of putting them away and picking them again, EWM routes the needed quantity straight from the goods-receipt zone to the goods-issue zone; only the rest is put away.

Educational content. SAP behaviour varies by configuration and release. Spotted something off? Report it.

Docs

Demo data

01An outbound delivery is waiting

Outbound delivery 80000480 needs 40 EA of FG-2000 today. There is none in the warehouse.

Business scenario

100 EA of FG-2000 arrive from Demo Supplier Ltd. An outbound delivery for 40 EA to Demo Retail Pvt. Ltd. is waiting with no stock in the pick face. EWM sends 40 EA directly to door 05 and puts the remaining 60 EA away.

All companies, numbers and documents are fictional demo data.

Step-by-step flow

01
An outbound delivery is waiting open in twin
Outbound delivery 80000480 needs 40 EA of FG-2000 today. There is none in the warehouse.
This open demand is what opportunistic cross-docking looks for when goods arrive.
02
Goods arrive and are received (101) open in twin
The truck docks, 100 EA are unloaded and goods receipt is posted into ROD.
Cross-docking does not change how goods are received; it changes where they go next.
03
Where do the 40 EA go? open in twin
100 EA are in the goods-receipt zone. 40 EA are needed at door 05 today.
Every bin-to-bin move is labour. Moving goods to a rack only to fetch them back an hour later is waste.
04
Two moves instead of one open in twin
Putting the 40 EA away and picking them again doubles the handling and delays the customer's truck.
But the 40 EA travel GR zone → rack → GI zone instead of GR zone → GI zone: two tasks, two forklift trips, and the outbound wave waits for both.
05
Cross-dock 40 EA to the goods-issue zone open in twin
Task 100000901 moves 40 EA from GR-ZONE to GI-ZONE. Their stock type changes to available (ROD → AFS).
The goods skip storage entirely. Only the quantity actually needed is cross-docked.
06
Put the remaining 60 EA away open in twin
Task 100000902 puts 60 EA into RACK-01-03.
Cross-docking splits a receipt: what is needed now passes through, what is not is stored.
07
Load and post goods issue (601) open in twin
40 EA are loaded at door 05 and goods issue is posted. The customer's truck leaves the same day the goods arrived.
No picking task from storage was needed — the cross-docking task already brought the goods to the goods-issue zone.
08
Cross-docking complete open in twin
In: 100 EA. Out the same day: 40 EA. Stored: 60 EA. One storage step skipped.
The accounting is unchanged — a receipt and an issue — but the warehouse saved a putaway and a pick.

SAP documents

Drag to pan · Ctrl + scroll to zoom

Stock impact

Step	Plant / SLoc	Stock type	MvT	Change
Goods arrive and are received (101)	1000 / ROD · GR-ZONE	Unrestricted use	101	+100 EA
Cross-dock 40 EA to the goods-issue zone	1000 / ROD · GR-ZONE	Unrestricted use	311	−40 EA
Cross-dock 40 EA to the goods-issue zone	1000 / AFS · GI-ZONE	Unrestricted use	311	+40 EA
Put the remaining 60 EA away	1000 / ROD · GR-ZONE	Unrestricted use	311	−60 EA
Put the remaining 60 EA away	1000 / AFS · RACK-01-03	Unrestricted use	311	+60 EA
Load and post goods issue (601)	1000 / AFS · GI-ZONE	Unrestricted use	601	−40 EA

Accounting impact

Goods receipt for a purchase order

Typical

Goods arrive and are received (101)

Dr Inventory — trading goods (BSX)₹1,20,000
Cr GR/IR clearing (WRX)₹1,20,000

Standard PO receipt: inventory against GR/IR clearing. In this demo the PO price equals the standard price, so there is no price difference.

Goods issue for a sales delivery

Typical

Load and post goods issue (601)

Dr Cost of goods sold (GBB/VAX)₹48,000
Cr Inventory — trading goods (BSX)₹48,000

Standard sales goods issue: inventory value to cost of goods sold.

Typical conceptual flow. Actual G/L accounts and posting behaviour depend on material valuation, automatic account determination and system configuration.

Movement type

101GR for purchase orderReversal: 102
311Transfer ROD → AFS (typical mapping)Reversal: 312
601GI for deliveryReversal: 602

Shortens lead times and cuts handling by passing incoming goods directly to waiting outbound deliveries instead of storing and picking them.

Transactions & Fiori apps

/SCWM/PRDI — Maintain Inbound Delivery
/SCWM/PRDO — Maintain Outbound Delivery Order
/SCWM/TO_CONF — Confirm Warehouse Task
/SCWM/MON — Warehouse Management Monitor

Warehouse Monitor

Differences by SAP version

Classic WM offered cross-docking only in limited form; EWM is the target solution.

Configuration

Opportunistic cross-docking (EWM-triggered)
Configuration dependent
Activated per warehouse process type; EWM checks for open outbound demand when creating putaway tasks.
Planned cross-docking
Configuration dependent
An alternative where the cross-docking route is planned in advance (e.g. transportation cross-docking or merchandise distribution).
Stock type change at cross-docking
Configuration dependent
How cross-docked stock becomes available for the outbound delivery.

Prerequisites

Opportunistic cross-docking activated for the warehouse and process type
Open outbound delivery order for the product when the putaway task is created
Goods-receipt and goods-issue staging areas

Master data

Product (EWM views): Must be extended to the warehouse for both inbound and outbound processing.

Organizational structure

Warehouse EW01
Storage locations ROD and AFS
Doors 01 and 05

Tables

Table	Description
/SCWM/ORDIM_C	Confirmed cross-docking and putaway tasks
/SCDL/DB_PROCH_I / _O	Inbound and outbound delivery headers
MATDOC	101, 311 and 601 postings

Integration

MMGoods receipt and storage-location transfers.
SDThe outbound delivery being served.
FIReceipt and issue are valuated exactly as without cross-docking.

Common errors

“Goods are put away even though an outbound delivery was waiting”
Likely causes: Opportunistic cross-docking not active for the process type; Outbound delivery created after the putaway task; Outbound delivery already assigned to other stock
Where to look: Process type settings · Timing of task creation vs delivery creation · Warehouse monitor

Troubleshooting

Something went wrong? Work through these checks in order. They are diagnostic questions, not configuration instructions — confirm changes with your system owner.

CHECK 1
No cross-docking
- Is opportunistic cross-docking active?
- Was the outbound delivery open when the putaway task was created?

Interview questions

What is opportunistic cross-docking in EWM?
EWM-triggered cross-docking: when it creates a putaway task for received goods, it checks for open outbound delivery demand for the same product and, if found, creates a task to the goods-issue zone for the needed quantity instead of to storage. The rest is put away normally.
Does cross-docking change the accounting?
No. The goods are still received (101) and issued (601) with the usual postings. Cross-docking only changes the warehouse moves in between.
What is the difference between opportunistic and planned cross-docking?
Planned cross-docking is decided before the goods arrive — the route through the warehouse is known in advance. Opportunistic cross-docking is decided by EWM at the moment of putaway, based on whatever outbound demand is open then.

Quiz

Q1 · Multiple choice

What triggers opportunistic cross-docking?

Open outbound demand when the putaway task is createdA flag on the purchase orderAn MRP exceptionA full reserve bin

Q2 · Put in order

Put the cross-docking flow in order.

1Goods receipt (101)
2Cross-docking task to the GI zone
3Goods issue (601)

Q3 · Identify the accounting impact

How does cross-docking change the accounting compared with putaway and picking?

It does not — the receipt and the issue post as usualGoods receipt is skippedReceipt and issue are netted into one postingStock is posted to in-transit

References

SAP SE — SAP Help Portal: Cross-Docking in EWM (source)
SAP SE — SAP Help Portal: Opportunistic Cross-Docking (source)
SAP SE — SAP Help Portal: Warehouse Process Types (source)

Explanations are original. They summarize standard behaviour; always validate against your system's release and configuration.

Version history

Version	Change
1.0.0	Initial version.