/SCDL/DB_REFDOC
transactionMixed keyDOCCAT: IDRDOCCAT: ODRDOCCAT: PDIDOCCAT: PDODOCCAT: FDOReference 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
One EWM document can carry several reference rows (ERP delivery, purchase order, sales order, ASN) — filter REFDOCCAT before joining or documents duplicate
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.
- 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
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.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | DOCID | GUID of the EWM delivery document | RAW(16) | Key |
| 3 | ITEMID | GUID of the EWM delivery item — initial for header-level references | RAW(16) | Key |
| 4 | REFDOCCAT | Category of the referenced document (ERP delivery, purchase order, sales order, ASN) | CHAR(3) | Key |
| 5 | REFDOCID | GUID of the referenced document, where it exists in EWM | RAW(16) | Key |
| 6 | REFITEMID | GUID of the referenced item | RAW(16) | Key |
| 7 | DOCCAT | Document category of the owning EWM document | CHAR(3) | |
| 8 | REFBSKEY | Business system key the reference points into — which connected system owns the number | CHAR(60) | |
| 9 | REFDOCNO | Readable reference document number, typically the ERP delivery number | CHAR(35) | |
| 10 | REFITEMNO | Readable reference item number, typically the ERP delivery item | NUMC(10) | |
| 11 | TSTFR | Reference valid-from time | DEC(15) | UTCFilter date |
| 12 | TSTTO | Reference valid-to time | DEC(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.
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
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 onlyON 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 onlyON 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
- /SCWM/IDNMaintain the inbound delivery notification — the request document that arrives from the connected ERP system before the inbound delivery existsRead accessChangedelivery-processing
- /SCWM/ODRMaintain the outbound delivery request — the request document that precedes the outbound delivery orderRead accessChangedelivery-processing
- /SCWM/PRDIMaintain the inbound delivery — the EWM-side receipt document goods receipt is posted againstRead accessChangedelivery-processing
- /SCWM/PRDOMaintain the outbound delivery order — the document EWM plans, picks, and stages against before goods issueRead accessChangedelivery-processing
More Delivery Processing (Warehouse Requests) tables
- /SCDL/DB_REQHDelivery request header — the notification or request EWM received before the processing document existed, inbound (IDR) or outbound (ODR)
- /SCDL/DB_REQIDelivery request item — the line grain of the inbound notification or outbound request, with product, batch, quantity, and entitled party
- /SCDL/DB_STATUSDelivery 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
- /SCDL/DB_DATEDelivery dates — the typed date table for the /SCDL layer, one row per document, item, schedule line, date type, and category, each carrying a from/to timestamp pair
- /SCDL/DB_DLVH_OFinal outbound delivery header — the document that exists after goods issue, carrying the shipped delivery's number, type, incoterms, sales organization, and the flags that mark corrections, pickups, and scrapping
- /SCDL/DB_DLVI_OFinal outbound delivery item — the shipped line, carrying its own item GUID plus the reference document and item it was created from in both GUID and readable form