Configuring and Executing Wave Creation: Templates, Selection Criteria, and Release Strategies

Explanation

Once the business case for wave management is understood, the next step for a consultant is knowing how a wave is actually configured and executed. In EWM (embedded in S/4HANA or decentralized), the central configuration object is the wave template. A wave template is set up in warehouse customizing under warehouse process configuration and defines selection criteria - the attributes used to decide which warehouse-request items are eligible to be pulled into a wave - such as delivery priority, shipping point, route, destination, planned goods issue date, or activity area. The template also defines grouping and splitting rules, which determine how eligible items are subdivided into individual waves (for example, one wave per route, or one wave per door assignment), and sequencing rules that influence the order in which tasks within a wave are worked. Wave creation itself can be manual or automatic. Manual wave creation is typically used by a supervisor who selects a set of open warehouse-request items and applies a wave template interactively, useful for exception handling, rush orders, or ad hoc reorganization of work. Automatic wave creation relies on background jobs or event-triggered processing that periodically scans open warehouse requests and applies configured wave templates according to schedule (for example, running every 30 minutes) or in response to a triggering event (such as a delivery being created or a certain time threshold being reached). Consultants must configure the job variant or trigger and the selection window carefully; a poorly scoped selection can either miss legitimate candidates (if criteria are too narrow) or create oversized waves that overwhelm downstream capacity (if criteria are too broad). After a wave is created, wave release is the step that converts the grouped items into actual execution documents - warehouse tasks in EWM, or transfer orders in ECC WM. Release can happen immediately upon wave creation (direct release) or be held for supervisor approval (two-step: create then release), which is valuable when capacity or stock availability needs a final check. Release strategies also interact with resource management and RF queues: once released, tasks become visible to workers based on queue assignment, and the wave's grouping logic effectively pre-sorts the work into logical execution chunks. In ECC WM, the equivalent process is less template-driven and more tied to the classic collective processing of deliveries for transfer order creation, often executed via background jobs that group deliveries by shipping point, route, or other selection fields and then create transfer orders in a single run; the concept of a discrete

Code example

* Illustrative pseudo-representation of wave template selection logic (conceptual, not a real transaction)* Wave Template: ZWAVE_ROUTE_AM* Selection Criteria:*   Warehouse Number = 1710*   Shipping Point   = 1000*   Route             = ROUTE_NORTH_AM*   Planned GI Date   = Today* Grouping Rule: One wave per Route + Loading Door combination* Sequencing Rule: Sort by Storage Bin ascending (pick path optimization)* Release Mode: Two-step (Create, then Supervisor Release)** Automatic Job (conceptual):*   Job: WAVE_AUTO_CREATE_JOB*   Frequency: Every 30 minutes, 06:00-18:00*   Action: Apply ZWAVE_ROUTE_AM to all eligible open warehouse requests*   Exception: Items flagged for Hazmat routed to manual review queue

Real project scenario

A consumer goods distribution center configures separate wave templates for its two main outbound lanes: a fast-moving regional route wave triggered automatically every 30 minutes to keep pickers continuously fed, and a long-haul export wave that is created automatically but held for manual release so the export documentation team can verify customs paperwork before tasks reach the floor. The consultant tunes selection criteria to avoid pulling in delivery items still pending credit block release, which had earlier caused wave creation failures.

Common mistakes

• Setting automatic wave selection criteria too broad, resulting in oversized waves that exceed available labor or staging capacity. • Failing to exclude blocked or incomplete delivery items from selection, causing wave creation errors or partial waves. • Using direct release everywhere without considering scenarios (like export or hazmat) that genuinely need a supervisor checkpoint before task release. • Not aligning wave job scheduling frequency with actual dock and shift patterns, leading to either work starvation or flooding. • Assuming ECC WM's collective transfer order creation is functionally identical to EWM's wave template mechanism, when the configuration objects and flexibility differ.

Best practices

• Scope wave selection criteria tightly enough to avoid oversized waves while still capturing all legitimate eligible work. • Use two-step release for scenarios needing verification (customs, hazmat, credit checks) and direct release for high-volume routine flows. • Align automatic wave job frequency with real shift and dock schedules rather than arbitrary defaults. • Explicitly exclude known blocking conditions (credit blocks, incomplete documents) from wave selection criteria to prevent creation failures. • Document wave template purpose and ownership so future consultants understand why each template exists.

Interview angle

Be prepared to explain the difference between wave creation and wave release, describe what a wave template controls (selection, grouping, sequencing), and discuss when you would choose automatic versus manual wave creation and direct versus two-step release. Interviewers may probe whether you understand that overly broad selection criteria is a common root cause of warehouse congestion.