Skip to content
EWM Reference

/SCDL/DB_PROCH_O

transactionGUID keyDOCCAT: PDO

Outbound delivery order header — the EWM-side outbound document with its readable number, type, warehouse, ship-to and carrier parties, route, and sales organization

Notes

The outbound delivery order (PDO) is the document EWM plans and picks against; the final outbound delivery (FDO) that follows goods issue is a separate pair of tables deferred to R2. CRETST_WH is warehouse-local, not UTC.

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_PROCH_O is the header for its items in /SCDL/DB_PROCI_O.

Document categories

The /SCDL layer is shared: this table holds PDO (outbound delivery order) rows, and the generated SQL anchors DOCCAT to it. How DOCCAT works

Fields

15 fields · 2 key

15 fields.

Table fields: position, field name, description, data type, and flags. 15 fields.
#FieldDescriptionTypeFlags
1MANDTClientCLNT(3)
Key
2DOCIDDocument GUID of the outbound delivery orderRAW(16)
Key
3DOCCATDocument categoryCHAR(3)
4DOCTYPEDelivery document typeCHAR(4)
5DOCNOReadable outbound delivery order numberCHAR(35)
6CRETSTCreation timeDEC(15)
UTCFilter date
7CHGTSTLast change timeDEC(15)
8WAREHOUSE_IDLocation GUID of the warehouseRAW(16)
9PARTNERTO_IDPartner GUID of the ship-to partyRAW(16)
10PARTNERCARR_IDPartner GUID of the carrierRAW(16)
11STATUSHeader status valueCHAR(1)
12ROUTE_IDRoute identificationCHAR(10)
13VKORGSales organizationCHAR(4)
14TW_STOP_IDTransit-warehouse stop referenceCHAR(10)
15CRETST_WHCreation time in the warehouse time zone — warehouse-local, not UTCDEC(15)

Field provenance: hand-curated. 2 key fields.

Boilerplate SQL

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

Query parameters

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

-- ============================================================
-- Table  : /SCDL/DB_PROCH_O — Outbound delivery order header — the EWM-side outbound document with its readable number, type, warehouse, ship-to and carrier parties, route, and sales organization
-- Purpose: Column-selected read of /SCDL/DB_PROCH_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_PROCH_O; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scdl_db_proch_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 outbound delivery order",
  lower(hex(t.DOCID)) AS "Document GUID of the outbound delivery order (hex)",  -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
  t.DOCCAT AS "Document category",
  t.DOCTYPE AS "Delivery document type",
  t.DOCNO AS "Readable outbound delivery order number",
  t.CRETST AS "Creation time",  -- UTC
  t.CHGTST AS "Last change time",  -- UTC
  t.WAREHOUSE_ID AS "Location GUID of the warehouse",
  lower(hex(t.WAREHOUSE_ID)) AS "Location GUID of the warehouse (hex)",  -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
  t.PARTNERTO_ID AS "Partner GUID of the ship-to party",
  lower(hex(t.PARTNERTO_ID)) AS "Partner GUID of the ship-to party (hex)",  -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
  t.PARTNERCARR_ID AS "Partner GUID of the carrier",
  lower(hex(t.PARTNERCARR_ID)) AS "Partner GUID of the carrier (hex)",  -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
  t.STATUS AS "Header status value",
  t.ROUTE_ID AS "Route identification",
  t.VKORG AS "Sales organization",
  t.TW_STOP_ID AS "Transit-warehouse stop reference",
  t.CRETST_WH AS "Creation time in the warehouse time zone — warehouse-local, not UTC"
FROM <catalog>.<schema>.scdl_db_proch_o t
WHERE
  t.MANDT = '<client>'  -- client filter — drop on single-client systems
  AND t.DOCCAT = 'PDO'  -- 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_PROCH_O/SCDL/DB_PROCI_Oheader item · 1:N
    ON scdl_db_proch_o.MANDT = scdl_db_proci_o.MANDT AND scdl_db_proch_o.DOCID = scdl_db_proci_o.DOCID
  • /SCDL/DB_PROCH_O/SCDL/DB_STATUSGUID join · 1:N
    ON scdl_db_proch_o.MANDT = scdl_db_status.MANDT AND scdl_db_proch_o.DOCID = scdl_db_status.DOCID -- RAW16 GUID equality — join raw; hex is for display/conformance only
  • /SCDL/DB_PROCH_O/SCDL/DB_REFDOCGUID join · 1:N
    ON scdl_db_proch_o.MANDT = scdl_db_refdoc.MANDT AND scdl_db_proch_o.DOCID = scdl_db_refdoc.DOCID -- RAW16 GUID equality — join raw; hex is for display/conformance only
  • /SCDL/DB_PROCH_O/SCDL/DB_DATEGUID join · 1:N
    ON 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

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.