Skip to content
EWM Reference

/SCDL/DB_HUITEM

transactionMixed key

Delivery handling unit contents — one row per delivery item packed into an HU, with the packed quantity and unit

Notes

The grain that answers what is physically in which HU: a delivery item split across two HUs has two rows here, and COUNTER (an integer, the one readable key column) is what keeps them apart. ITEMID points at the delivery item, so an HU can be resolved to a product only through the item tables.

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_HUITEM items join back to their header /SCDL/DB_HU on the document key, so an item never fans out.

Fields

9 fields · 5 key

9 fields.

Table fields: position, field name, description, data type, and flags. 9 fields.
#FieldDescriptionTypeFlags
1MANDTClientCLNT(3)
Key
2DOCIDDocument GUID of the deliveryRAW(16)
Key
3HUIDHandling unit GUID the content belongs toRAW(16)
Key
4ITEMIDDelivery item GUID packed into the handling unitRAW(16)
Key
5COUNTERCounter separating repeated packings of the same delivery item into the same handling unit — the one readable key columnINT4(10)
Key
6HUITEMNOReadable handling unit item numberCHAR(20)
7HUITEMIDGUID of the handling unit item itselfRAW(16)
8QTYQuantity of the delivery item packed into this handling unitQUAN(31,14)
9UOMUnit of measure of the packed quantityUNIT(3)

Field provenance: hand-curated. 5 key fields.

Boilerplate SQL

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

5 parameters not filled: <catalog>, <schema>, <client>, <DOCID>, <ITEMID>

-- ============================================================
-- Table  : /SCDL/DB_HUITEM — Delivery handling unit contents — one row per delivery item packed into an HU, with the packed quantity and unit
-- Purpose: Column-selected read of /SCDL/DB_HUITEM — auto-generated from field metadata
-- Grain  : One row per client + DOCID + HUID + ITEMID + 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_HUITEM; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scdl_db_huitem — 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 content belongs to",
  lower(hex(t.HUID)) AS "Handling unit GUID the content belongs to (hex)",  -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
  t.ITEMID AS "Delivery item GUID packed into the handling unit",
  lower(hex(t.ITEMID)) AS "Delivery item GUID packed into the handling unit (hex)",  -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
  t.COUNTER AS "Counter separating repeated packings of the same delivery item into the same handling unit — the one readable key column",
  t.HUITEMNO AS "Readable handling unit item number",
  t.HUITEMID AS "GUID of the handling unit item itself",
  lower(hex(t.HUITEMID)) AS "GUID of the handling unit item itself (hex)",  -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
  t.QTY AS "Quantity of the delivery item packed into this handling unit",
  t.UOM AS "Unit of measure of the packed quantity"
FROM <catalog>.<schema>.scdl_db_huitem t
WHERE
  t.MANDT = '<client>'  -- client filter — drop on single-client systems
  -- AND t.DOCID = unhex('<DOCID>')  -- pass the 32-character hex form
  -- AND t.ITEMID = unhex('<ITEMID>')  -- 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_HU/SCDL/DB_HUITEMheader item · 1:N
    ON scdl_db_hu.MANDT = scdl_db_huitem.MANDT AND scdl_db_hu.HUID = scdl_db_huitem.HUID AND scdl_db_hu.DOCID = scdl_db_huitem.DOCID
  • /SCDL/DB_HUITEM/SCDL/DB_DLVI_OGUID join · N:1
    ON scdl_db_huitem.MANDT = scdl_db_dlvi_o.MANDT AND scdl_db_huitem.ITEMID = scdl_db_dlvi_o.ITEMID AND scdl_db_huitem.DOCID = scdl_db_dlvi_o.DOCID -- RAW16 GUID equality — join raw; hex is for display/conformance only · resolves what is inside an HU — the item GUID is the delivery item, and the FDO item authors no product column, so the product is reached by following its REFDOCID/REFITEMID back to /SCDL/DB_PROCI_O and reading PRODUCTID there

    resolves what is inside an HU — the item GUID is the delivery item, and the FDO item authors no product column, so the product is reached by following its REFDOCID/REFITEMID back to /SCDL/DB_PROCI_O and reading PRODUCTID there

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.