/SCDL/DB_DLVH_O
transactionGUID keyDOCCAT: FDOFinal 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
The FDO is a separate document from the outbound delivery order (PDO) EWM planned and picked against, with its own DOCID — the two are tied together through /SCDL/DB_REFDOC and through the item-level reference columns on /SCDL/DB_DLVI_O, not by sharing a document GUID. Reading outbound service levels off the PDO alone misses what actually shipped.
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_DLVH_O is the header for its items in /SCDL/DB_DLVI_O.
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
18 fields · 2 key
18 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | DOCID | Document GUID of the final outbound delivery — its own GUID, not the delivery order's | RAW(16) | Key |
| 3 | DOCCAT | Document category — the final outbound delivery category | CHAR(3) | |
| 4 | DOCTYPE | Delivery document type | CHAR(4) | |
| 5 | DOCNO | Readable outbound delivery number | CHAR(35) | |
| 6 | CRETST | Creation time of the final delivery — in practice the goods-issue moment the document was cut at | DEC(15) | UTCFilter date |
| 7 | CREUSR | Created by | CHAR(12) | |
| 8 | CHGTST | Last change time | DEC(15) | |
| 9 | CHGUSR | Last changed by | CHAR(12) | |
| 10 | CHGVERSION | Change version counter of the document | INT4(10) | |
| 11 | MANUAL | Flag: the delivery was created manually rather than by the process | CHAR(1) | |
| 12 | VKORG | Sales organization the delivery belongs to | CHAR(4) | |
| 13 | INCO1 | Incoterms part 1 | CHAR(3) | |
| 14 | /SCWM/CORRIND | Flag: the document is a correction delivery — a namespaced column name | CHAR(1) | |
| 15 | /SCWM/PICKUPIND | Flag: the goods were picked up rather than shipped — a namespaced column name | CHAR(1) | |
| 16 | /SCWM/SCRAPPIND | Flag: the delivery is a scrapping — a namespaced column name | CHAR(1) | |
| 17 | /SCWM/COMMIND | ERP communication indicator — a namespaced column name | CHAR(1) | |
| 18 | /SCWM/LOG_PROCESS | Logistic process classification — a namespaced column name | CHAR(1) |
Field provenance: hand-curated. 2 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /SCDL/DB_DLVH_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.
6 parameters not filled: <catalog>, <schema>, <client>, <DOCID>, <TS_FROM>, <TS_TO>
-- ============================================================
-- Table : /SCDL/DB_DLVH_O — Final 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
-- Purpose: Column-selected read of /SCDL/DB_DLVH_O — auto-generated from field metadata
-- Grain : One row per client + DOCID
-- 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_DLVH_O; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scdl_db_dlvh_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 final outbound delivery — its own GUID, not the delivery order's",
lower(hex(t.DOCID)) AS "Document GUID of the final outbound delivery — its own GUID, not the delivery order's (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.DOCCAT AS "Document category — the final outbound delivery category",
t.DOCTYPE AS "Delivery document type",
t.DOCNO AS "Readable outbound delivery number",
t.CRETST AS "Creation time of the final delivery — in practice the goods-issue moment the document was cut at", -- 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 document",
t.MANUAL AS "Flag: the delivery was created manually rather than by the process",
t.VKORG AS "Sales organization the delivery belongs to",
t.INCO1 AS "Incoterms part 1",
t.`/SCWM/CORRIND` AS "Flag: the document is a correction delivery — a namespaced column name", -- namespaced column — most replication targets rename it; see quirks guide #namespace-slashes
t.`/SCWM/PICKUPIND` AS "Flag: the goods were picked up rather than shipped — a namespaced column name", -- namespaced column — most replication targets rename it; see quirks guide #namespace-slashes
t.`/SCWM/SCRAPPIND` AS "Flag: the delivery is a scrapping — a namespaced column name", -- namespaced column — most replication targets rename it; see quirks guide #namespace-slashes
t.`/SCWM/COMMIND` AS "ERP communication indicator — a namespaced column name", -- namespaced column — most replication targets rename it; see quirks guide #namespace-slashes
t.`/SCWM/LOG_PROCESS` AS "Logistic process classification — a namespaced column name" -- namespaced column — most replication targets rename it; see quirks guide #namespace-slashes
FROM <catalog>.<schema>.scdl_db_dlvh_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.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_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 onlyON 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_dlvh_o.MANDT = scdl_db_date.MANDT AND scdl_db_dlvh_o.DOCID = scdl_db_date.DOCID -- RAW16 GUID equality — join raw; hex is for display/conformance onlyON scdl_db_hu.MANDT = scdl_db_dlvh_o.MANDT AND scdl_db_hu.DOCID = scdl_db_dlvh_o.DOCID -- RAW16 GUID equality — join raw; hex is for display/conformance only · the same table also holds the HUs of the other /SCDL document categories — DOCID identifies which document, whatever its categorythe same table also holds the HUs of the other /SCDL document categories — DOCID identifies which document, whatever its category
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 Delivery Processing (Warehouse Requests) tables
- /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
- /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