Skip to content
EWM Reference

/SAPAPO/MATLWH

masterGUID key

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

Notes

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.

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.

Fields

16 fields · 4 key

16 fields.

Table fields: position, field name, description, data type, and flags. 16 fields.
#FieldDescriptionTypeFlags
1MANDTClientCLNT(3)
Key
2MATIDProduct GUID in its 22-character compressed formCHAR(22)
Key
3SCUGUIDSupply chain unit GUID of the warehouse — there is no LGNUM column on this tableRAW(16)
Key
4ENTITLED_IDParty entitled to dispose, as a GUIDRAW(16)
Key
5LVORMDeletion flagCHAR(1)
6PROCPRFLProcess block profile for the product in this warehouseCHAR(2)
7PTDETINDControl indicator for warehouse process type determinationCHAR(2)
8PUT_STRAPutaway control (strategy) indicatorCHAR(4)
9LGBKZStorage section indicator for putawayCHAR(4)
10LPTYPPreferred storage bin typeCHAR(4)
11KZZULFlag: addition to existing stock is not allowedCHAR(1)
12REM_STRAStock removal control (strategy) indicatorCHAR(4)
13STCKDETGRStock determination groupCHAR(2)
14L2SKRRelevance for two-step pickingCHAR(1)
15DEMQTYDemand quantity used by slottingQUAN(15,3)
16CONCSTATSlotting status of the product in this warehouseCHAR(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.

Query parameters

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

  • /SAPAPO/MATLWH/SAPAPO/MATKEYGUID join · N:1
    ON sapapo_matlwh.MANDT = sapapo_matkey.MANDT AND sapapo_matlwh.MATID = sapapo_matkey.MATID -- compressed CHAR(22) GUID equality — join as-is
  • /SAPAPO/MATLWH/SCMB/TOENTITYGUID join · N:1
    ON sapapo_matlwh.MANDT = scmb_toentity.MANDT AND sapapo_matlwh.SCUGUID = scmb_toentity.SCUGUID -- RAW16 GUID equality — join raw; hex is for display/conformance only
  • /SAPAPO/MATLWHST/SAPAPO/MATLWHGUID join · N:1
    ON 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 key

    the 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

Browse more Master Data & Parties tables

More Master Data & Parties 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.