/SCWM/T331
configSemantic keyStorage 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
Same key as /SCWM/T301 (warehouse plus storage type), and the table the storage-type control attributes actually live on — ST_ROLE, the HU requirement, the capacity check method, and the availability group are all here rather than on T301. The DDIC page shows 85 columns; this catalog curates the subset that carries analytical meaning (role, control, replenishment, mixing) and leaves the screen-control and rounding flags out.
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
28 fields · 3 key
28 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | LGNUM | EWM warehouse number | CHAR(4) | Key |
| 3 | LGTYP | Storage type whose behavior this row controls | CHAR(4) | Key |
| 4 | ST_ROLE | Storage type role — what the storage type is used for (standard storage, staging, work centre, and so on) | CHAR(1) | |
| 5 | HUOBL | Whether stock in this storage type must sit in a handling unit | CHAR(1) | |
| 6 | KAPAP | Capacity check method used when putting stock away here | CHAR(1) | |
| 7 | AVLGRP | Availability group — the stock-availability bucket the storage type reports into | CHAR(10) | |
| 8 | AVLGRP_MAND | Whether an availability group is mandatory for the storage type | CHAR(1) | |
| 9 | AVQLVL | Level at which available quantity is determined for the storage type | CHAR(1) | |
| 10 | REM_RULE | Stock removal rule applied when picking from the storage type | CHAR(4) | |
| 11 | PUT_RULE | Putaway rule applied when placing stock into the storage type | CHAR(1) | |
| 12 | QUEIN | Whether putaway tasks into this storage type require confirmation | CHAR(1) | |
| 13 | QUAUS | Whether stock removal tasks out of this storage type require confirmation | CHAR(1) | |
| 14 | NEGAT | Whether negative stock is permitted in the storage type | CHAR(1) | |
| 15 | FIXBIN | Whether the storage type works with fixed storage bins | CHAR(1) | |
| 16 | MAXFIXBIN | Maximum number of fixed bins a product may hold in the storage type | NUMC(3) | |
| 17 | REPL_LVL | Replenishment level the storage type is replenished at | CHAR(1) | |
| 18 | REPL_TOL | Tolerance applied to the replenishment quantity | NUMC(3) | |
| 19 | CHKSMAQ | Whether the maximum storage type quantity is checked | CHAR(1) | |
| 20 | MIXBIN | Whether mixed stock is allowed in a bin or handling unit of the storage type | CHAR(1) | |
| 21 | MIXHU | Whether mixed stock is allowed inside one handling unit | CHAR(1) | |
| 22 | MIXBBD | Whether quants with different expiration dates may be added to the same bin or handling unit | CHAR(1) | |
| 23 | BEHAV | Storage behavior of the storage type (standard, handling-unit managed, and so on) | CHAR(1) | |
| 24 | STGTYP_LVL | Level of the storage type, used where storage types are layered | NUMC(1) | |
| 25 | CAT_ROLE | Stock type role of the storage type | CHAR(1) | |
| 26 | PROCS | External storage process step the storage type takes part in | CHAR(4) | |
| 27 | AAREA_PLAN | Activity area used for planning in the storage type | CHAR(4) | |
| 28 | DISTANCE_DEF | Default travel distance assumed for the storage type | DEC(10,3) |
Field provenance: hand-curated. 3 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /SCWM/T331on 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.
5 parameters not filled: <catalog>, <schema>, <client>, <LGNUM>, <LGTYP>
-- ============================================================
-- Table : /SCWM/T331 — Storage 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
-- Purpose: Column-selected read of /SCWM/T331 — auto-generated from field metadata
-- Grain : One row per client + LGNUM + LGTYP
-- Notes : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/T331; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_t331 — 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 whose behavior this row controls",
t.ST_ROLE AS "Storage type role — what the storage type is used for (standard storage, staging, work centre, and so on)",
t.HUOBL AS "Whether stock in this storage type must sit in a handling unit",
t.KAPAP AS "Capacity check method used when putting stock away here",
t.AVLGRP AS "Availability group — the stock-availability bucket the storage type reports into",
t.AVLGRP_MAND AS "Whether an availability group is mandatory for the storage type",
t.AVQLVL AS "Level at which available quantity is determined for the storage type",
t.REM_RULE AS "Stock removal rule applied when picking from the storage type",
t.PUT_RULE AS "Putaway rule applied when placing stock into the storage type",
t.QUEIN AS "Whether putaway tasks into this storage type require confirmation",
t.QUAUS AS "Whether stock removal tasks out of this storage type require confirmation",
t.NEGAT AS "Whether negative stock is permitted in the storage type",
t.FIXBIN AS "Whether the storage type works with fixed storage bins",
t.MAXFIXBIN AS "Maximum number of fixed bins a product may hold in the storage type",
t.REPL_LVL AS "Replenishment level the storage type is replenished at",
t.REPL_TOL AS "Tolerance applied to the replenishment quantity",
t.CHKSMAQ AS "Whether the maximum storage type quantity is checked",
t.MIXBIN AS "Whether mixed stock is allowed in a bin or handling unit of the storage type",
t.MIXHU AS "Whether mixed stock is allowed inside one handling unit",
t.MIXBBD AS "Whether quants with different expiration dates may be added to the same bin or handling unit",
t.BEHAV AS "Storage behavior of the storage type (standard, handling-unit managed, and so on)",
t.STGTYP_LVL AS "Level of the storage type, used where storage types are layered",
t.CAT_ROLE AS "Stock type role of the storage type",
t.PROCS AS "External storage process step the storage type takes part in",
t.AAREA_PLAN AS "Activity area used for planning in the storage type",
t.DISTANCE_DEF AS "Default travel distance assumed for the storage type"
FROM <catalog>.<schema>.scwm_t331 t
WHERE
t.MANDT = '<client>' -- client filter — drop on single-client systems
-- AND t.LGNUM = '<LGNUM>'
-- AND t.LGTYP = '<LGTYP>'
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_t331.MANDT = scwm_t301.MANDT AND scwm_t331.LGTYP = scwm_t301.LGTYP AND scwm_t331.LGNUM = scwm_t301.LGNUM
More Warehouse Structure tables
- /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
- /SCWM/T300TWarehouse number descriptions — one row per warehouse per language; the readable name behind LGNUM