Skip to content
EWM Reference

/SCDL/DB_HUREFHU

transactionGUID key

Delivery handling unit hierarchy — the parent-to-child links between nested HUs on a delivery, and nothing else

Grain note

A recursive parent/child edge list — walk it, never aggregate it: summing HU quantities across the join double-counts every unit that sits inside a nested HU

Notes

Four columns, all key: the table is pure structure. HUID is the higher-level HU and HUID_LOW the one nested inside it, and a pallet holding cartons holding cases produces a chain of rows, not one.

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.

Fields

4 fields · 4 key

4 fields.

Table fields: position, field name, description, data type, and flags. 4 fields.
#FieldDescriptionTypeFlags
1MANDTClientCLNT(3)
Key
2DOCIDDocument GUID of the delivery the nesting belongs toRAW(16)
Key
3HUIDGUID of the higher-level handling unitRAW(16)
Key
4HUID_LOWGUID of the handling unit nested inside itRAW(16)
Key

Field provenance: hand-curated. 4 key fields.

Boilerplate SQL

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

4 parameters not filled: <catalog>, <schema>, <client>, <DOCID>

-- ============================================================
-- Table  : /SCDL/DB_HUREFHU — Delivery handling unit hierarchy — the parent-to-child links between nested HUs on a delivery, and nothing else
-- Purpose: Column-selected read of /SCDL/DB_HUREFHU — auto-generated from field metadata
-- Grain  : One row per client + DOCID + HUID + HUID_LOW
-- Caution: A recursive parent/child edge list — walk it, never aggregate it: summing HU quantities across the join double-counts every unit that sits inside a nested HU
-- 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_HUREFHU; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scdl_db_hurefhu — 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 the nesting belongs to",
  lower(hex(t.DOCID)) AS "Document GUID of the delivery the nesting belongs to (hex)",  -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
  t.HUID AS "GUID of the higher-level handling unit",
  lower(hex(t.HUID)) AS "GUID of the higher-level handling unit (hex)",  -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
  t.HUID_LOW AS "GUID of the handling unit nested inside it",
  lower(hex(t.HUID_LOW)) AS "GUID of the handling unit nested inside it (hex)"  -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
FROM <catalog>.<schema>.scdl_db_hurefhu t
WHERE
  t.MANDT = '<client>'  -- client filter — drop on single-client systems
  -- AND t.DOCID = unhex('<DOCID>')  -- pass the 32-character hex form
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_HUREFHU/SCDL/DB_HUGUID join · N:1
    ON scdl_db_hurefhu.MANDT = scdl_db_hu.MANDT AND scdl_db_hurefhu.HUID = scdl_db_hu.HUID AND scdl_db_hurefhu.DOCID = scdl_db_hu.DOCID -- RAW16 GUID equality — join raw; hex is for display/conformance only · the higher-level side of the nesting

    the higher-level side of the nesting

  • /SCDL/DB_HUREFHU/SCDL/DB_HUGUID join · N:1
    ON scdl_db_hurefhu.MANDT = scdl_db_hu.MANDT AND scdl_db_hurefhu.HUID_LOW = scdl_db_hu.HUID AND scdl_db_hurefhu.DOCID = scdl_db_hu.DOCID -- RAW16 GUID equality — join raw; hex is for display/conformance only · the nested side — the two edges together are one recursive hierarchy, not two independent joins

    the nested side — the two edges together are one recursive hierarchy, not two independent joins

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.