/SCWM/HUHDR
transactionGUID keyHandling 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
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.
- 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
18 fields · 2 key
18 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | GUID_HU | Internal GUID of the handling unit — the join handle from available quants, the LIME tree, and task HU references | RAW(16) | Key |
| 3 | HUIDENT | External handling-unit identification — the human-readable HU number, often an SSCC | CHAR(20) | |
| 4 | PMAT_GUID | GUID of the packaging material product | RAW(16) | |
| 5 | LGNUM | Warehouse number the handling unit lives in | CHAR(4) | |
| 6 | LETYP | Handling unit type | CHAR(4) | |
| 7 | CREATED_BY | User who created the handling unit | CHAR(12) | |
| 8 | CREATED_AT | Handling unit creation time | DEC(15) | UTCFilter date |
| 9 | CHANGED_AT | Last change time | DEC(15) | |
| 10 | G_WEIGHT | Total (gross) weight of the handling unit | QUAN(15,3) | |
| 11 | T_WEIGHT | Tare weight of the packaging | QUAN(15,3) | |
| 12 | UNIT_GW | Unit for the weight figures | UNIT(3) | |
| 13 | G_VOLUME | Total volume of the handling unit | QUAN(15,3) | |
| 14 | UNIT_GV | Unit for the volume figures | UNIT(3) | |
| 15 | ENTITLED | Party entitled to dispose of the stock in the handling unit | CHAR(10) | |
| 16 | WSTYP | Storage type where the handling unit currently sits | CHAR(4) | |
| 17 | WSBIN | Storage bin where the handling unit currently sits | CHAR(18) | |
| 18 | TOP | Flag: the highest-level handling unit in a nesting hierarchy | CHAR(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.
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
ON scwm_aqua.MANDT = scwm_huhdr.MANDT AND scwm_aqua.HUIDENT = scwm_huhdr.HUIDENT AND scwm_aqua.LGNUM = scwm_huhdr.LGNUMON 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 equalitythe /SCWM side is RAW(16) and MATKEY keys the CHAR 22 compressed form — convert before comparing; this is not a raw equality
ON scwm_huhdr.MANDT = scwm_lagp.MANDT AND scwm_huhdr.WSBIN = scwm_lagp.LGPLA AND scwm_huhdr.LGNUM = scwm_lagp.LGNUMON 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 onlyON 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 estatethe 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
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'sthe counted handling unit, joined on the readable HU number and its own warehouse column (LGNUM_HU), not on the location's
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 itthe transportation unit seen as a handling unit, which is how loaded stock hangs off it
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 initialpopulated 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
- /SCWM/ADGIPost an unplanned goods issue — take stock out of the warehouse without a delivery behind itRead accessCreatestock-hu
- /SCWM/ADHUCreate an ad-hoc warehouse task for a handling unit — move a whole HU rather than a product quantityRead accessCreatestock-hu
- /SCWM/MONThe warehouse monitor — the single screen operations works from, with drill-downs across tasks, orders, stock, handling units, deliveries, and resourcesRead accessList / Monitorwarehouse-tasks
- /SCWM/PACKGeneral packing — build, repack, and unpack handling units at a work centerRead/write accessChangestock-hu
More Stock & Handling Units tables
- /SCWM/QUANQuant attributes — the descriptive side of a stock item (units, weight, volume, goods-receipt time, shelf life, country of origin, and the document reference for special stock), keyed by the stock GUID
- /LIME/NQUANThe LIME stock quantities table — the physical quantity of a stock item hanging on one node of the location/handling-unit tree, one row per stock GUID per node per unit of measure
- /LIME/NTREEThe LIME tree structure — one row per node of the location and handling-unit hierarchy stock hangs on, with its object type, its parent node, and the nested-set interval bookkeeping the engine walks the tree with
- /SCWM/AQUAAvailable quants — the stock that warehouse task creation can actually consume, with the bin, handling unit, product, stock type, batch, owner, and entitled party all resolved onto one row