EWM Reference
/SCWM/T302
configSemantic keyStorage sections — the subdivision of a storage type used to group bins for putaway strategy
Identity
Module: Warehouse StructureBronze: scwm_t302
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
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
5 fields · 4 key
5 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | LGNUM | EWM warehouse number | CHAR(4) | Key |
| 3 | LGTYP | Storage type the section belongs to | CHAR(4) | Key |
| 4 | LGBER | Storage section | CHAR(4) | Key |
| 5 | AAREA_PLAN | Activity area used for planning purposes for this section | CHAR(4) |
Field provenance: hand-curated. 4 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /SCWM/T302on 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>, <LGTYP>, <LGBER>
-- ============================================================
-- Table : /SCWM/T302 — Storage sections — the subdivision of a storage type used to group bins for putaway strategy
-- Purpose: Column-selected read of /SCWM/T302 — auto-generated from field metadata
-- Grain : One row per client + LGNUM + LGTYP + LGBER
-- Notes : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/T302; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_t302 — 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.LGTYP AS "Storage type the section belongs to",
t.LGBER AS "Storage section",
t.AAREA_PLAN AS "Activity area used for planning purposes for this section"
FROM <catalog>.<schema>.scwm_t302 t
WHERE
t.MANDT = '<client>' -- client filter — drop on single-client systems
-- AND t.LGNUM = '<LGNUM>'
-- AND t.LGTYP = '<LGTYP>'
-- AND t.LGBER = '<LGBER>'
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_t302.MANDT = scwm_t301.MANDT AND scwm_t302.LGTYP = scwm_t301.LGTYP AND scwm_t302.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.LGTYP
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 Warehouse Structure tables
- /SCWM/T331Storage type control — the behavior of a storage type: its role, whether handling units are mandatory, the capacity check method and availability group, the putaway and stock-removal rules, replenishment level and tolerance, and the mixing rules that decide what may share a bin
- /SCWM/TAAREAActivity area definition — the execution-oriented grouping of bins that warehouse-order creation and pick-path sorting work against
- /SCWM/TDOORDoors — the loading and unloading points of the warehouse, each mapped to a bin, a default staging area, and (where a yard exists) the matching yard bin
- /SCWM/TWORKSTWork centers — the packing, deconsolidation, value-added-service, and counting stations in the warehouse, each modeled as a storage type and bin
- /SCWM/T300The warehouse number definition — one row per EWM warehouse, the four-character key every structure, bin, stock, and task row is striped by
- /SCWM/T300_MDWarehouse-to-party assignment — the supply chain unit the warehouse maps to plus the default entitled-to-dispose and ship-to parties