Skip to content
EWM Reference

/SCWM/WHO

transactionMixed key

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

Notes

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.

Structural facts — how the table is keyed, not a trap by itself

Semantic key
Every non-client key column is readable business data — LGNUM plus a bin, task, or order number. Joins run on the columns you can see (see the quirks guide).

Join & extract hazards — verify before you rely on this

GUID key
Every non-client key column is a GUID — RAW(16) on the /SCWM, /SCDL, /LIME, and /SCMB tables, and the CHAR(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.
In field listings, the Key chip marks a primary-key field, and UTC marks a timestamp stored in UTC rather than warehouse-local time.
Used in the library

Fields

18 fields · 3 key

18 fields.

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1MANDTClientCLNT(3)
Key
2LGNUMWarehouse numberCHAR(4)
Key
3WHOWarehouse order number — the table/field name collision: the table is /SCWM/WHO and so is the columnNUMC(10)
Key
4STATUSWarehouse order statusCHAR(1)
5WCRWarehouse order creation rule that produced the orderCHAR(4)
6WAVEWave the warehouse order was created fromNUMC(10)
7AREAWHOActivity area the warehouse order is assigned to — the column is AREAWHO here, not AAREACHAR(4)
8QUEUEQueue the warehouse order is routed toCHAR(10)
9RSRCResource (user or equipment) the warehouse order is assigned toCHAR(18)
10PROCESSORProcessor working the warehouse orderCHAR(12)
11CREATED_ATWarehouse order creation timeDEC(15)
UTCFilter date
12STARTED_ATWarehouse order start timeDEC(15)
13CONFIRMED_ATWarehouse order confirmation timeDEC(15)
14CONFIRMED_BYUser who confirmed the warehouse orderCHAR(12)
15LSDLatest starting date and time for on-time executionDEC(15)
16TOPWHOIDHigher-level warehouse order number, where orders are nestedNUMC(10)
17FLGTOFlag: the warehouse order contains warehouse tasksCHAR(1)
18WHOIDUnique GUID of the warehouse order — informational; joins ride warehouse number plus order numberRAW(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.

Query parameters

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

  • /SCWM/ORDIM_O/SCWM/WHOforeign key · N:1
    ON scwm_ordim_o.MANDT = scwm_who.MANDT AND scwm_ordim_o.WHO = scwm_who.WHO AND scwm_ordim_o.LGNUM = scwm_who.LGNUM
  • /SCWM/ORDIM_C/SCWM/WHOforeign key · N:1
    ON scwm_ordim_c.MANDT = scwm_who.MANDT AND scwm_ordim_c.WHO = scwm_who.WHO AND scwm_ordim_c.LGNUM = scwm_who.LGNUM
  • /SCWM/ORDIM_L/SCWM/WHOforeign key · N:1
    ON scwm_ordim_l.MANDT = scwm_who.MANDT AND scwm_ordim_l.WHO = scwm_who.WHO AND scwm_ordim_l.LGNUM = scwm_who.LGNUM
  • /SCWM/WHO/SCWM/RSRCforeign key · N:1
    ON scwm_who.MANDT = scwm_rsrc.MANDT AND scwm_who.RSRC = scwm_rsrc.RSRC AND scwm_who.LGNUM = scwm_rsrc.LGNUM
  • /SCWM/WHO/SCWM/WAVEHDRforeign key · N:1
    ON scwm_who.MANDT = scwm_wavehdr.MANDT AND scwm_who.WAVE = scwm_wavehdr.WAVE AND scwm_who.LGNUM = scwm_wavehdr.LGNUM
  • /SCWM/WHO/SCWM/TAAREAforeign key · N:1
    ON scwm_who.MANDT = scwm_taarea.MANDT AND scwm_who.AREAWHO = scwm_taarea.AAREA AND scwm_who.LGNUM = scwm_taarea.LGNUM
  • /SCWM/WHO/SCWM/T346foreign key · N:1
    ON 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

Browse more Warehouse Tasks & Orders tables

More Warehouse Tasks & Orders tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by SAP. SAP, SAP S/4HANA, and SAP Extended Warehouse Management are trademarks or registered trademarks of SAP SE.