/SAPAPO/MATLWH
masterGUID keyWarehouse product — the warehouse-level settings for a product: putaway and stock-removal control, storage section and bin type indicators, stock determination, two-step picking relevance, and the slotting demand quantity
There is no LGNUM column: the warehouse is identified by its supply-chain-unit GUID (SCUGUID), so a readable warehouse number requires a hop through /SCMB/TOENTITY or /SCWM/T300_MD. The entitled party is a RAW16 GUID here (ENTITLED_ID), unlike the readable ENTITLED column on the /SCWM 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.
- 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
16 fields · 4 key
16 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | MATID | Product GUID in its 22-character compressed form | CHAR(22) | Key |
| 3 | SCUGUID | Supply chain unit GUID of the warehouse — there is no LGNUM column on this table | RAW(16) | Key |
| 4 | ENTITLED_ID | Party entitled to dispose, as a GUID | RAW(16) | Key |
| 5 | LVORM | Deletion flag | CHAR(1) | |
| 6 | PROCPRFL | Process block profile for the product in this warehouse | CHAR(2) | |
| 7 | PTDETIND | Control indicator for warehouse process type determination | CHAR(2) | |
| 8 | PUT_STRA | Putaway control (strategy) indicator | CHAR(4) | |
| 9 | LGBKZ | Storage section indicator for putaway | CHAR(4) | |
| 10 | LPTYP | Preferred storage bin type | CHAR(4) | |
| 11 | KZZUL | Flag: addition to existing stock is not allowed | CHAR(1) | |
| 12 | REM_STRA | Stock removal control (strategy) indicator | CHAR(4) | |
| 13 | STCKDETGR | Stock determination group | CHAR(2) | |
| 14 | L2SKR | Relevance for two-step picking | CHAR(1) | |
| 15 | DEMQTY | Demand quantity used by slotting | QUAN(15,3) | |
| 16 | CONCSTAT | Slotting status of the product in this warehouse | CHAR(1) |
Field provenance: hand-curated. 4 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /SAPAPO/MATLWHon 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>, <MATID>, <SCUGUID>, <ENTITLED_ID>
-- ============================================================
-- Table : /SAPAPO/MATLWH — Warehouse product — the warehouse-level settings for a product: putaway and stock-removal control, storage section and bin type indicators, stock determination, two-step picking relevance, and the slotting demand quantity
-- Purpose: Column-selected read of /SAPAPO/MATLWH — auto-generated from field metadata
-- Grain : One row per client + MATID + SCUGUID + ENTITLED_ID
-- Notes : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SAPAPO/MATLWH; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as sapapo_matlwh — 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.MATID AS "Product GUID in its 22-character compressed form",
t.SCUGUID AS "Supply chain unit GUID of the warehouse — there is no LGNUM column on this table",
lower(hex(t.SCUGUID)) AS "Supply chain unit GUID of the warehouse — there is no LGNUM column on this table (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.ENTITLED_ID AS "Party entitled to dispose, as a GUID",
lower(hex(t.ENTITLED_ID)) AS "Party entitled to dispose, as a GUID (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.LVORM AS "Deletion flag",
t.PROCPRFL AS "Process block profile for the product in this warehouse",
t.PTDETIND AS "Control indicator for warehouse process type determination",
t.PUT_STRA AS "Putaway control (strategy) indicator",
t.LGBKZ AS "Storage section indicator for putaway",
t.LPTYP AS "Preferred storage bin type",
t.KZZUL AS "Flag: addition to existing stock is not allowed",
t.REM_STRA AS "Stock removal control (strategy) indicator",
t.STCKDETGR AS "Stock determination group",
t.L2SKR AS "Relevance for two-step picking",
t.DEMQTY AS "Demand quantity used by slotting",
t.CONCSTAT AS "Slotting status of the product in this warehouse"
FROM <catalog>.<schema>.sapapo_matlwh t
WHERE
t.MANDT = '<client>' -- client filter — drop on single-client systems
-- AND t.MATID = '<MATID>'
-- AND t.SCUGUID = unhex('<SCUGUID>') -- pass the 32-character hex form
-- AND t.ENTITLED_ID = unhex('<ENTITLED_ID>') -- pass the 32-character hex form
ORDER BY t.MATID;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 sapapo_matlwh.MANDT = sapapo_matkey.MANDT AND sapapo_matlwh.MATID = sapapo_matkey.MATID -- compressed CHAR(22) GUID equality — join as-isON sapapo_matlwh.MANDT = scmb_toentity.MANDT AND sapapo_matlwh.SCUGUID = scmb_toentity.SCUGUID -- RAW16 GUID equality — join raw; hex is for display/conformance onlyON sapapo_matlwhst.MANDT = sapapo_matlwh.MANDT AND sapapo_matlwhst.MATID = sapapo_matlwh.MATID AND sapapo_matlwhst.SCUGUID = sapapo_matlwh.SCUGUID AND sapapo_matlwhst.ENTITLED_ID = sapapo_matlwh.ENTITLED_ID -- compressed CHAR(22) GUID equality — join as-is · the storage-type row hangs off the warehouse-product row — join the full product + supply chain unit + entitled party keythe storage-type row hangs off the warehouse-product row — join the full product + supply chain unit + entitled party key
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
More Master Data & Parties tables
- /SAPAPO/MATLWHSTWarehouse product at storage-type level — the same product's parameters narrowed to one storage type: preferred section and bin type, maximum fixed bins, and the min/max/replenishment quantity set
- /SCMB/TOENTITYSupply chain unit header — the location object EWM resolves warehouse, door, and party GUIDs against, carrying the readable identifier, the time zone, and the geo-coordinates
- /SCWM/PNPAKHPackaging specification header — the packing recipe as an iPPE node, with its status, the time it was activated, its group, and the rounding limits that decide how demand quantities are rounded to whole packs
- /SCWM/PVPAKCPackaging specification content — what is packed at a level: the product, the quantity and unit, and the mixing rules that say whether different products or batches may share the pack
- /SCWM/PVPAKLPackaging specification element — one level of the packing recipe as an iPPE variant: what packaging material is used, how much of it, and whether the level creates a handling unit
- /SAPAPO/MATKEYThe product master key table — the bridge between the internal product GUID every EWM table carries and the readable material number, with the base unit, weights, volumes, and shelf-life control