Skip to content
EWM Reference

/SCWM/BINMAT

masterMixed key

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

Identity
Module: Storage BinsBronze: scwm_binmat
Notes

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.

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

15 fields · 5 key

15 fields.

Table fields: position, field name, description, data type, and flags. 15 fields.
#FieldDescriptionTypeFlags
1MANDTClientCLNT(3)
Key
2LGNUMEWM warehouse numberCHAR(4)
Key
3MATIDProduct GUID — the RAW16 form; resolve to a material number through the product master bridgeRAW(16)
Key
4ENTITLEDParty entitled to dispose the assignment applies toCHAR(10)
Key
5LGPLAFixed storage bin for the productCHAR(18)
Key
6LGTYPStorage type of the fixed binCHAR(4)
7OUTCONFlag set by slotting: the bin assignment is considered improvableCHAR(1)
8MAXQTYMaximum replenishment-planning quantity for the product in the binQUAN(15,3)
9MAXQTY_UOM_DSPDisplay unit for the maximum quantityUNIT(3)
10MINQTYMinimum quantity that triggers planned replenishmentQUAN(15,3)
11MINQTY_UOM_DSPDisplay unit for the minimum quantityUNIT(3)
12MATNRMaterial number carried denormalized alongside the product GUIDCHAR(40)
13RMMQTY_FIXFlag: the minimum, maximum, and replenishment quantities are fixed against slottingCHAR(1)
14CREATED_ATTime the assignment was createdDEC(15)
UTCFilter date
15CREATED_BYUser who created the assignmentCHAR(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.

Query parameters

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

  • /SCWM/BINMAT/SCWM/LAGPforeign key · N:1
    ON scwm_binmat.MANDT = scwm_lagp.MANDT AND scwm_binmat.LGPLA = scwm_lagp.LGPLA AND scwm_binmat.LGNUM = scwm_lagp.LGNUM
  • /SCWM/BINMAT/SAPAPO/MATKEYGUID join · N:1
    ON 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 equality

    the /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

Browse more Storage Bins tables

More Storage Bins 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.