/SCWM/T301M
configSemantic keyStorage type group assignment — which storage types belong to a group and in what sequence they are searched
SEQNO is the search order within the group, not a cosmetic sort: it decides which storage type a strategy tries first. One storage type can appear in more than one group, so joining bins to groups through this table can multiply rows.
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
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 | LGTYPGRP | Storage type group the assignment belongs to | CHAR(4) | Key |
| 4 | SEQNO | Sequence number — the order in which the group's storage types are searched | NUMC(5) | Key |
| 5 | LGTYP | Storage type assigned to the group at this position | CHAR(4) |
Field provenance: hand-curated. 4 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /SCWM/T301Mon 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.
4 parameters not filled: <catalog>, <schema>, <client>, <LGNUM>
-- ============================================================
-- Table : /SCWM/T301M — Storage type group assignment — which storage types belong to a group and in what sequence they are searched
-- Purpose: Column-selected read of /SCWM/T301M — auto-generated from field metadata
-- Grain : One row per client + LGNUM + LGTYPGRP + SEQNO
-- Notes : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/T301M; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_t301m — 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.LGTYPGRP AS "Storage type group the assignment belongs to",
t.SEQNO AS "Sequence number — the order in which the group's storage types are searched",
t.LGTYP AS "Storage type assigned to the group at this position"
FROM <catalog>.<schema>.scwm_t301m t
WHERE
t.MANDT = '<client>' -- client filter — drop on single-client systems
-- AND t.LGNUM = '<LGNUM>'
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_t301m.MANDT = scwm_t301g.MANDT AND scwm_t301m.LGTYPGRP = scwm_t301g.LGTYPGRP AND scwm_t301m.LGNUM = scwm_t301g.LGNUMON scwm_t301m.MANDT = scwm_t301.MANDT AND scwm_t301m.LGTYP = scwm_t301.LGTYP AND scwm_t301m.LGNUM = scwm_t301.LGNUM
More Warehouse Structure tables
- /SCWM/T301TStorage type descriptions — one row per storage type per language
- /SCWM/T302Storage sections — the subdivision of a storage type used to group bins for putaway strategy
- /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