/SCDL/DB_DLVI_O
transactionGUID keyDOCCAT: FDOFinal 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
REFDOCID / REFITEMID are the predecessor link back to the delivery order item, and REFDOCNO / REFITEMNO carry the same reference in readable form. The reference is not category-typed on this table, so confirm what a reference points at through /SCDL/DB_REFDOC before treating it as the delivery order. No product or quantity columns render on the DDIC page — they sit in unexpanded include structures — so line detail is read from the delivery order item or the HU item tables.
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
Header & item
/SCDL/DB_DLVI_O items join back to their header /SCDL/DB_DLVH_O on the document key, so an item never fans out.
The /SCDL layer is shared: this table holds FDO (final outbound delivery) rows, and the generated SQL anchors DOCCAT to it. How DOCCAT works
Fields
17 fields · 3 key
17 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | DOCID | Document GUID of the owning final outbound delivery header | RAW(16) | Key |
| 3 | ITEMID | Item GUID of the shipped line | RAW(16) | Key |
| 4 | DOCCAT | Document category | CHAR(3) | |
| 5 | DOCNO | Readable delivery number, carried denormalized onto the item | CHAR(35) | |
| 6 | ITEMNO | Readable item number | NUMC(10) | |
| 7 | ITEMCAT | Item category | CHAR(3) | |
| 8 | REFDOCID | Document GUID of the predecessor the item was created from — the link back to the delivery order | RAW(16) | |
| 9 | REFITEMID | Item GUID of that predecessor item | RAW(16) | |
| 10 | REFDOCNO | Readable predecessor document number | CHAR(35) | |
| 11 | REFITEMNO | Readable predecessor item number | NUMC(10) | |
| 12 | CRETST | Item creation time | DEC(15) | UTCFilter date |
| 13 | CREUSR | Created by | CHAR(12) | |
| 14 | CHGTST | Last change time | DEC(15) | |
| 15 | CHGUSR | Last changed by | CHAR(12) | |
| 16 | CHGVERSION | Change version counter of the item | INT4(10) | |
| 17 | MANUAL | Flag: the item was created manually | CHAR(1) |
Field provenance: hand-curated. 3 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /SCDL/DB_DLVI_Oon 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>, <DOCID>, <ITEMID>, <TS_FROM>, <TS_TO>
-- ============================================================
-- Table : /SCDL/DB_DLVI_O — Final 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
-- Purpose: Column-selected read of /SCDL/DB_DLVI_O — auto-generated from field metadata
-- Grain : One row per client + DOCID + ITEMID
-- 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_DLVI_O; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scdl_db_dlvi_o — 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 of the owning final outbound delivery header",
lower(hex(t.DOCID)) AS "Document GUID of the owning final outbound delivery header (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.ITEMID AS "Item GUID of the shipped line",
lower(hex(t.ITEMID)) AS "Item GUID of the shipped line (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.DOCCAT AS "Document category",
t.DOCNO AS "Readable delivery number, carried denormalized onto the item",
t.ITEMNO AS "Readable item number",
t.ITEMCAT AS "Item category",
t.REFDOCID AS "Document GUID of the predecessor the item was created from — the link back to the delivery order",
lower(hex(t.REFDOCID)) AS "Document GUID of the predecessor the item was created from — the link back to the delivery order (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.REFITEMID AS "Item GUID of that predecessor item",
lower(hex(t.REFITEMID)) AS "Item GUID of that predecessor item (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.REFDOCNO AS "Readable predecessor document number",
t.REFITEMNO AS "Readable predecessor item number",
t.CRETST AS "Item creation time", -- UTC
t.CREUSR AS "Created by",
t.CHGTST AS "Last change time", -- UTC
t.CHGUSR AS "Last changed by",
t.CHGVERSION AS "Change version counter of the item",
t.MANUAL AS "Flag: the item was created manually"
FROM <catalog>.<schema>.scdl_db_dlvi_o t
WHERE
t.MANDT = '<client>' -- client filter — drop on single-client systems
AND t.DOCCAT = '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.CRETST >= <TS_FROM> -- UTC yyyymmddhhmmss — convert warehouse-local dates first (#utc-timestamps)
-- AND t.CRETST <= <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_dlvi_o.MANDT AND scdl_db_dlvh_o.DOCID = scdl_db_dlvi_o.DOCIDON scdl_db_dlvi_o.MANDT = scdl_db_proci_o.MANDT AND scdl_db_dlvi_o.REFDOCID = scdl_db_proci_o.DOCID AND scdl_db_dlvi_o.REFITEMID = scdl_db_proci_o.ITEMID -- RAW16 GUID equality — join raw; hex is for display/conformance only · the predecessor reference is not category-typed on the item — confirm through /SCDL/DB_REFDOC before treating it as the delivery orderthe predecessor reference is not category-typed on the item — confirm through /SCDL/DB_REFDOC before treating it as the delivery order
ON scdl_db_huitem.MANDT = scdl_db_dlvi_o.MANDT AND scdl_db_huitem.ITEMID = scdl_db_dlvi_o.ITEMID AND scdl_db_huitem.DOCID = scdl_db_dlvi_o.DOCID -- RAW16 GUID equality — join raw; hex is for display/conformance only · resolves what is inside an HU — the item GUID is the delivery item, and the FDO item authors no product column, so the product is reached by following its REFDOCID/REFITEMID back to /SCDL/DB_PROCI_O and reading PRODUCTID thereresolves what is inside an HU — the item GUID is the delivery item, and the FDO item authors no product column, so the product is reached by following its REFDOCID/REFITEMID back to /SCDL/DB_PROCI_O and reading PRODUCTID there
More Delivery Processing (Warehouse Requests) tables
- /SCDL/DB_HUDelivery handling units — the HUs attached to a delivery document, with the readable HU number, the packaging material, and the packaging specification and packing instruction that built them
- /SCDL/DB_HUIDENTAlternative handling unit identifiers — the other numbers an HU is known by, one row per identifier type
- /SCDL/DB_HUITEMDelivery handling unit contents — one row per delivery item packed into an HU, with the packed quantity and unit
- /SCDL/DB_HUREFHUDelivery handling unit hierarchy — the parent-to-child links between nested HUs on a delivery, and nothing else
- /SCDL/DB_PROCH_IInbound delivery header — the EWM-side inbound delivery document with its readable number, type, warehouse, vendor and carrier parties, status, and delivery date
- /SCDL/DB_PROCH_OOutbound delivery order header — the EWM-side outbound document with its readable number, type, warehouse, ship-to and carrier parties, route, and sales organization