Skip to content
EWM Reference

/SCWM/LAGPS

configSemantic key

Bin assignments to activity areas — one row per bin per activity, carrying the sort sequence that determines the order an operator walks the bins

Grain note

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

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.

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 · 4 key

15 fields.

Table fields: position, field name, description, data type, and flags. 15 fields.
#FieldDescriptionTypeFlags
1MANDTClientCLNT(3)
Key
2LGNUMEWM warehouse numberCHAR(4)
Key
3LGPLAStorage bin the sort entry applies toCHAR(18)
Key
4ACT_TYPEActivity the sort entry applies to (picking, putaway, counting)CHAR(4)
Key
5RANKRank of the bin within the activity-area sequenceNUMC(5)
6AAREAActivity area the bin is assigned to — an attribute of the assignment, not part of the keyCHAR(4)
7LGTYPStorage type of the bin, carried denormalizedCHAR(4)
8LGBERStorage section of the bin, carried denormalizedCHAR(4)
9AISLEAisle of the bin, carried denormalizedCHAR(18)
10SRT_NRBin sort sequence for the activity — the column that drives pick-path orderDEC(10)
11AISLE_S_DISTANCEDistance from the bin to the start of its aisleQUAN(10)
12AISLE_LENGTHLength of the aisleQUAN(10)
13AISLE_NEXTSubsequent aisle in the pathCHAR(18)
14AISLE_N_DISTANCEDistance to the subsequent aisleQUAN(10)
15DSTGRPConsolidation group used at this binCHAR(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.

Query parameters

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

  • /SCWM/LAGPS/SCWM/LAGPforeign key · N:1
    ON scwm_lagps.MANDT = scwm_lagp.MANDT AND scwm_lagps.LGPLA = scwm_lagp.LGPLA AND scwm_lagps.LGNUM = scwm_lagp.LGNUM
  • /SCWM/LAGPS/SCWM/TAAREAforeign key · N:1
    ON 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

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.