Skip to content
EWM Reference

/SCDL/DB_REFDOC

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

Reference documents — the bridge from an EWM delivery document to the document that caused it in the connected ERP system, with the readable reference number and item

Grain note

One EWM document can carry several reference rows (ERP delivery, purchase order, sales order, ASN) — filter REFDOCCAT before joining or documents duplicate

Notes

This is where the ERP delivery number lives: REFBSKEY says which connected system owns the number, REFDOCNO/REFITEMNO carry it. The ERP-side delivery tables themselves (LIKP/LIPS) live in the ERP system, not in EWM — this reference names them in prose only and draws no edge to them.

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

12 fields · 6 key

12 fields.

Table fields: position, field name, description, data type, and flags. 12 fields.
#FieldDescriptionTypeFlags
1MANDTClientCLNT(3)
Key
2DOCIDGUID of the EWM delivery documentRAW(16)
Key
3ITEMIDGUID of the EWM delivery item — initial for header-level referencesRAW(16)
Key
4REFDOCCATCategory of the referenced document (ERP delivery, purchase order, sales order, ASN)CHAR(3)
Key
5REFDOCIDGUID of the referenced document, where it exists in EWMRAW(16)
Key
6REFITEMIDGUID of the referenced itemRAW(16)
Key
7DOCCATDocument category of the owning EWM documentCHAR(3)
8REFBSKEYBusiness system key the reference points into — which connected system owns the numberCHAR(60)
9REFDOCNOReadable reference document number, typically the ERP delivery numberCHAR(35)
10REFITEMNOReadable reference item number, typically the ERP delivery itemNUMC(10)
11TSTFRReference valid-from timeDEC(15)
UTCFilter date
12TSTTOReference valid-to timeDEC(15)

Field provenance: hand-curated. 6 key fields.

Boilerplate SQL

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

10 parameters not filled: <catalog>, <schema>, <client>, <DOCID>, <ITEMID>, <REFDOCCAT>, <REFDOCID>, <REFITEMID>, <TS_FROM>, <TS_TO>

-- ============================================================
-- Table  : /SCDL/DB_REFDOC — Reference documents — the bridge from an EWM delivery document to the document that caused it in the connected ERP system, with the readable reference number and item
-- Purpose: Column-selected read of /SCDL/DB_REFDOC — auto-generated from field metadata
-- Grain  : One row per client + DOCID + ITEMID + REFDOCCAT + REFDOCID + REFITEMID
-- Caution: One EWM document can carry several reference rows (ERP delivery, purchase order, sales order, ASN) — filter REFDOCCAT before joining or documents duplicate
-- 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_REFDOC; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scdl_db_refdoc — 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 "GUID of the EWM delivery document",
  lower(hex(t.DOCID)) AS "GUID of the EWM delivery document (hex)",  -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
  t.ITEMID AS "GUID of the EWM delivery item — initial for header-level references",
  lower(hex(t.ITEMID)) AS "GUID of the EWM delivery item — initial for header-level references (hex)",  -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
  t.REFDOCCAT AS "Category of the referenced document (ERP delivery, purchase order, sales order, ASN)",
  t.REFDOCID AS "GUID of the referenced document, where it exists in EWM",
  lower(hex(t.REFDOCID)) AS "GUID of the referenced document, where it exists in EWM (hex)",  -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
  t.REFITEMID AS "GUID of the referenced item",
  lower(hex(t.REFITEMID)) AS "GUID of the referenced item (hex)",  -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
  t.DOCCAT AS "Document category of the owning EWM document",
  t.REFBSKEY AS "Business system key the reference points into — which connected system owns the number",
  t.REFDOCNO AS "Readable reference document number, typically the ERP delivery number",
  t.REFITEMNO AS "Readable reference item number, typically the ERP delivery item",
  t.TSTFR AS "Reference valid-from time",  -- UTC
  t.TSTTO AS "Reference valid-to time"  -- UTC
FROM <catalog>.<schema>.scdl_db_refdoc 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.REFDOCCAT = '<REFDOCCAT>'
  -- AND t.REFDOCID = unhex('<REFDOCID>')  -- pass the 32-character hex form
  -- AND t.REFITEMID = unhex('<REFITEMID>')  -- pass the 32-character hex form
  -- 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_REFDOCGUID join · 1:N
    ON scdl_db_dlvh_o.MANDT = scdl_db_refdoc.MANDT AND scdl_db_dlvh_o.DOCID = scdl_db_refdoc.DOCID -- RAW16 GUID equality — join raw; hex is for display/conformance only
  • /SCDL/DB_PROCH_I/SCDL/DB_REFDOCGUID join · 1:N
    ON scdl_db_proch_i.MANDT = scdl_db_refdoc.MANDT AND scdl_db_proch_i.DOCID = scdl_db_refdoc.DOCID -- RAW16 GUID equality — join raw; hex is for display/conformance only
  • /SCDL/DB_PROCH_O/SCDL/DB_REFDOCGUID join · 1:N
    ON scdl_db_proch_o.MANDT = scdl_db_refdoc.MANDT AND scdl_db_proch_o.DOCID = scdl_db_refdoc.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.