Skip to content
EWM Reference

/SCWM/HUHDR

transactionGUID key

Handling unit header — one row per HU with its external number, packaging material, current storage type and bin, weights, volumes, and the entitled party whose stock it holds

Notes

The HU type field is LETYP, not HUTYP, and there is no higher-HU column: nesting shows up through the TOP/BOTTOM flags plus the LIME tree, and the GUID_HU_TOP column on the DDIC page is explicitly marked not for use. The packing instructions behind an HU are the packaging specifications, cataloged in the master data module.

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.
Used in the library

Fields

18 fields · 2 key

18 fields.

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1MANDTClientCLNT(3)
Key
2GUID_HUInternal GUID of the handling unit — the join handle from available quants, the LIME tree, and task HU referencesRAW(16)
Key
3HUIDENTExternal handling-unit identification — the human-readable HU number, often an SSCCCHAR(20)
4PMAT_GUIDGUID of the packaging material productRAW(16)
5LGNUMWarehouse number the handling unit lives inCHAR(4)
6LETYPHandling unit typeCHAR(4)
7CREATED_BYUser who created the handling unitCHAR(12)
8CREATED_ATHandling unit creation timeDEC(15)
UTCFilter date
9CHANGED_ATLast change timeDEC(15)
10G_WEIGHTTotal (gross) weight of the handling unitQUAN(15,3)
11T_WEIGHTTare weight of the packagingQUAN(15,3)
12UNIT_GWUnit for the weight figuresUNIT(3)
13G_VOLUMETotal volume of the handling unitQUAN(15,3)
14UNIT_GVUnit for the volume figuresUNIT(3)
15ENTITLEDParty entitled to dispose of the stock in the handling unitCHAR(10)
16WSTYPStorage type where the handling unit currently sitsCHAR(4)
17WSBINStorage bin where the handling unit currently sitsCHAR(18)
18TOPFlag: the highest-level handling unit in a nesting hierarchyCHAR(1)

Field provenance: hand-curated. 2 key fields.

Boilerplate SQL

Starting point for reading the replicated copy of /SCWM/HUHDRon 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>, <GUID_HU>, <TS_FROM>, <TS_TO>

-- ============================================================
-- Table  : /SCWM/HUHDR — Handling unit header — one row per HU with its external number, packaging material, current storage type and bin, weights, volumes, and the entitled party whose stock it holds
-- Purpose: Column-selected read of /SCWM/HUHDR — auto-generated from field metadata
-- Grain  : One row per client + GUID_HU
-- Notes  : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/HUHDR; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_huhdr — 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.GUID_HU AS "Internal GUID of the handling unit — the join handle from available quants, the LIME tree, and task HU references",
  lower(hex(t.GUID_HU)) AS "Internal GUID of the handling unit — the join handle from available quants, the LIME tree, and task HU references (hex)",  -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
  t.HUIDENT AS "External handling-unit identification — the human-readable HU number, often an SSCC",
  t.PMAT_GUID AS "GUID of the packaging material product",
  lower(hex(t.PMAT_GUID)) AS "GUID of the packaging material product (hex)",  -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
  t.LGNUM AS "Warehouse number the handling unit lives in",
  t.LETYP AS "Handling unit type",
  t.CREATED_BY AS "User who created the handling unit",
  t.CREATED_AT AS "Handling unit creation time",  -- UTC
  t.CHANGED_AT AS "Last change time",  -- UTC
  t.G_WEIGHT AS "Total (gross) weight of the handling unit",
  t.T_WEIGHT AS "Tare weight of the packaging",
  t.UNIT_GW AS "Unit for the weight figures",
  t.G_VOLUME AS "Total volume of the handling unit",
  t.UNIT_GV AS "Unit for the volume figures",
  t.ENTITLED AS "Party entitled to dispose of the stock in the handling unit",
  t.WSTYP AS "Storage type where the handling unit currently sits",
  t.WSBIN AS "Storage bin where the handling unit currently sits",
  t.TOP AS "Flag: the highest-level handling unit in a nesting hierarchy"
