/SCWM/LAGPS
configSemantic keyBin assignments to activity areas — one row per bin per activity, carrying the sort sequence that determines the order an operator walks the bins
One bin appears once per ACT_TYPE — filter to the activity you mean (picking, putaway, counting) before joining to bins or bin counts multiply
The key is bin + activity; the activity area itself is an attribute of the assignment row, not part of the key. SRT_NR and the aisle distance columns are the raw material for pick-path and travel-distance analysis.
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 · 4 key
15 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | LGNUM | EWM warehouse number | CHAR(4) | Key |
| 3 | LGPLA | Storage bin the sort entry applies to | CHAR(18) | Key |
| 4 | ACT_TYPE | Activity the sort entry applies to (picking, putaway, counting) | CHAR(4) | Key |
| 5 | RANK | Rank of the bin within the activity-area sequence | NUMC(5) | |
| 6 | AAREA | Activity area the bin is assigned to — an attribute of the assignment, not part of the key | CHAR(4) | |
| 7 | LGTYP | Storage type of the bin, carried denormalized | CHAR(4) | |
| 8 | LGBER | Storage section of the bin, carried denormalized | CHAR(4) | |
| 9 | AISLE | Aisle of the bin, carried denormalized | CHAR(18) | |
| 10 | SRT_NR | Bin sort sequence for the activity — the column that drives pick-path order | DEC(10) | |
| 11 | AISLE_S_DISTANCE | Distance from the bin to the start of its aisle | QUAN(10) | |
| 12 | AISLE_LENGTH | Length of the aisle | QUAN(10) | |
| 13 | AISLE_NEXT | Subsequent aisle in the path | CHAR(18) | |
| 14 | AISLE_N_DISTANCE | Distance to the subsequent aisle | QUAN(10) | |
| 15 | DSTGRP | Consolidation group used at this bin | CHAR(10) |
Field provenance: hand-curated. 4 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /SCWM/LAGPSon 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>, <LGNUM>, <LGPLA>, <ACT_TYPE>
-- ============================================================
-- Table : /SCWM/LAGPS — Bin assignments to activity areas — one row per bin per activity, carrying the sort sequence that determines the order an operator walks the bins
-- Purpose: Column-selected read of /SCWM/LAGPS — auto-generated from field metadata
-- Grain : One row per client + LGNUM + LGPLA + ACT_TYPE
-- Caution: One bin appears once per ACT_TYPE — filter to the activity you mean (picking, putaway, counting) before joining to bins or bin counts multiply
-- Notes : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/LAGPS; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_lagps — 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 the sort entry applies to",
t.ACT_TYPE AS "Activity the sort entry applies to (picking, putaway, counting)",
t.RANK AS "Rank of the bin within the activity-area sequence",
t.AAREA AS "Activity area the bin is assigned to — an attribute of the assignment, not part of the key",
t.LGTYP AS "Storage type of the bin, carried denormalized",
t.LGBER AS "Storage section of the bin, carried denormalized",
t.AISLE AS "Aisle of the bin, carried denormalized",
t.SRT_NR AS "Bin sort sequence for the activity — the column that drives pick-path order",
t.AISLE_S_DISTANCE AS "Distance from the bin to the start of its aisle",
t.AISLE_LENGTH AS "Length of the aisle",
t.AISLE_NEXT AS "Subsequent aisle in the path",
t.AISLE_N_DISTANCE AS "Distance to the subsequent aisle",
t.DSTGRP AS "Consolidation group used at this bin"
FROM <catalog>.<schema>.scwm_lagps t
WHERE
t.MANDT = '<client>' -- client filter — drop on single-client systems
-- AND t.LGNUM = '<LGNUM>'
-- AND t.LGPLA = '<LGPLA>'
-- AND t.ACT_TYPE = '<ACT_TYPE>'
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_lagps.MANDT = scwm_lagp.MANDT AND scwm_lagps.LGPLA = scwm_lagp.LGPLA AND scwm_lagps.LGNUM = scwm_lagp.LGNUMON scwm_lagps.MANDT = scwm_taarea.MANDT AND scwm_lagps.AAREA = scwm_taarea.AAREA AND scwm_lagps.LGNUM = scwm_taarea.LGNUM
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/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
- /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