EWM Reference

/SCDL/DB_REQH

transactionGUID keyDOCCAT: IDRDOCCAT: ODR

Delivery request header — the notification or request EWM received before the processing document existed, inbound (IDR) or outbound (ODR)

Identity

Module: Delivery Processing (Warehouse Requests)Bronze: scdl_db_reqh

Classic WM

In the SAP reference: LTBK In the SAP reference: LTBP WM → EWM crosswalk

Notes

There is NO readable document number column on this header (confirmed on two mirrors) — readable numbers for request documents come through /SCDL/DB_REFDOC or the successor processing document. CHGVERSION and ACTION_CODE come from the replication message that created the row, which makes them useful for diagnosing ERP-to-EWM interface problems.

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 — LGNUM plus 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 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.

Header & item

/SCDL/DB_REQH is the header for its items in /SCDL/DB_REQI.

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

14 fields · 2 key

14 fields.

Table fields: position, field name, description, data type, and flags. 14 fields.
#	Field	Description	Type	Flags
1	MANDT	Client	CLNT(3)	Key
2	DOCID	Document GUID of the delivery request, inbound or outbound	RAW(16)	Key
3	DOCCAT	Document category — inbound notification or outbound request; always filter it	CHAR(3)
4	DOCTYPE	Request document type	CHAR(4)
5	CRETST	Creation time	DEC(15)	UTCFilter date
6	CREUSR	Created by	CHAR(12)
7	CHGTST	Last change time	DEC(15)	UTC
8	CHGVERSION	Change version counter of the replicated document	INT4(10)
9	MANUAL	Flag: the document was created manually rather than replicated	CHAR(1)
10	ACTION_CODE	Action code from the replication message	CHAR(2)
11	INCO1	Incoterms part 1	CHAR(3)
12	/SCWM/COMMIND	ERP communication indicator — a namespaced column name	CHAR(1)
13	/SCWM/LOG_PROCESS	Logistic process classification — a namespaced column name	CHAR(1)
14	TW_STOP_ID	Transit-warehouse stop reference	CHAR(10)

Field provenance: hand-curated. 2 key fields.

Boilerplate SQL

Starting point for reading the replicated copy of /SCDL/DB_REQHon 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

CatalogSchemaClient (MANDT)Document GUID (RAW16)From timestamp (yyyymmddhhmmss, UTC)To timestamp (yyyymmddhhmmss, UTC)

Include optional filters (3)

6 parameters not filled: <catalog>, <schema>, <client>, <DOCID>, <TS_FROM>, <TS_TO>

-- ============================================================
-- Table  : /SCDL/DB_REQH — Delivery request header — the notification or request EWM received before the processing document existed, inbound (IDR) or outbound (ODR)
-- Purpose: Column-selected read of /SCDL/DB_REQH — 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_REQH; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scdl_db_reqh — 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 delivery request, inbound or outbound",
  lower(hex(t.DOCID)) AS "Document GUID of the delivery request, inbound or outbound (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.DOCTYPE AS "Request document type",
  t.CRETST AS "Creation time",  -- UTC
  t.CREUSR AS "Created by",
  t.CHGTST AS "Last change time",  -- UTC
  t.CHGVERSION AS "Change version counter of the replicated document",
  t.MANUAL AS "Flag: the document was created manually rather than replicated",
  t.ACTION_CODE AS "Action code from the replication message",
  t.INCO1 AS "Incoterms part 1",
  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
  t.TW_STOP_ID AS "Transit-warehouse stop reference"
FROM <catalog>.<schema>.scdl_db_reqh 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.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

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