Configuring Picking Strategies and Wave/Group Processing

Explanation

Once the fundamentals of picking documents are understood, the next layer of complexity is controlling which bin the system proposes for a pick and how multiple deliveries are batched together for efficient execution. This is governed by picking strategies (in ECC WM) or storage type/process configuration combined with wave management (in EWM and S/4HANA). In ECC WM, picking strategy is configured at the storage type level via the storage type search strategy indicator combined with the picking strategy indicator on the storage type record. Common approaches include First-In-First-Out (FIFO) based on stock placement date, Last-In-First-Out in rare cases, fixed bin picking where a designated pick face is always used, and quantity-based strategies where the system searches partial-quantity bins before full bins to consolidate open quantities. These strategies are assigned per storage type, and the system evaluates them during TO creation based on the source storage type search sequence defined for the movement type and storage type combination. In EWM, similar outcomes are achieved through a combination of storage type search configuration, quantity classification, and stock removal strategies configured within the warehouse product master and storage type definitions. EWM's Process-Oriented Storage Control (POSC) allows different physical process steps (like pick, pack, and quality check) to be sequenced explicitly per warehouse process type, which is more flexible than the WM approach of implicit sequencing through movement types. Wave management is the mechanism for grouping multiple deliveries or delivery items into a single release for picking, aiming to optimize picker travel time and equipment usage. In ECC WM, this is typically handled at the delivery grouping level combined with background TO creation jobs that consolidate multiple deliveries by route, ship-to zone, or shipping condition. In EWM, waves are a first-class object: a wave template defines selection criteria (delivery priority, ship-to region, carrier) and grouping/optimization rules, and wave release converts warehouse requests into warehouse tasks in a controlled, schedulable manner. This allows warehouses to release picking work in planned batches aligned to truck departure times or shift capacity, rather than picking every delivery immediately upon creation. Group processing, in contrast, is a simpler batching mechanism where multiple TOs are combined under one group number for printing or RF processing convenience, without the sophisticated optimization logic of EWM waves. This distinction matters when advising clients: a WM shop asking for 'wave-like' functionality is often better served by combining group processing with background job scheduling, whereas true dynamic wave optimization (based on real-time capacity, carrier cutoff times, or resource availability) generally requires EWM. Configuration decisions here directly affect key performance indicators: pick density (items picked per travel distance), pick accuracy, and dock-to-stock or order-to-ship cycle time. A poorly designed strategy—for example, always picking from full pallets when a pick face storage type exists—leads to excessive travel and bin depletion issues. Conversely, over-engineering wave templates with too many small waves can create excessive system overhead and confuse floor supervisors. Testing picking strategy changes requires running representative sample deliveries through TO/WT creation in a test client, verifying the proposed source bins align with expectations, and checking that stock removal respects any batch management or shelf-life requirements configured on top of the base picking strategy.

Code example

Example: ECC WM storage type search sequence (conceptual, illustrative only) Movement Type: 601 (Goods Issue for Delivery)Storage Type Search Sequence for Plant/Warehouse combination:  Sequence 1: Storage Type 010 (Fixed Pick Face) - Strategy: Fixed Bin  Sequence 2: Storage Type 020 (Bulk Reserve) - Strategy: FIFO by placement date  Sequence 3: Storage Type 030 (High Rack Random) - Strategy: Quantity-based (partial bins first) System logic during TO creation:1. Check Storage Type 010 for the material's fixed bin assignment2. If insufficient quantity, check Storage Type 020 applying FIFO3. If still insufficient, check Storage Type 030 for partial-quantity bins before full pallets Note: exact indicator names and configuration transaction paths vary by system and should be verified against the client's actual customizing rather than assumed from this illustrative example.

Real project scenario

An EWM implementation team was asked to reduce picker travel time in a distribution center handling both large-volume and small-volume orders. The initial wave template grouped all deliveries by ship date only, causing pickers to walk long distances between scattered small orders and bulk pallet picks in the same wave. The team redesigned wave templates to separate small-item pick-face waves from bulk pallet waves, releasing them on different schedules aligned to different resource groups (RF pickers vs forklift operators), which measurably reduced average pick travel distance and improved dock loading punctuality.

Common mistakes

• Configuring a single storage type search sequence for all movement types without considering that returns or internal transfers may need different logic • Building overly granular wave templates that fragment picking work and increase administrative overhead • Failing to align wave release timing with actual dock/truck schedules, causing picked stock to sit idle in staging • Ignoring batch/shelf-life determination when only focusing on bin-level FIFO logic, risking expired stock shipment • Assuming EWM wave templates and ECC WM group processing are interchangeable concepts during blueprint discussions

Best practices

• Segment wave templates or group processing rules by resource type (RF picker, forklift, pick-to-cart) to reduce mixed-mode travel inefficiency • Align wave release scheduling with actual carrier cutoff and dock appointment times rather than releasing immediately on order creation • Validate picking strategy changes with representative sample orders in a test environment before production cutover • Coordinate picking strategy design with slotting/bin replenishment processes so pick faces are consistently stocked • Document storage type search sequences and picking strategy indicators clearly for support teams, since misconfiguration here is a common root cause of picking errors

Interview angle

Expect questions distinguishing WM picking strategy configuration (storage type search plus picking strategy indicator) from EWM wave management as a first-class scheduling object. A strong candidate explains that WM strategies are largely static bin-proposal rules evaluated at TO creation, while EWM waves add a scheduling and optimization layer on top of similar bin-proposal logic. Also be prepared to discuss how quantity-based strategies help consolidate partial bins and reduce fragmented stock.