/SCDL/DB_REQI
transactionGUID keyDOCCAT: IDRDOCCAT: ODRDelivery request item — the line grain of the inbound notification or outbound request, with product, batch, quantity, and entitled party
Like its header, no readable document or item number columns are visible on the DDIC page — join through /SCDL/DB_REFDOC when a request has to be tied back to an ERP number.
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_REQI items join back to their header /SCDL/DB_REQH on the document key, so an item never fans out.
The /SCDL layer is shared: this table holds IDR (inbound delivery request), ODR (outbound delivery request) rows in the same table, discriminated by DOCCAT — pick the one you mean before joining. How DOCCAT works
Fields
15 fields · 3 key
15 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | DOCID | Document GUID of the owning request header | RAW(16) | Key |
| 3 | ITEMID | Item GUID | RAW(16) | Key |
| 4 | DOCCAT | Document category — inbound notification or outbound request; always filter it | CHAR(3) | |
| 5 | ITEMCAT | Item category | CHAR(3) | |
| 6 | ITEMTYPE | Item type | CHAR(4) | |
| 7 | CRETST | Item creation time | DEC(15) | UTCFilter date |
| 8 | CHGTST | Last change time | DEC(15) | |
| 9 | PRODUCTID | Product GUID (RAW16 form) | RAW(16) | |
| 10 | PRODUCTNO | Readable product number | CHAR(40) | |
| 11 | BATCHNO | Batch number | CHAR(20) | |
| 12 | QTY | Request item quantity | QUAN(31,14) | |
| 13 | UOM | Unit of measure | UNIT(3) | |
| 14 | ENTITLED | Party entitled to dispose | CHAR(10) | |
| 15 | STOCK_USAGE | Stock usage classification | CHAR(1) |
Field provenance: hand-curated. 3 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /SCDL/DB_REQIon 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_REQI — Delivery request item — the line grain of the inbound notification or outbound request, with product, batch, quantity, and entitled party
-- Purpose: Column-selected read of /SCDL/DB_REQI — 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_REQI; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scdl_db_reqi — 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 request header",
lower(hex(t.DOCID)) AS "Document GUID of the owning request header (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.ITEMID AS "Item GUID",
lower(hex(t.ITEMID)) AS "Item GUID (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.DOCCAT AS "Document category — inbound notification or outbound request; always filter it",
t.ITEMCAT AS "Item category",
t.ITEMTYPE AS "Item type",
t.CRETST AS "Item creation time", -- UTC
t.CHGTST AS "Last change time", -- UTC
t.PRODUCTID AS "Product GUID (RAW16 form)",
lower(hex(t.PRODUCTID)) AS "Product GUID (RAW16 form) (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.PRODUCTNO AS "Readable product number",
t.BATCHNO AS "Batch number",
t.QTY AS "Request item quantity",
t.UOM AS "Unit of measure",
t.ENTITLED AS "Party entitled to dispose",
t.STOCK_USAGE AS "Stock usage classification"
FROM <catalog>.<schema>.scdl_db_reqi t
WHERE
t.MANDT = '<client>' -- client filter — drop on single-client systems
AND t.DOCCAT = '<IDR|ODR>' -- 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_reqh.MANDT = scdl_db_reqi.MANDT AND scdl_db_reqh.DOCID = scdl_db_reqi.DOCIDON scdl_db_reqi.MANDT = sapapo_matkey.MANDT AND scdl_db_reqi.PRODUCTID = sapapo_matkey.MATID -- the /SCWM side is RAW(16) and MATKEY keys the CHAR 22 compressed form — convert before comparing; this is not a raw equalitythe /SCWM side is RAW(16) and MATKEY keys the CHAR 22 compressed form — convert before comparing; this is not a raw equality
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/write accessChangedelivery-processing
- /SCWM/ODRMaintain the outbound delivery request — the request document that precedes the outbound delivery orderRead/write accessChangedelivery-processing
More Delivery Processing (Warehouse Requests) tables
- /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
- /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