Wave Planning and Picking Strategy Design for Outbound Deliveries

Explanation

Wave planning is the mechanism that groups outbound deliveries into a single releasable unit of work so that picking, packing, and loading can be executed efficiently within a shift or transportation cutoff. In ECC WM, this is typically handled through the wave pick concept combined with transfer order creation rules and print-relevant grouping; the logic is simpler and often supplemented by custom sorting programs. In Embedded and Decentralized EWM, wave management is a dedicated object: wave templates define selection criteria (delivery priority, ship-to, route, carrier, product group, storage area), grouping rules (how many deliveries or how much volume/weight per wave), and release rules (time-based, capacity-based, or manual). Understanding this distinction matters because a consultant configuring wave templates in EWM without understanding the business cutoff and dock schedule will create waves that either starve the dock or overload pickers at shift start. Picking strategy design sits underneath wave planning. Storage type search strategies define where pick tasks are generated from: fixed bin picking, bulk storage picking with quantity-based rounding, or wave-controlled batch/FIFO-driven picking. In EWM, Warehouse Process Types (WPTs) and storage type indicators drive whether a pick creates a single warehouse task or splits across multiple source bins when the primary bin lacks full quantity. A key intermediate-level skill is configuring picking area and activity area assignments so that pick tasks route through RF-optimized paths rather than jumping randomly across the warehouse floor -- this materially affects picker productivity and is a very common client complaint when misconfigured. Runtime flow: delivery creation (or delivery due list processing) triggers wave assignment based on template matching, the wave is released manually or automatically, warehouse tasks (or transfer orders in WM) are created against the wave, and RF users confirm picks against those tasks. If a wave fails to release because deliveries have blocked stock, incomplete batch determination, or missing HU requirements, the wave sits in an incomplete or open status and must be diagnosed. Common troubleshooting starts with checking whether all deliveries in the wave meet the release prerequisites (stock availability, no delivery block, capacity check passed) and whether the wave template's grouping criteria actually matches the delivery population expected -- a frequent root cause of 'wave never fills' issues is overly narrow grouping criteria that no combination of daily order volume satisfies. On S/4HANA embedded EWM, wave functionality is largely the same as decentralized EWM since it runs on the same code line, but system landscape differences affect how master data (e.g., route, shipping point) synchronizes with the wave template's selection fields -- delays in delivery replication in decentralized landscapes can cause waves to be built against stale data. Performance-wise, very large wave templates with broad selection criteria can create long-running background jobs; splitting wave runs by shipping point or by hourly batch job schedules is a standard scaling practice in high-volume distribution centers.

Code example

* Illustrative EWM-style wave template logic (conceptual, not literal config path)Wave Template: WT_EXPRESS_AM Selection Criteria:   Delivery Priority = High   Route = EXPRESS*   Shipping Point = 1710 Grouping Rule:   Max Deliveries per Wave = 40   Max Total Weight = 800 KG Release Rule:   Type = Time-based   Release Time = 06:00, 09:00, 12:00   Fallback = Manual release if capacity check fails * Picking strategy note (conceptual): Storage Type Search Sequence for Pick:   1. Fixed Bin (FIFO by GR date)   2. Bulk Storage (round to full pallet if remainder < 10%)   3. Overflow/Reserve storage (manual task creation, supervisor alert)

Real project scenario

A retail distribution center on Decentralized EWM found that its 'Express AM' wave consistently released only 5-8 deliveries instead of the expected 40, delaying the 06:00 truck loading window. Investigation showed the wave template's route selection field used an exact match 'EXPRESS-01' instead of a wildcard pattern, so orders routed through newly added 'EXPRESS-02' and 'EXPRESS-03' lanes (introduced after a carrier network change) were excluded. The fix involved correcting the selection pattern and adding a monitoring alert comparing expected vs actual wave delivery counts each morning.

Common mistakes

• Assuming wave planning in ECC WM behaves identically to EWM wave management; the underlying objects and flexibility differ significantly. • Defining wave templates with selection criteria so narrow that daily order volume never satisfies grouping thresholds, causing waves to sit unreleased. • Ignoring capacity checks (dock, picker headcount) when setting automatic time-based release rules, leading to floor congestion. • Not aligning picking area/activity area sequencing with actual warehouse layout, resulting in inefficient picker travel paths. • Failing to monitor wave completion status, so partially picked waves silently miss loading cutoffs.

Best practices

• Design wave templates around actual daily order volume patterns, validated with historical delivery data before go-live. • Build monitoring reports comparing planned vs actual wave fill rates and investigate deviations daily during hypercare. • Align picking strategy storage type sequences with physical warehouse layout and confirm with a walkthrough, not just paper design. • Use manual release fallback for waves tied to variable capacity constraints (e.g., seasonal peak) rather than rigid time-based rules alone. • Document wave template selection logic in plain business terms so operations supervisors can self-diagnose fill issues without IT involvement.

Interview angle

Interviewers often ask candidates to explain the difference between wave-based and delivery-based (non-waved) processing, and to describe how they would design a wave template for a scenario with mixed priority orders and tight dock schedules. Be ready to discuss trade-offs between automatic time-based release and manual supervisor-triggered release, and how you would diagnose a wave that consistently under-fills.