FROM <catalog>.<schema>.scwm_huhdr t
WHERE
  t.MANDT = '<client>'  -- client filter — drop on single-client systems
  -- AND t.GUID_HU = unhex('<GUID_HU>')  -- pass the 32-character hex form
  -- AND t.CREATED_AT >= <TS_FROM>  -- UTC yyyymmddhhmmss — convert warehouse-local dates first (#utc-timestamps)
  -- AND t.CREATED_AT <= <TS_TO>
ORDER BY t.GUID_HU;

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

  • /SCWM/AQUA/SCWM/HUHDRforeign key · N:1
    ON scwm_aqua.MANDT = scwm_huhdr.MANDT AND scwm_aqua.HUIDENT = scwm_huhdr.HUIDENT AND scwm_aqua.LGNUM = scwm_huhdr.LGNUM
  • /SCWM/HUHDR/SAPAPO/MATKEYGUID join · N:1
    ON scwm_huhdr.MANDT = sapapo_matkey.MANDT AND scwm_huhdr.PMAT_GUID = sapapo_matkey.MATID -- the /SCWM side is RAW(16) and MATKEY keys the CHAR 22 compressed form — convert before comparing; this is not a raw equality

    the /SCWM side is RAW(16) and MATKEY keys the CHAR 22 compressed form — convert before comparing; this is not a raw equality

  • /SCWM/HUHDR/SCWM/LAGPforeign key · N:1
    ON scwm_huhdr.MANDT = scwm_lagp.MANDT AND scwm_huhdr.WSBIN = scwm_lagp.LGPLA AND scwm_huhdr.LGNUM = scwm_lagp.LGNUM
  • /SCWM/RSRC/SCWM/HUHDRGUID join · N:1
    ON scwm_rsrc.MANDT = scwm_huhdr.MANDT AND scwm_rsrc.GUID_HU = scwm_huhdr.GUID_HU -- RAW16 GUID equality — join raw; hex is for display/conformance only
  • /SCDL/DB_HU/SCWM/HUHDRforeign key · N:1
    ON scdl_db_hu.MANDT = scwm_huhdr.MANDT AND scdl_db_hu.HUNO = scwm_huhdr.HUIDENT -- the delivery-side HU to the warehouse-side HU on the READABLE number: nothing public says the /SCDL HUID equals /SCWM/HUHDR's GUID_HU, so no GUID equality is asserted here. HU numbers are unique per warehouse and this table carries no warehouse column — qualify through the delivery header's warehouse before trusting this join in a multi-warehouse estate

    the delivery-side HU to the warehouse-side HU on the READABLE number: nothing public says the /SCDL HUID equals /SCWM/HUHDR's GUID_HU, so no GUID equality is asserted here. HU numbers are unique per warehouse and this table carries no warehouse column — qualify through the delivery header's warehouse before trusting this join in a multi-warehouse estate

  • /LIME/PI_IT_BIZ/SCWM/HUHDRforeign key · N:1
    ON lime_pi_it_biz.MANDT = scwm_huhdr.MANDT AND lime_pi_it_biz.HUIDENT = scwm_huhdr.HUIDENT AND lime_pi_it_biz.LGNUM_HU = scwm_huhdr.LGNUM -- the counted handling unit, joined on the readable HU number and its own warehouse column (LGNUM_HU), not on the location's

    the counted handling unit, joined on the readable HU number and its own warehouse column (LGNUM_HU), not on the location's

  • /SCWM/TUNIT/SCWM/HUHDRGUID join · 1:1
    ON scwm_tunit.MANDT = scwm_huhdr.MANDT AND scwm_tunit.HU_ID = scwm_huhdr.GUID_HU -- RAW16 GUID equality — join raw; hex is for display/conformance only · the transportation unit seen as a handling unit, which is how loaded stock hangs off it

    the transportation unit seen as a handling unit, which is how loaded stock hangs off it

  • /SCWM/TU_DLV/SCWM/HUHDRGUID join · N:1
    ON scwm_tu_dlv.MANDT = scwm_huhdr.MANDT AND scwm_tu_dlv.TOP_HU = scwm_huhdr.GUID_HU -- RAW16 GUID equality — join raw; hex is for display/conformance only · populated on handling-unit assignments; delivery-level assignment rows leave it initial

    populated on handling-unit assignments; delivery-level assignment rows leave it initial

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 Stock & Handling Units tables

More Stock & Handling Units 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.