Skip to content
EWM Reference

/SCWM/T331

configSemantic key

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

Identity
Notes

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.

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

28 fields · 3 key

28 fields.

Table fields: position, field name, description, data type, and flags. 28 fields.
#FieldDescriptionTypeFlags
1MANDTClientCLNT(3)
Key
2LGNUMEWM warehouse numberCHAR(4)
Key
3LGTYPStorage type whose behavior this row controlsCHAR(4)
Key
4ST_ROLEStorage type role — what the storage type is used for (standard storage, staging, work centre, and so on)CHAR(1)
5HUOBLWhether stock in this storage type must sit in a handling unitCHAR(1)
6KAPAPCapacity check method used when putting stock away hereCHAR(1)
7AVLGRPAvailability group — the stock-availability bucket the storage type reports intoCHAR(10)
8AVLGRP_MANDWhether an availability group is mandatory for the storage typeCHAR(1)
9AVQLVLLevel at which available quantity is determined for the storage typeCHAR(1)
10REM_RULEStock removal rule applied when picking from the storage typeCHAR(4)
11PUT_RULEPutaway rule applied when placing stock into the storage typeCHAR(1)
12QUEINWhether putaway tasks into this storage type require confirmationCHAR(1)
13QUAUSWhether stock removal tasks out of this storage type require confirmationCHAR(1)
14NEGATWhether negative stock is permitted in the storage typeCHAR(1)
15FIXBINWhether the storage type works with fixed storage binsCHAR(1)
16MAXFIXBINMaximum number of fixed bins a product may hold in the storage typeNUMC(3)
17REPL_LVLReplenishment level the storage type is replenished atCHAR(1)
18REPL_TOLTolerance applied to the replenishment quantityNUMC(3)
19CHKSMAQWhether the maximum storage type quantity is checkedCHAR(1)
20MIXBINWhether mixed stock is allowed in a bin or handling unit of the storage typeCHAR(1)
21MIXHUWhether mixed stock is allowed inside one handling unitCHAR(1)
22MIXBBDWhether quants with different expiration dates may be added to the same bin or handling unitCHAR(1)
23BEHAVStorage behavior of the storage type (standard, handling-unit managed, and so on)CHAR(1)
24STGTYP_LVLLevel of the storage type, used where storage types are layeredNUMC(1)
25CAT_ROLEStock type role of the storage typeCHAR(1)
26PROCSExternal storage process step the storage type takes part inCHAR(4)
27AAREA_PLANActivity area used for planning in the storage typeCHAR(4)
28DISTANCE_DEFDefault travel distance assumed for the storage typeDEC(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.

Query parameters

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

  • /SCWM/T331/SCWM/T301foreign key · 1:1
    ON scwm_t331.MANDT = scwm_t301.MANDT AND scwm_t331.LGTYP = scwm_t301.LGTYP AND scwm_t331.LGNUM = scwm_t301.LGNUM

Browse more Warehouse Structure tables

More Warehouse Structure 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.