EWM Two-Step Picking: One Withdrawal for the Wave, Then Allocation per Delivery into Handling Units
Instead of walking to the same bin once per delivery, the picker withdraws the wave's total in one trip (step 1) to an intermediate work center, where it is split per delivery and packed into handling units (step 2). Pick-pack-pass and warehouse order rules are explained alongside.
Educational content. SAP behaviour varies by configuration and release. Spotted something off? Report it.
Digital twin
01Release the wave
Wave 4200: two deliveries, 30 + 20 EA of FG-2000, both from RACK-01-03.
Business scenario
The morning wave has two deliveries of FG-2000: 30 EA for Demo Retail and 20 EA for Demo Wholesale. Both come from rack bin RACK-01-03.
All companies, numbers and documents are fictional demo data.
Step-by-step flow
- 01
Release the wave open in twin
Wave 4200: two deliveries, 30 + 20 EA of FG-2000, both from RACK-01-03.
Grouping is what makes it possible to pick the same product once for several deliveries.
- 02
How should the picker work? open in twin
Two deliveries need the same product from the same bin. How should picking be organised?
It pays off when many deliveries need small quantities of the same products.
- 03
Twice to the same bin open in twin
Two tasks, two trips to RACK-01-03. With 200 deliveries a wave, single-step picking multiplies travel in the high-rack aisles.
For many small deliveries, travel time dominates — that is what two-step picking removes.
- 04
Step 1: one withdrawal for the wave open in twin
Withdrawal task: 50 EA from RACK-01-03 to WORKCTR-SORT in one trip.
Its quantity is the wave's total for the product.
- 05
Step 2: allocate and pack per delivery open in twin
At the work center the stock is split: 30 EA into HU 1, 20 EA into HU 2, both moved to GI-ZONE.
From here each HU is tracked as one unit to the customer.
- 06
Load and post goods issue open in twin
Both HUs are loaded and goods issue is posted for both deliveries: cost of goods sold ₹60,000.
Two-step picking changes the internal moves only; SD and FI see normal deliveries.
- 07
Wave shipped open in twin
One withdrawal, two allocations, two HUs, two goods issues.
Warehouse order creation rules decide how tasks are bundled for each worker — by zone, quantity, volume or pick path.
SAP documents
Stock impact
| Step | Plant / SLoc | Stock type | MvT | Change |
|---|---|---|---|---|
| Step 1: one withdrawal for the wave | 1000 / AFS · RACK-01-03 | Unrestricted use | — | −50 EA |
| Step 1: one withdrawal for the wave | 1000 / AFS · WORKCTR-SORT | Unrestricted use | — | +50 EA |
| Step 2: allocate and pack per delivery | 1000 / AFS · WORKCTR-SORT | Unrestricted use | — | −50 EA |
| Step 2: allocate and pack per delivery | 1000 / AFS · GI-ZONE | Unrestricted use | — | +50 EA |
| Load and post goods issue | 1000 / AFS · GI-ZONE | Unrestricted use | 601 | −50 EA |
Accounting impact
Goods issue for two deliveries
TypicalLoad and post goods issue
- Dr Cost of goods sold (GBB/VAX)₹60,000
- Cr Inventory — finished goods (BSX)₹60,000
Each delivery posts its own 601; shown together here.
Typical conceptual flow. Actual G/L accounts and posting behaviour depend on material valuation, automatic account determination and system configuration.
Movement type
- 601GI for deliveryReversal: 602
Cuts travel time in storage by picking each product once per wave and distributing it to deliveries at a work center.
Transactions & Fiori apps
- /SCWM/WAVE — Maintain Waves
- /SCWM/RFUI — RF Framework
- /SCWM/PACK — Packing
- /SCWM/PRDO — Outbound Delivery Order
- /SCWM/MON — Warehouse Monitor
- Warehouse Monitor
Differences by SAP version
Classic WM also offered two-step picking with transfer orders, with fewer options.
Two-step picking and pick-pack-pass are EWM features in embedded and decentralized EWM.
Availability depends on the EWM scope.
Configuration
Two-step picking relevance
Configuration dependentSet per warehouse and storage type; products picked from those storage types in a wave are withdrawn in two steps.
Warehouse order creation rules
Configuration dependentBundle tasks into warehouse orders by zone, limits and sorting.
Pick-pack-pass
Configuration dependentHU passes through pick zones in sequence; configured through warehouse order creation and work centers.
Prerequisites
- Two-step picking relevance for the product and storage type
- Intermediate work center / storage type for allocation
- Wave management
Master data
- Packaging specification
- How allocated quantities are packed.
Organizational structure
- Warehouse EW01
- Storage location AFS
Tables
| Table | Description |
|---|---|
| /SCWM/WAVEHDR | Waves |
| /SCWM/WHO | Warehouse orders |
| /SCWM/ORDIM_C | Withdrawal and allocation tasks |
Integration
- SDDeliveries and goods issue.
- FICOGS at goods issue.
Common errors
“Deliveries picked in one step despite setup”
Likely causes: Products not released in a wave; Storage type not two-step relevant
Where to look: Wave status · Two-step relevance settings
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
Two-step
- Is the wave released?
- Is the storage type two-step relevant?
Interview questions
What is two-step picking in EWM?
Step 1 withdraws the total quantity a wave needs of a product from storage to an intermediate area in one task, independent of deliveries. Step 2 allocates that stock to the individual deliveries (and packs it). It reduces trips to storage when many deliveries need small quantities of the same product.
What is pick-pack-pass?
A picking method where a handling unit travels through several pick zones; each zone's picker adds their items and passes it on, so the HU arrives complete without a separate consolidation step.
Quiz
References
- SAP SE — SAP Help Portal: Two-Step Picking (source)
- SAP SE — SAP Help Portal: Warehouse Order Creation (source)
- SAP SE — SAP Help Portal: Handling Units in EWM (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. |