/SCWM/WAVEITM
transactionMixed keyWave item — one delivery item assigned to a wave, with the task-creation status that says whether the wave actually produced work for it
The delivery reference is RDOCID/RITMID (the outbound delivery order item), not DOCID/ITEMID. STAT_CR and WV_ERROR together explain wave items that were released but never became warehouse tasks — the first place to look when a wave under-delivers.
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/WAVEITM items join back to their header /SCWM/WAVEHDR on the document key, so an item never fans out.
Fields
17 fields · 4 key
17 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | LGNUM | Warehouse number | CHAR(4) | Key |
| 3 | WAVE | Wave number | NUMC(10) | Key |
| 4 | WAVE_ITM | Wave item number | NUMC(6) | Key |
| 5 | RDOCID | GUID of the assigned delivery document | RAW(16) | |
| 6 | RITMID | GUID of the assigned delivery item | RAW(16) | |
| 7 | DOCNO | Readable document number of the referenced delivery | CHAR(35) | |
| 8 | ITEMNO | Readable item number of the referenced delivery item | NUMC(10) | |
| 9 | STAT_CR | Status of warehouse task creation for the wave item | CHAR(1) | |
| 10 | WV_ERROR | Error status of the wave item | CHAR(1) | |
| 11 | AAREA | Activity area of the wave item | CHAR(4) | |
| 12 | MATNR | Product number in its readable form | CHAR(40) | |
| 13 | CHARG | Batch | CHAR(10) | |
| 14 | ENTITLED | Party entitled to dispose | CHAR(10) | |
| 15 | QUAN | Wave item quantity | QUAN(31,14) | |
| 16 | UNIT | Unit of measure of the wave item quantity | UNIT(3) | |
| 17 | PROCTY | Warehouse process type | CHAR(4) |
Field provenance: hand-curated. 4 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /SCWM/WAVEITMon 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.
6 parameters not filled: <catalog>, <schema>, <client>, <LGNUM>, <WAVE>, <WAVE_ITM>
-- ============================================================
-- Table : /SCWM/WAVEITM — Wave item — one delivery item assigned to a wave, with the task-creation status that says whether the wave actually produced work for it
-- Purpose: Column-selected read of /SCWM/WAVEITM — auto-generated from field metadata
-- Grain : One row per client + LGNUM + WAVE + WAVE_ITM
-- Notes : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/WAVEITM; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_waveitm — adjust to your landing convention (see quirks #namespace-slashes). RAW16 GUID columns are joined raw; the hex aliases are for display only (#guid-keys). 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",
t.WAVE_ITM AS "Wave item number",
t.RDOCID AS "GUID of the assigned delivery document",
lower(hex(t.RDOCID)) AS "GUID of the assigned delivery document (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.RITMID AS "GUID of the assigned delivery item",
lower(hex(t.RITMID)) AS "GUID of the assigned delivery item (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.DOCNO AS "Readable document number of the referenced delivery",
t.ITEMNO AS "Readable item number of the referenced delivery item",
t.STAT_CR AS "Status of warehouse task creation for the wave item",
t.WV_ERROR AS "Error status of the wave item",
t.AAREA AS "Activity area of the wave item",
t.MATNR AS "Product number in its readable form",
t.CHARG AS "Batch",
t.ENTITLED AS "Party entitled to dispose",
t.QUAN AS "Wave item quantity",
t.UNIT AS "Unit of measure of the wave item quantity",
t.PROCTY AS "Warehouse process type"
FROM <catalog>.<schema>.scwm_waveitm t
WHERE
t.MANDT = '<client>' -- client filter — drop on single-client systems
-- AND t.LGNUM = '<LGNUM>'
-- AND t.WAVE = '<WAVE>'
-- AND t.WAVE_ITM = '<WAVE_ITM>'
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_wavehdr.MANDT = scwm_waveitm.MANDT AND scwm_wavehdr.WAVE = scwm_waveitm.WAVE AND scwm_wavehdr.LGNUM = scwm_waveitm.LGNUMON scwm_waveitm.MANDT = scdl_db_proci_o.MANDT AND scwm_waveitm.RDOCID = scdl_db_proci_o.DOCID AND scwm_waveitm.RITMID = scdl_db_proci_o.ITEMID -- RAW16 GUID equality — join raw; hex is for display/conformance only
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/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
- /SCWM/WAVEHDRWave header — the planned release of outbound work, with its template, type, cutoff and release times, and the planned picking and loading completion times