/SCDL/DB_DATE
transactionMixed keyDOCCAT: IDRDOCCAT: ODRDOCCAT: PDIDOCCAT: PDODOCCAT: FDODelivery 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
Typed and long — pick the TSTTYPE (and TST_CATEGORY) you mean before joining, or one delivery contributes a row per planned and actual event it carries
Six key columns, three of them GUIDs. The TZONE column beside each timestamp pair is what turns the stored UTC values into warehouse-local ones for a service-level measure.
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
11 fields · 6 key
11 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | DOCID | GUID of the delivery document | RAW(16) | Key |
| 3 | ITEMID | GUID of the delivery item — initial for header-level dates | RAW(16) | Key |
| 4 | SLINEID | GUID of the schedule line the date belongs to | RAW(16) | Key |
| 5 | TSTTYPE | Date and time type code — which planned or actual event the row represents | CHAR(12) | Key |
| 6 | TST_CATEGORY | Date and time category qualifying the type | CHAR(6) | Key |
| 7 | DOCCAT | Document category of the owning document | CHAR(3) | |
| 8 | TZONE | Time zone reference for the timestamp pair | CHAR(6) | |
| 9 | TSTFR | From-timestamp of the date entry | DEC(15) | UTCFilter date |
| 10 | TSTTO | To-timestamp of the date entry | DEC(15) | |
| 11 | DATE_INDICATOR | How the value was determined — the planned against actual determination indicator | CHAR(1) |
Field provenance: hand-curated. 6 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /SCDL/DB_DATEon 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>, <SLINEID>, <TSTTYPE>, <TST_CATEGORY>, <TS_FROM>, <TS_TO>
-- ============================================================
-- Table : /SCDL/DB_DATE — Delivery 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
-- Purpose: Column-selected read of /SCDL/DB_DATE — auto-generated from field metadata
-- Grain : One row per client + DOCID + ITEMID + SLINEID + TSTTYPE + TST_CATEGORY
-- Caution: Typed and long — pick the TSTTYPE (and TST_CATEGORY) you mean before joining, or one delivery contributes a row per planned and actual event it carries
-- 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_DATE; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scdl_db_date — 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 delivery document",
lower(hex(t.DOCID)) AS "GUID of the 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 delivery item — initial for header-level dates",
lower(hex(t.ITEMID)) AS "GUID of the delivery item — initial for header-level dates (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.SLINEID AS "GUID of the schedule line the date belongs to",
lower(hex(t.SLINEID)) AS "GUID of the schedule line the date belongs to (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.TSTTYPE AS "Date and time type code — which planned or actual event the row represents",
t.TST_CATEGORY AS "Date and time category qualifying the type",
t.DOCCAT AS "Document category of the owning document",
t.TZONE AS "Time zone reference for the timestamp pair",
t.TSTFR AS "From-timestamp of the date entry", -- UTC
t.TSTTO AS "To-timestamp of the date entry", -- UTC
t.DATE_INDICATOR AS "How the value was determined — the planned against actual determination indicator"
FROM <catalog>.<schema>.scdl_db_date 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.SLINEID = unhex('<SLINEID>') -- pass the 32-character hex form
-- AND t.TSTTYPE = '<TSTTYPE>'
-- AND t.TST_CATEGORY = '<TST_CATEGORY>'
-- 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_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_proch_i.MANDT = scdl_db_date.MANDT AND scdl_db_proch_i.DOCID = scdl_db_date.DOCID -- RAW16 GUID equality — join raw; hex is for display/conformance onlyON scdl_db_proch_o.MANDT = scdl_db_date.MANDT AND scdl_db_proch_o.DOCID = scdl_db_date.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/PRDIMaintain the inbound delivery — the EWM-side receipt document goods receipt is posted againstRead/write accessChangedelivery-processing
- /SCWM/PRDOMaintain the outbound delivery order — the document EWM plans, picks, and stages against before goods issueRead/write accessChangedelivery-processing
More Delivery Processing (Warehouse Requests) tables
- /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
- /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