/SCWM/WAVEHDR
transactionSemantic keyWave header — the planned release of outbound work, with its template, type, cutoff and release times, and the planned picking and loading completion times
The wave key is semantic (warehouse + wave number), settled from two independent mirrors — waves are not GUID-keyed. The gap between RLS_DT (planned release) and RELEASED_AT (actual release) is the wave-punctuality measure; both are UTC — though the RELEASED_AT reading rests on the column name and its non-_WH suffix rather than a wave-specific data element.
What the badges mean
- master
- Data class: what the table holds — master data, transaction documents, configuration, an organizational object, or a language-striped text companion.
- Semantic key
- Every non-client key column is readable business data —
LGNUMplus a bin, task, or order number. Joins run on the columns you can see (see the quirks guide). - GUID key
- Every non-client key column is a GUID —
RAW(16)on the /SCWM, /SCDL, /LIME, and /SCMB tables, and theCHAR(22)compressed form on the product master. Join the raw column; a hex rendering is for reading only, and the two encodings need converting between (see the quirks guide). - Mixed key
- The key mixes readable and GUID columns in either direction — a product GUID inside an otherwise-readable bin key, or a readable status type inside an otherwise-GUID key. Check which side of a join you are on (see the quirks guide).
- DOCCAT: PDO
- A /SCDL delivery table holds several document categories in one table — inbound and outbound requests, the inbound delivery, the outbound delivery order, and the final outbound delivery — discriminated by
DOCCAT. The chips list the categories this table carries; anchor the one you mean or documents of every kind come back together (see the quirks guide). - Embedded S/4HANA only
- Deployment: shown only when a table does not exist in both embedded S/4HANA EWM and decentralized EWM. No table in this wave is deployment-specific, so the badge stays absent until one is.
Structural facts — how the table is keyed, not a trap by itself
Join & extract hazards — verify before you rely on this
Header & item
/SCWM/WAVEHDR is the header for its items in /SCWM/WAVEITM.
Fields
16 fields · 3 key
16 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | LGNUM | Warehouse number | CHAR(4) | Key |
| 3 | WAVE | Wave number, unique within the warehouse | NUMC(10) | Key |
| 4 | TMPLT | Wave template the wave was built from | NUMC(10) | |
| 5 | WAVE_TYPE | Wave type | CHAR(4) | |
| 6 | WAVE_CAT | Wave category | CHAR(2) | |
| 7 | RLS_MTHD | Release method — manual against automatic or scheduled | CHAR(1) | |
| 8 | STATUS | Wave header status | CHAR(1) | |
| 9 | CUTOFF_DT | Wave cutoff date and time | DEC(15) | |
| 10 | RLS_DT | Planned wave release date and time | DEC(15) | |
| 11 | RELEASED_AT | Actual wave release time | DEC(15) | UTCFilter date |
| 12 | RELEASED_BY | User who released the wave | CHAR(12) | |
| 13 | PICK_COMP_DT | Planned picking completion time | DEC(15) | |
| 14 | LOAD_COMP_DT | Planned wave and loading completion time | DEC(15) | |
| 15 | FLG_MNRLS | Flag: the wave was released manually | CHAR(1) | |
| 16 | MXITM | Highest item number issued in the wave | NUMC(6) |
Field provenance: hand-curated. 3 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /SCWM/WAVEHDRon Databricks — the client anchor is already in place, the namespaced name is rendered as the underscore bronze name replication targets conventionally land it under, and any RAW16 GUID column selects a hex rendering alongside the raw value. Set your Unity Catalog location, schema, and filter values below; they’re substituted into the SQL and the copy button.
7 parameters not filled: <catalog>, <schema>, <client>, <LGNUM>, <WAVE>, <TS_FROM>, <TS_TO>
-- ============================================================
-- Table : /SCWM/WAVEHDR — Wave header — the planned release of outbound work, with its template, type, cutoff and release times, and the planned picking and loading completion times
-- Purpose: Column-selected read of /SCWM/WAVEHDR — auto-generated from field metadata
-- Grain : One row per client + LGNUM + WAVE
-- Notes : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/WAVEHDR; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_wavehdr — adjust to your landing convention (see quirks #namespace-slashes). Timestamps flagged UTC are DEC(15) yyyymmddhhmmss values in UTC, not warehouse local time (#utc-timestamps).
-- ============================================================
SELECT
t.MANDT AS "Client",
t.LGNUM AS "Warehouse number",
t.WAVE AS "Wave number, unique within the warehouse",
t.TMPLT AS "Wave template the wave was built from",
t.WAVE_TYPE AS "Wave type",
t.WAVE_CAT AS "Wave category",
t.RLS_MTHD AS "Release method — manual against automatic or scheduled",
t.STATUS AS "Wave header status",
t.CUTOFF_DT AS "Wave cutoff date and time", -- UTC
t.RLS_DT AS "Planned wave release date and time", -- UTC
t.RELEASED_AT AS "Actual wave release time", -- UTC
t.RELEASED_BY AS "User who released the wave",
t.PICK_COMP_DT AS "Planned picking completion time", -- UTC
t.LOAD_COMP_DT AS "Planned wave and loading completion time", -- UTC
t.FLG_MNRLS AS "Flag: the wave was released manually",
t.MXITM AS "Highest item number issued in the wave"
FROM <catalog>.<schema>.scwm_wavehdr t
WHERE
t.MANDT = '<client>' -- client filter — drop on single-client systems
-- AND t.LGNUM = '<LGNUM>'
-- AND t.WAVE = '<WAVE>'
-- AND t.RELEASED_AT >= <TS_FROM> -- UTC yyyymmddhhmmss — convert warehouse-local dates first (#utc-timestamps)
-- AND t.RELEASED_AT <= <TS_TO>
ORDER BY t.LGNUM;Verified August 2026
Landing conventions differ — see namespaced names in a lakehouse.
Relationships
Diagram of 1-hop neighbors — join details below. GUID joins and text-table joins are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON scwm_who.MANDT = scwm_wavehdr.MANDT AND scwm_who.WAVE = scwm_wavehdr.WAVE AND scwm_who.LGNUM = scwm_wavehdr.LGNUMON scwm_wavehdr.MANDT = scwm_waveitm.MANDT AND scwm_wavehdr.WAVE = scwm_waveitm.WAVE AND scwm_wavehdr.LGNUM = scwm_waveitm.LGNUM
Transaction codes that touch this table
Curated: the EWM transactions an analyst would trace back to these rows, and how each one touches them.
R read · W write · R/W read + write
More Warehouse Tasks & Orders tables
- /SCWM/WAVEITMWave item — one delivery item assigned to a wave, with the task-creation status that says whether the wave actually produced work for it
- /SCWM/WHOWarehouse order header — the bundle of tasks one operator executes as a unit, with the creation rule that produced it, the wave it came from, its queue, activity area, assigned resource, and the timestamps that bound execution
- /SCWM/ORDIM_CConfirmed warehouse tasks — the same movement after execution, carrying the actual quantity, the confirmation timestamp, and (with the creation stamp) the task cycle time
- /SCWM/ORDIM_LWarehouse task log — the historical record of tasks that left the open table without a normal confirmation; generally where cancelled and logged tasks are found
- /SCWM/ORDIM_OOpen warehouse tasks — the work still to be done: source and destination bin, product, target quantity, process type, queue, and the delivery item the move was created for