/SCWM/BINMAT
masterMixed keyFixed bin assignment — the products that live in a named bin for a given entitled party, with the minimum, maximum, and replenishment quantities slotting maintains
The key mixes readable columns (warehouse, entitled party, bin) with one RAW16 product GUID (MATID) — a partial-GUID key, which is why this table is badged mixed rather than guid. MATNR is carried denormalized alongside the GUID, so simple reads don't need the product bridge. Also present as a shallow entry in the SAP reference's EWM module; this reference is authoritative for the /SCWM namespace going forward.
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
15 fields · 5 key
15 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | LGNUM | EWM warehouse number | CHAR(4) | Key |
| 3 | MATID | Product GUID — the RAW16 form; resolve to a material number through the product master bridge | RAW(16) | Key |
| 4 | ENTITLED | Party entitled to dispose the assignment applies to | CHAR(10) | Key |
| 5 | LGPLA | Fixed storage bin for the product | CHAR(18) | Key |
| 6 | LGTYP | Storage type of the fixed bin | CHAR(4) | |
| 7 | OUTCON | Flag set by slotting: the bin assignment is considered improvable | CHAR(1) | |
| 8 | MAXQTY | Maximum replenishment-planning quantity for the product in the bin | QUAN(15,3) | |
| 9 | MAXQTY_UOM_DSP | Display unit for the maximum quantity | UNIT(3) | |
| 10 | MINQTY | Minimum quantity that triggers planned replenishment | QUAN(15,3) | |
| 11 | MINQTY_UOM_DSP | Display unit for the minimum quantity | UNIT(3) | |
| 12 | MATNR | Material number carried denormalized alongside the product GUID | CHAR(40) | |
| 13 | RMMQTY_FIX | Flag: the minimum, maximum, and replenishment quantities are fixed against slotting | CHAR(1) | |
| 14 | CREATED_AT | Time the assignment was created | DEC(15) | UTCFilter date |
| 15 | CREATED_BY | User who created the assignment | CHAR(12) |
Field provenance: hand-curated. 5 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /SCWM/BINMATon 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.
8 parameters not filled: <catalog>, <schema>, <client>, <LGNUM>, <MATID>, <LGPLA>, <TS_FROM>, <TS_TO>
-- ============================================================
-- Table : /SCWM/BINMAT — Fixed bin assignment — the products that live in a named bin for a given entitled party, with the minimum, maximum, and replenishment quantities slotting maintains
-- Purpose: Column-selected read of /SCWM/BINMAT — auto-generated from field metadata
-- Grain : One row per client + LGNUM + MATID + ENTITLED + LGPLA
-- Notes : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/BINMAT; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_binmat — 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.LGNUM AS "EWM warehouse number",
t.MATID AS "Product GUID — the RAW16 form; resolve to a material number through the product master bridge",
lower(hex(t.MATID)) AS "Product GUID — the RAW16 form; resolve to a material number through the product master bridge (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.ENTITLED AS "Party entitled to dispose the assignment applies to",
t.LGPLA AS "Fixed storage bin for the product",
t.LGTYP AS "Storage type of the fixed bin",
t.OUTCON AS "Flag set by slotting: the bin assignment is considered improvable",
t.MAXQTY AS "Maximum replenishment-planning quantity for the product in the bin",
t.MAXQTY_UOM_DSP AS "Display unit for the maximum quantity",
t.MINQTY AS "Minimum quantity that triggers planned replenishment",
t.MINQTY_UOM_DSP AS "Display unit for the minimum quantity",
t.MATNR AS "Material number carried denormalized alongside the product GUID",
t.RMMQTY_FIX AS "Flag: the minimum, maximum, and replenishment quantities are fixed against slotting",
t.CREATED_AT AS "Time the assignment was created", -- UTC
t.CREATED_BY AS "User who created the assignment"
FROM <catalog>.<schema>.scwm_binmat t
WHERE
t.MANDT = '<client>' -- client filter — drop on single-client systems
-- AND t.LGNUM = '<LGNUM>'
-- AND t.MATID = unhex('<MATID>') -- pass the 32-character hex form
-- AND t.LGPLA = '<LGPLA>'
-- AND t.CREATED_AT >= <TS_FROM> -- UTC yyyymmddhhmmss — convert warehouse-local dates first (#utc-timestamps)
-- AND t.CREATED_AT <= <TS_TO>
ORDER BY t.LGNUM;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_binmat.MANDT = scwm_lagp.MANDT AND scwm_binmat.LGPLA = scwm_lagp.LGPLA AND scwm_binmat.LGNUM = scwm_lagp.LGNUMON scwm_binmat.MANDT = sapapo_matkey.MANDT AND scwm_binmat.MATID = 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
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 Storage Bins tables
- /SCWM/LAGPThe storage bin master — one row per bin in a warehouse, with its storage type and section, the three block indicators, capacity limits, empty/full flags, and the layout coordinates the pick path is built from
- /SCWM/LAGPSBin assignments to activity areas — one row per bin per activity, carrying the sort sequence that determines the order an operator walks the bins
- /SCWM/T303Storage bin types — the weight, volume, capacity, and packing-dimension limits a bin of each type accepts