/SCWM/LAGP
masterSemantic keyThe 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
The key is warehouse + bin: unlike classic WM's LAGP, storage type is NOT part of the EWM key — bins are unique within the warehouse and LGTYP is an attribute. Two RAW16 columns on the DDIC page (GUID_LOC, GUID_HU) are carried for legacy data and were not curated here, which is why the bin master stays a semantic-key table.
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 · 3 key
18 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | LGNUM | EWM warehouse number | CHAR(4) | Key |
| 3 | LGPLA | Storage bin — unique within the warehouse, with storage type NOT part of the key | CHAR(18) | Key |
| 4 | LGTYP | Storage type the bin belongs to (an attribute here, not a key column) | CHAR(4) | |
| 5 | LGBER | Storage section the bin belongs to | CHAR(4) | |
| 6 | LPTYP | Storage bin type — the capacity profile the bin follows | CHAR(4) | |
| 7 | SKZUA | Block indicator for stock removals from the bin | CHAR(1) | |
| 8 | SKZUE | Block indicator for putaways into the bin | CHAR(1) | |
| 9 | SKZSI | Block indicator set by an ongoing physical inventory | CHAR(1) | |
| 10 | MAX_WEIGHT | Maximum weight the bin can hold | QUAN(15,3) | |
| 11 | UNIT_W | Unit of the weight figures | UNIT(3) | |
| 12 | MAX_VOLUME | Maximum volume the bin can hold | QUAN(15,3) | |
| 13 | UNIT_V | Unit of the volume figures | UNIT(3) | |
| 14 | FCAPA | Remaining available capacity in the bin, as used by the capacity check | DEC(15,3) | |
| 15 | KZLER | Flag: the bin is currently empty | CHAR(1) | |
| 16 | KZVOL | Flag: the bin is currently full | CHAR(1) | |
| 17 | AISLE | Aisle coordinate of the bin — layout data the pick path is built from | CHAR(18) | |
| 18 | MOVED_AT | Time of the last movement into the bin | DEC(15) | UTCFilter date |
Field provenance: hand-curated. 3 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /SCWM/LAGPon 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.
7 parameters not filled: <catalog>, <schema>, <client>, <LGNUM>, <LGPLA>, <TS_FROM>, <TS_TO>
-- ============================================================
-- Table : /SCWM/LAGP — The 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
-- Purpose: Column-selected read of /SCWM/LAGP — auto-generated from field metadata
-- Grain : One row per client + LGNUM + 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/LAGP; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_lagp — adjust to your landing convention (see quirks #namespace-slashes). 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.LGPLA AS "Storage bin — unique within the warehouse, with storage type NOT part of the key",
t.LGTYP AS "Storage type the bin belongs to (an attribute here, not a key column)",
t.LGBER AS "Storage section the bin belongs to",
t.LPTYP AS "Storage bin type — the capacity profile the bin follows",
t.SKZUA AS "Block indicator for stock removals from the bin",
t.SKZUE AS "Block indicator for putaways into the bin",
t.SKZSI AS "Block indicator set by an ongoing physical inventory",
t.MAX_WEIGHT AS "Maximum weight the bin can hold",
t.UNIT_W AS "Unit of the weight figures",
t.MAX_VOLUME AS "Maximum volume the bin can hold",
t.UNIT_V AS "Unit of the volume figures",
t.FCAPA AS "Remaining available capacity in the bin, as used by the capacity check",
t.KZLER AS "Flag: the bin is currently empty",
t.KZVOL AS "Flag: the bin is currently full",
t.AISLE AS "Aisle coordinate of the bin — layout data the pick path is built from",
t.MOVED_AT AS "Time of the last movement into the bin" -- UTC
FROM <catalog>.<schema>.scwm_lagp t
WHERE
t.MANDT = '<client>' -- client filter — drop on single-client systems
-- AND t.LGNUM = '<LGNUM>'
-- AND t.LGPLA = '<LGPLA>'
-- AND t.MOVED_AT >= <TS_FROM> -- UTC yyyymmddhhmmss — convert warehouse-local dates first (#utc-timestamps)
-- AND t.MOVED_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_tworkst.MANDT = scwm_lagp.MANDT AND scwm_tworkst.LGPLA = scwm_lagp.LGPLA AND scwm_tworkst.LGNUM = scwm_lagp.LGNUMON scwm_tdoor.MANDT = scwm_lagp.MANDT AND scwm_tdoor.DOOR_BIN = scwm_lagp.LGPLA AND scwm_tdoor.LGNUM = scwm_lagp.LGNUMON scwm_lagp.MANDT = scwm_t300.MANDT AND scwm_lagp.LGNUM = scwm_t300.LGNUMON scwm_lagp.MANDT = scwm_t301.MANDT AND scwm_lagp.LGTYP = scwm_t301.LGTYP AND scwm_lagp.LGNUM = scwm_t301.LGNUMON scwm_lagp.MANDT = scwm_t302.MANDT AND scwm_lagp.LGBER = scwm_t302.LGBER AND scwm_lagp.LGNUM = scwm_t302.LGNUM AND scwm_lagp.LGTYP = scwm_t302.LGTYPON scwm_lagp.MANDT = scwm_t303.MANDT AND scwm_lagp.LPTYP = scwm_t303.LPTYP AND scwm_lagp.LGNUM = scwm_t303.LGNUMON scwm_lagps.MANDT = scwm_lagp.MANDT AND scwm_lagps.LGPLA = scwm_lagp.LGPLA AND scwm_lagps.LGNUM = scwm_lagp.LGNUMON scwm_binmat.MANDT = scwm_lagp.MANDT AND scwm_binmat.LGPLA = scwm_lagp.LGPLA AND scwm_binmat.LGNUM = scwm_lagp.LGNUMON scwm_aqua.MANDT = scwm_lagp.MANDT AND scwm_aqua.LGPLA = scwm_lagp.LGPLA AND scwm_aqua.LGNUM = scwm_lagp.LGNUMON scwm_huhdr.MANDT = scwm_lagp.MANDT AND scwm_huhdr.WSBIN = scwm_lagp.LGPLA AND scwm_huhdr.LGNUM = scwm_lagp.LGNUMON scwm_ordim_o.MANDT = scwm_lagp.MANDT AND scwm_ordim_o.VLPLA = scwm_lagp.LGPLA AND scwm_ordim_o.LGNUM = scwm_lagp.LGNUMON scwm_ordim_o.MANDT = scwm_lagp.MANDT AND scwm_ordim_o.NLPLA = scwm_lagp.LGPLA AND scwm_ordim_o.LGNUM = scwm_lagp.LGNUMON scwm_ordim_c.MANDT = scwm_lagp.MANDT AND scwm_ordim_c.VLPLA = scwm_lagp.LGPLA AND scwm_ordim_c.LGNUM = scwm_lagp.LGNUMON scwm_ordim_c.MANDT = scwm_lagp.MANDT AND scwm_ordim_c.NLPLA = scwm_lagp.LGPLA AND scwm_ordim_c.LGNUM = scwm_lagp.LGNUMON scwm_ordim_l.MANDT = scwm_lagp.MANDT AND scwm_ordim_l.VLPLA = scwm_lagp.LGPLA AND scwm_ordim_l.LGNUM = scwm_lagp.LGNUMON scwm_ordim_l.MANDT = scwm_lagp.MANDT AND scwm_ordim_l.NLPLA = scwm_lagp.LGPLA AND scwm_ordim_l.LGNUM = scwm_lagp.LGNUMON lime_pi_par_biz.MANDT = scwm_lagp.MANDT AND lime_pi_par_biz.LGPLA = scwm_lagp.LGPLA AND lime_pi_par_biz.LGNUM = scwm_lagp.LGNUM -- bins are unique only within a warehouse — LGNUM belongs in the join even though this table does not key on itbins are unique only within a warehouse — LGNUM belongs in the join even though this table does not key on it
ON lime_pi_it_biz.MANDT = scwm_lagp.MANDT AND lime_pi_it_biz.LGPLA = scwm_lagp.LGPLA AND lime_pi_it_biz.LGNUM = scwm_lagp.LGNUMON scwm_tmfscp.MANDT = scwm_lagp.MANDT AND scwm_tmfscp.LGPLA = scwm_lagp.LGPLA AND scwm_tmfscp.LGNUM = scwm_lagp.LGNUM -- the bin behind a communication point — what makes a conveyor movement land in the task tables as an ordinary bin movementthe bin behind a communication point — what makes a conveyor movement land in the task tables as an ordinary bin movement
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/ADHUCreate an ad-hoc warehouse task for a handling unit — move a whole HU rather than a product quantityRead accessCreatestock-hu
- /SCWM/ADPRODCreate an ad-hoc warehouse task for a product — move stock without a delivery or a wave asking for itRead accessCreatestock-hu
- /SCWM/LS01Create a storage bin — one bin, or a generated range of them, in a storage typeWrite accessCreatestorage-bins
- /SCWM/LS03Display a storage bin — the bin's type, section, capacity, block indicators, and the stock currently sitting in itRead accessDisplaystorage-bins
- /SCWM/TODLV_ICreate warehouse tasks for an inbound delivery — the putaway work behind a receiptRead accessCreatewarehouse-tasks
More Storage Bins tables
- /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
- /SCWM/BINMATFixed bin assignment — the products that live in a named bin for a given entitled party, with the minimum, maximum, and replenishment quantities slotting maintains