/SCWM/ORDIM_L
transactionMixed keyWarehouse task log — the historical record of tasks that left the open table without a normal confirmation; generally where cancelled and logged tasks are found
Same shape as the open table (no task-item key column) with a status column that says how the task ended. Cancelled tasks drop out of the open table without reaching the confirmed one, and this log is generally where they are found — worth confirming against your own system, since the public documentation of the exact routing is thin. Counting cancellations against confirmations needs this table; the open/confirmed pair alone undercounts the work that was created.
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
15 fields · 3 key
15 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | LGNUM | Warehouse number | CHAR(4) | Key |
| 3 | TANUM | Warehouse task number | NUMC(12) | Key |
| 4 | WHO | Warehouse order reference | NUMC(10) | |
| 5 | PROCTY | Warehouse process type | CHAR(4) | |
| 6 | QUEUE | Execution queue | CHAR(10) | |
| 7 | MATID | Product GUID (RAW16 form) | RAW(16) | |
| 8 | TOSTAT | Warehouse task status at the time it was logged, such as cancelled | CHAR(1) | |
| 9 | VLPLA | Source storage bin | CHAR(18) | |
| 10 | NLPLA | Destination storage bin | CHAR(18) | |
| 11 | VSOLM | Target quantity in the base unit | QUAN(31,14) | |
| 12 | MEINS | Base unit of measure | UNIT(3) | |
| 13 | RDOCID | GUID of the reference delivery document | RAW(16) | |
| 14 | RITMID | GUID of the reference delivery item | RAW(16) | |
| 15 | CREATED_AT | Task creation time | DEC(15) | UTCFilter date |
Field provenance: hand-curated. 3 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /SCWM/ORDIM_Lon 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>, <TANUM>, <TS_FROM>, <TS_TO>
-- ============================================================
-- Table : /SCWM/ORDIM_L — Warehouse task log — the historical record of tasks that left the open table without a normal confirmation; generally where cancelled and logged tasks are found
-- Purpose: Column-selected read of /SCWM/ORDIM_L — auto-generated from field metadata
-- Grain : One row per client + LGNUM + TANUM
-- Notes : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/ORDIM_L; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_ordim_l — 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.TANUM AS "Warehouse task number",
t.WHO AS "Warehouse order reference",
t.PROCTY AS "Warehouse process type",
t.QUEUE AS "Execution queue",
t.MATID AS "Product GUID (RAW16 form)",
lower(hex(t.MATID)) AS "Product GUID (RAW16 form) (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.TOSTAT AS "Warehouse task status at the time it was logged, such as cancelled",
t.VLPLA AS "Source storage bin",
t.NLPLA AS "Destination storage bin",
t.VSOLM AS "Target quantity in the base unit",
t.MEINS AS "Base unit of measure",
t.RDOCID AS "GUID of the reference delivery document",
lower(hex(t.RDOCID)) AS "GUID of the reference 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 reference delivery item",
lower(hex(t.RITMID)) AS "GUID of the reference delivery item (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.CREATED_AT AS "Task creation time" -- UTC
FROM <catalog>.<schema>.scwm_ordim_l t
WHERE
t.MANDT = '<client>' -- client filter — drop on single-client systems
-- AND t.LGNUM = '<LGNUM>'
-- AND t.TANUM = '<TANUM>'
-- 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_l.MANDT = scwm_who.MANDT AND scwm_ordim_l.WHO = scwm_who.WHO AND scwm_ordim_l.LGNUM = scwm_who.LGNUMON scwm_ordim_l.MANDT = scwm_lagp.MANDT AND scwm_ordim_l.VLPLA = scwm_lagp.LGPLA AND scwm_ordim_l.LGNUM = scwm_lagp.LGNUMON scwm_ordim_l.MANDT = scwm_lagp.MANDT AND scwm_ordim_l.NLPLA = scwm_lagp.LGPLA AND scwm_ordim_l.LGNUM = scwm_lagp.LGNUMON scwm_ordim_l.MANDT = sapapo_matkey.MANDT AND scwm_ordim_l.MATID = sapapo_matkey.MATID -- the /SCWM side is RAW(16) and MATKEY keys the CHAR 22 compressed form — convert before comparing; this is not a raw equalitythe /SCWM side is RAW(16) and MATKEY keys the CHAR 22 compressed form — convert before comparing; this is not a raw equality
ON scwm_ordim_l.MANDT = scdl_db_proci_i.MANDT AND scwm_ordim_l.RDOCID = scdl_db_proci_i.DOCID AND scwm_ordim_l.RITMID = scdl_db_proci_i.ITEMID -- RAW16 GUID equality — join raw; hex is for display/conformance onlyON scwm_ordim_l.MANDT = scdl_db_proci_o.MANDT AND scwm_ordim_l.RDOCID = scdl_db_proci_o.DOCID AND scwm_ordim_l.RITMID = scdl_db_proci_o.ITEMID -- RAW16 GUID equality — join raw; hex is for display/conformance onlyON scwm_ordim_l.MANDT = scwm_t346.MANDT AND scwm_ordim_l.QUEUE = scwm_t346.QUEUE AND scwm_ordim_l.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
More Warehouse Tasks & Orders tables
- /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
- /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