/SCDL/DB_HUIDENT
transactionMixed keyAlternative handling unit identifiers — the other numbers an HU is known by, one row per identifier type
HUIDTYPE says what kind of identifier the row holds and COUNTER allows several of a kind, so an HU can carry many rows here. The 40-character HUIDENT on this table is wider than the 20-character external HU number on /SCWM/HUHDR and is not the same column — matching one against the other needs the identifier type filtered first, which is why no edge is drawn from here to the HU header.
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
Fields
6 fields · 5 key
6 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | DOCID | Document GUID of the delivery | RAW(16) | Key |
| 3 | HUID | Handling unit GUID the identifier belongs to | RAW(16) | Key |
| 4 | HUIDTYPE | Identification type — which kind of identifier the row carries | CHAR(1) | Key |
| 5 | COUNTER | Counter allowing several identifiers of the same type on one handling unit | INT4(10) | Key |
| 6 | HUIDENT | The identifier value — 40 characters here, wider than the 20-character external HU number on the warehouse-side HU header | CHAR(40) |
Field provenance: hand-curated. 5 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /SCDL/DB_HUIDENTon 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.
4 parameters not filled: <catalog>, <schema>, <client>, <DOCID>
-- ============================================================
-- Table : /SCDL/DB_HUIDENT — Alternative handling unit identifiers — the other numbers an HU is known by, one row per identifier type
-- Purpose: Column-selected read of /SCDL/DB_HUIDENT — auto-generated from field metadata
-- Grain : One row per client + DOCID + HUID + HUIDTYPE + COUNTER
-- 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_HUIDENT; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scdl_db_huident — 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",
lower(hex(t.DOCID)) AS "Document GUID of the delivery (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.HUID AS "Handling unit GUID the identifier belongs to",
lower(hex(t.HUID)) AS "Handling unit GUID the identifier belongs to (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.HUIDTYPE AS "Identification type — which kind of identifier the row carries",
t.COUNTER AS "Counter allowing several identifiers of the same type on one handling unit",
t.HUIDENT AS "The identifier value — 40 characters here, wider than the 20-character external HU number on the warehouse-side HU header"
FROM <catalog>.<schema>.scdl_db_huident 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
ON scdl_db_huident.MANDT = scdl_db_hu.MANDT AND scdl_db_huident.HUID = scdl_db_hu.HUID AND scdl_db_huident.DOCID = scdl_db_hu.DOCID -- RAW16 GUID equality — join raw; hex is for display/conformance only · several identifiers per HU — filter HUIDTYPE before joining or the HU multipliesseveral identifiers per HU — filter HUIDTYPE before joining or the HU multiplies
More Delivery Processing (Warehouse Requests) tables
- /SCDL/DB_HUITEMDelivery handling unit contents — one row per delivery item packed into an HU, with the packed quantity and unit
- /SCDL/DB_HUREFHUDelivery handling unit hierarchy — the parent-to-child links between nested HUs on a delivery, and nothing else
- /SCDL/DB_PROCH_IInbound delivery header — the EWM-side inbound delivery document with its readable number, type, warehouse, vendor and carrier parties, status, and delivery date
- /SCDL/DB_PROCH_OOutbound delivery order header — the EWM-side outbound document with its readable number, type, warehouse, ship-to and carrier parties, route, and sales organization
- /SCDL/DB_PROCI_IInbound delivery item — the line grain of the inbound delivery: product, batch, quantity, entitled party, and the goods-receipt and completion statuses
- /SCDL/DB_PROCI_OOutbound delivery order item — the line grain outbound: product, quantity, entitled party, stock owner, and the picking and goods-issue statuses