Skip to content
EWM Reference

/SCDL/DB_REQI

transactionGUID keyDOCCAT: IDRDOCCAT: ODR

Delivery request item — the line grain of the inbound notification or outbound request, with product, batch, quantity, and entitled party

Notes

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.

Structural facts — how the table is keyed, not a trap by itself

Semantic key
Every non-client key column is readable business data — LGNUM plus a bin, task, or order number. Joins run on the columns you can see (see the quirks guide).

Join & extract hazards — verify before you rely on this

GUID key
Every non-client key column is a GUID — RAW(16) on the /SCWM, /SCDL, /LIME, and /SCMB tables, and the CHAR(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.
In field listings, the Key chip marks a primary-key field, and UTC marks a timestamp stored in UTC rather than warehouse-local time.

Header & item

/SCDL/DB_REQI items join back to their header /SCDL/DB_REQH on the document key, so an item never fans out.

Document categories

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.

Table fields: position, field name, description, data type, and flags. 15 fields.
#FieldDescriptionTypeFlags
1MANDTClientCLNT(3)
Key
2DOCIDDocument GUID of the owning request headerRAW(16)
Key
3ITEMIDItem GUIDRAW(16)
Key
4DOCCATDocument category — inbound notification or outbound request; always filter itCHAR(3)
5ITEMCATItem categoryCHAR(3)
6ITEMTYPEItem typeCHAR(4)
7CRETSTItem creation timeDEC(15)
UTCFilter date
8CHGTSTLast change timeDEC(15)
9PRODUCTIDProduct GUID (RAW16 form)RAW(16)
10PRODUCTNOReadable product numberCHAR(40)
11BATCHNOBatch numberCHAR(20)
12QTYRequest item quantityQUAN(31,14)
13UOMUnit of measureUNIT(3)
14ENTITLEDParty entitled to disposeCHAR(10)
15STOCK_USAGEStock usage classificationCHAR(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.

Query parameters

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

  • /SCDL/DB_REQH/SCDL/DB_REQIheader item · 1:N
    ON scdl_db_reqh.MANDT = scdl_db_reqi.MANDT AND scdl_db_reqh.DOCID = scdl_db_reqi.DOCID
  • /SCDL/DB_REQI/SAPAPO/MATKEYGUID join · N:1
    ON 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 equality

    the /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

Browse more Delivery Processing (Warehouse Requests) tables

More Delivery Processing (Warehouse Requests) tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by SAP. SAP, SAP S/4HANA, and SAP Extended Warehouse Management are trademarks or registered trademarks of SAP SE.