Skip to content
EWM Reference

/SCDL/DB_STATUS

transactionMixed keyDOCCAT: IDRDOCCAT: ODRDOCCAT: PDIDOCCAT: PDODOCCAT: FDO

Delivery status — the long, narrow status table every /SCDL document writes into, one row per document or item per status type with its value and validity window

Grain note

Long and narrow — filter STATUS_TYPE (and DOCCAT) before pivoting, or a document's statuses fan out across every status type it has ever carried

Notes

Header-level status rows carry an initial (blank) ITEMID, item-level rows carry the item GUID — the same table serves both grains. Status values are DDIC domain codes; this reference describes them rather than decoding them, since the code lists have no verifiable public enumeration.

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.
Document categories

The /SCDL layer is shared: this table holds IDR (inbound delivery request), ODR (outbound delivery request), PDI (inbound delivery), PDO (outbound delivery order), FDO (final outbound delivery) rows in the same table, discriminated by DOCCAT — pick the one you mean before joining. How DOCCAT works

Fields

10 fields · 4 key

10 fields.

Table fields: position, field name, description, data type, and flags. 10 fields.
#FieldDescriptionTypeFlags
1MANDTClientCLNT(3)
Key
2DOCIDDocument GUID the status row belongs toRAW(16)
Key
3ITEMIDItem GUID — initial (blank) for header-level status rowsRAW(16)
Key
4STATUS_TYPEStatus type code (picking, goods issue, warehouse activity, and so on) — filter it before pivotingCHAR(5)
Key
5DOCCATDocument category of the referenced document — all five categories share this tableCHAR(3)
6STATUS_VALUECurrent value of the statusCHAR(1)
7TZONETime zone reference for the status timestampsCHAR(6)
8TSTFRStatus valid-from timeDEC(15)
UTCFilter date
9TSTTOStatus valid-to timeDEC(15)
10CHGUSRUser who last changed the status rowCHAR(12)

Field provenance: hand-curated. 4 key fields.

Boilerplate SQL

Starting point for reading the replicated copy of /SCDL/DB_STATUSon 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

8 parameters not filled: <catalog>, <schema>, <client>, <DOCID>, <ITEMID>, <STATUS_TYPE>, <TS_FROM>, <TS_TO>

-- ============================================================
-- Table  : /SCDL/DB_STATUS — Delivery status — the long, narrow status table every /SCDL document writes into, one row per document or item per status type with its value and validity window
-- Purpose: Column-selected read of /SCDL/DB_STATUS — auto-generated from field metadata
-- Grain  : One row per client + DOCID + ITEMID + STATUS_TYPE
-- Caution: Long and narrow — filter STATUS_TYPE (and DOCCAT) before pivoting, or a document's statuses fan out across every status type it has ever carried
-- Notes  : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCDL/DB_STATUS; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scdl_db_status — 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.DOCID AS "Document GUID the status row belongs to",
  lower(hex(t.DOCID)) AS "Document GUID the status row belongs to (hex)",  -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
  t.ITEMID AS "Item GUID — initial (blank) for header-level status rows",
  lower(hex(t.ITEMID)) AS "Item GUID — initial (blank) for header-level status rows (hex)",  -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
  t.STATUS_TYPE AS "Status type code (picking, goods issue, warehouse activity, and so on) — filter it before pivoting",
  t.DOCCAT AS "Document category of the referenced document — all five categories share this table",
  t.STATUS_VALUE AS "Current value of the status",
  t.TZONE AS "Time zone reference for the status timestamps",
  t.TSTFR AS "Status valid-from time",  -- UTC
  t.TSTTO AS "Status valid-to time",  -- UTC
  t.CHGUSR AS "User who last changed the status row"
FROM <catalog>.<schema>.scdl_db_status t
WHERE
  t.MANDT = '<client>'  -- client filter — drop on single-client systems
  AND t.DOCCAT = '<IDR|ODR|PDI|PDO|FDO>'  -- document category — one /SCDL table holds every category; see quirks guide #doccat
  -- AND t.DOCID = unhex('<DOCID>')  -- pass the 32-character hex form
  -- AND t.ITEMID = unhex('<ITEMID>')  -- pass the 32-character hex form
  -- AND t.STATUS_TYPE = '<STATUS_TYPE>'
  -- AND t.TSTFR >= <TS_FROM>  -- UTC yyyymmddhhmmss — convert warehouse-local dates first (#utc-timestamps)
  -- AND t.TSTFR <= <TS_TO>
ORDER BY t.DOCID;

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

  • /SCDL/DB_DLVH_O/SCDL/DB_STATUSGUID join · 1:N
    ON scdl_db_dlvh_o.MANDT = scdl_db_status.MANDT AND scdl_db_dlvh_o.DOCID = scdl_db_status.DOCID -- RAW16 GUID equality — join raw; hex is for display/conformance only
  • /SCDL/DB_PROCH_I/SCDL/DB_STATUSGUID join · 1:N
    ON scdl_db_proch_i.MANDT = scdl_db_status.MANDT AND scdl_db_proch_i.DOCID = scdl_db_status.DOCID -- RAW16 GUID equality — join raw; hex is for display/conformance only
  • /SCDL/DB_PROCH_O/SCDL/DB_STATUSGUID join · 1:N
    ON scdl_db_proch_o.MANDT = scdl_db_status.MANDT AND scdl_db_proch_o.DOCID = scdl_db_status.DOCID -- 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

Browse more Delivery Processing (Warehouse Requests) tables

More Delivery Processing (Warehouse Requests) 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.