JinJin48

SAP Consultant | BTP · S/4HANA · US Global Rollout

June 27, 2026 · 12 min read

SAP EWM Wave Template

The Wave Template is the master configuration object in SAP EWM that defines how open outbound warehouse orders are selected, grouped, and scheduled into waves for batch picking. It sits at the intersection of delivery scheduling, warehouse order management, and resource planning — acting as the rule set that converts individual pick demands into organized, route-optimized waves. This article covers wave types, organizational hierarchy, integration with surrounding EWM objects, and the full set of configuration fields that govern wave creation and release.

Part 1: Wave Template — Core Concepts (All Modules)#

1.1 What Is the Wave Template?#

A Wave Template is a reusable configuration record that encapsulates all the rules needed to create a wave: which warehouse orders to include, how large the wave can grow, when it starts, and how orders should be sorted for optimized picking. Without a Wave Template, the system has no criteria to group and batch pick requests — each outbound delivery would need to trigger picking individually.

1.2 Wave Types#

EWM supports four wave execution modes, each suited to a different operational rhythm. Choosing the wrong mode forces pickers into either idle waiting (scheduled too infrequently) or constant interruption (triggered too often).

Design principle: In most implementations, one warehouse will run two or three Wave Templates — Automatic for standard volume, Immediate for priority, and Manual as a fallback. Mixing modes within the same Activity Area requires careful priority settings to avoid double-assignment of warehouse orders.

1.3 Organizational Levels and Data Hierarchy#

The Wave Template exists at the Activity Area level within a Warehouse Number. This positioning means a single warehouse can run different wave rules for different physical zones (e.g., dry goods vs. cold storage), each governed by its own Wave Template.

Warehouse Number (e.g., WH01)
   │
   └── Activity Area (e.g., AA01 — Outbound picking zone)
          │
          ├── Wave Template (e.g., WTP01 — Standard Daily Wave)
          │      │
          │      ├── /SCWM/TWAVETP  — Template header: type, size limits, scheduling
          │      ├── /SCWM/TWAVESEL — Selection criteria: delivery type, route, shipping point
          │      └── /SCWM/TWAVEOPT — Optimization: sort sequence, route grouping flag
          │
          └── Wave (runtime object — created when template is executed)
                 │
                 └── Warehouse Order (grouped by wave)
                        │
                        └── Warehouse Task (individual pick/put instruction)

Key design decision: The Activity Area is the pivotal organizational element. Assign Wave Templates to Activity Areas that represent homogeneous picking zones — mixing cold and ambient storage in one Activity Area makes wave size limits and sort sequences meaningless.

1.4 Integration with Other Master Data Objects#

The Wave Template does not operate in isolation. It reads from delivery and order master data to evaluate selection criteria, and it feeds the wave execution engine that ultimately drives warehouse task assignment to pickers.

Part 2: EWM-Specific Field Details#

2.0 Scope of EWM Ownership#

Legend: ◎ = Owner / Critical

2.1 Wave Selection Criteria#

Wave Selection Criteria are the filter rules embedded in the Wave Template that determine which outbound warehouse orders qualify for inclusion in a wave. Each template can hold multiple selection rows; the system applies logical OR across rows, so a warehouse order matching any single row is selected.

2.2 Wave Size Control#

Wave Size Control fields cap the number of warehouse orders, line items, weight, and volume that a single wave may contain. These limits prevent a wave from becoming too large for the available picking resources to complete within the required time window.

2.3 Scheduling Settings#

Scheduling Settings control when the wave is created, how far into the future it looks for qualifying orders, and whether it releases automatically to pickers or requires a manual release step.

2.4 Sort and Optimization#

Sort and Optimization settings control the sequence in which warehouse orders within a wave are presented to pickers and whether the system attempts to group orders by physical travel route through the warehouse.

What to Read Next#

L1) Big Picture

L2-A) Master Data

L2-B) Transaction