/SCWM/WHO
transactionMixed keyWarehouse 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
The name-collision trap: the table is /SCWM/WHO and its warehouse-order number column is also WHO, so an unqualified WHO in a query reads as either. The activity-area column here is AREAWHO, not AAREA. Joins ride LGNUM + WHO; the RAW16 WHOID column is an informational unique id and is not the join key.
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
Fields
18 fields · 3 key
18 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | LGNUM | Warehouse number | CHAR(4) | Key |
| 3 | WHO | Warehouse order number — the table/field name collision: the table is /SCWM/WHO and so is the column | NUMC(10) | Key |
| 4 | STATUS | Warehouse order status | CHAR(1) | |
| 5 | WCR | Warehouse order creation rule that produced the order | CHAR(4) | |
| 6 | WAVE | Wave the warehouse order was created from | NUMC(10) | |
| 7 | AREAWHO | Activity area the warehouse order is assigned to — the column is AREAWHO here, not AAREA | CHAR(4) | |
| 8 | QUEUE | Queue the warehouse order is routed to | CHAR(10) | |
| 9 | RSRC | Resource (user or equipment) the warehouse order is assigned to | CHAR(18) | |
| 10 | PROCESSOR | Processor working the warehouse order | CHAR(12) | |
| 11 | CREATED_AT | Warehouse order creation time | DEC(15) | UTCFilter date |
| 12 | STARTED_AT | Warehouse order start time | DEC(15) | |
| 13 | CONFIRMED_AT | Warehouse order confirmation time | DEC(15) | |
| 14 | CONFIRMED_BY | User who confirmed the warehouse order | CHAR(12) | |
| 15 | LSD | Latest starting date and time for on-time execution | DEC(15) | |
| 16 | TOPWHOID | Higher-level warehouse order number, where orders are nested | NUMC(10) | |
| 17 | FLGTO | Flag: the warehouse order contains warehouse tasks | CHAR(1) | |
| 18 | WHOID | Unique GUID of the warehouse order — informational; joins ride warehouse number plus order number | RAW(16) |
Field provenance: hand-curated. 3 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /SCWM/WHOon 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>, <WHO>, <TS_FROM>, <TS_TO>
-- ============================================================
-- Table : /SCWM/WHO — Warehouse 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
-- Purpose: Column-selected read of /SCWM/WHO — auto-generated from field metadata
-- Grain : One row per client + LGNUM + WHO
-- Notes : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/WHO; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_who — 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.WHO AS "Warehouse order number — the table/field name collision: the table is /SCWM/WHO and so is the column",
t.STATUS AS "Warehouse order status",
t.WCR AS "Warehouse order creation rule that produced the order",
t.WAVE AS "Wave the warehouse order was created from",
t.AREAWHO AS "Activity area the warehouse order is assigned to — the column is AREAWHO here, not AAREA",
t.QUEUE AS "Queue the warehouse order is routed to",
t.RSRC AS "Resource (user or equipment) the warehouse order is assigned to",
t.PROCESSOR AS "Processor working the warehouse order",
t.CREATED_AT AS "Warehouse order creation time", -- UTC
t.STARTED_AT AS "Warehouse order start time", -- UTC
t.CONFIRMED_AT AS "Warehouse order confirmation time", -- UTC
t.CONFIRMED_BY AS "User who confirmed the warehouse order",
t.LSD AS "Latest starting date and time for on-time execution", -- UTC
t.TOPWHOID AS "Higher-level warehouse order number, where orders are nested",
t.FLGTO AS "Flag: the warehouse order contains warehouse tasks",
t.WHOID AS "Unique GUID of the warehouse order — informational; joins ride warehouse number plus order number",
lower(hex(t.WHOID)) AS "Unique GUID of the warehouse order — informational; joins ride warehouse number plus order number (hex)" -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
FROM <catalog>.<schema>.scwm_who t
WHERE
t.MANDT = '<client>' -- client filter — drop on single-client systems
-- AND t.LGNUM = '<LGNUM>'
-- AND t.WHO = '<WHO>'
-- AND t.CREATED_AT >= <TS_FROM> -- UTC yyyymmddhhmmss — convert warehouse-local dates first (#utc-timestamps)
-- AND t.CREATED_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_ordim_o.MANDT = scwm_who.MANDT AND scwm_ordim_o.WHO = scwm_who.WHO AND scwm_ordim_o.LGNUM = scwm_who.LGNUMON scwm_ordim_c.MANDT = scwm_who.MANDT AND scwm_ordim_c.WHO = scwm_who.WHO AND scwm_ordim_c.LGNUM = scwm_who.LGNUMON scwm_ordim_l.MANDT = scwm_who.MANDT AND scwm_ordim_l.WHO = scwm_who.WHO AND scwm_ordim_l.LGNUM = scwm_who.LGNUMON scwm_who.MANDT = scwm_rsrc.MANDT AND scwm_who.RSRC = scwm_rsrc.RSRC AND scwm_who.LGNUM = scwm_rsrc.LGNUMON scwm_who.MANDT = scwm_wavehdr.MANDT AND scwm_who.WAVE = scwm_wavehdr.WAVE AND scwm_who.LGNUM = scwm_wavehdr.LGNUMON scwm_who.MANDT = scwm_taarea.MANDT AND scwm_who.AREAWHO = scwm_taarea.AAREA AND scwm_who.LGNUM = scwm_taarea.LGNUMON scwm_who.MANDT = scwm_t346.MANDT AND scwm_who.QUEUE = scwm_t346.QUEUE AND scwm_who.LGNUM = scwm_t346.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
- /SCWM/ADHUCreate an ad-hoc warehouse task for a handling unit — move a whole HU rather than a product quantityWrite accessCreatestock-hu
- /SCWM/ADPRODCreate an ad-hoc warehouse task for a product — move stock without a delivery or a wave asking for itWrite accessCreatestock-hu
- /SCWM/CANCPICKCancel picking — reverse picking work already created or confirmed for an outbound deliveryRead/write accessChangewarehouse-tasks
- /SCWM/MONThe warehouse monitor — the single screen operations works from, with drill-downs across tasks, orders, stock, handling units, deliveries, and resourcesRead accessList / Monitorwarehouse-tasks
- /SCWM/RFUILog on to the RF environment — the radio-frequency screen an operator works warehouse orders fromRead/write accessList / Monitorresources
- /SCWM/TO_CONFConfirm a warehouse task — the transaction that records work as done and moves the row out of the open-task tableRead/write accessChangewarehouse-tasks
- /SCWM/TODLV_ICreate warehouse tasks for an inbound delivery — the putaway work behind a receiptWrite accessCreatewarehouse-tasks
- /SCWM/TODLV_OCreate warehouse tasks for an outbound delivery order — the picking work behind a shipmentWrite accessCreatewarehouse-tasks
More Warehouse Tasks & Orders tables
- /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
- /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