EWM Reference

/SCWM/T303

configSemantic key

Storage bin types — the weight, volume, capacity, and packing-dimension limits a bin of each type accepts

Identity

Notes

Bin types are the configuration side of the capacity check: LAGP carries the per-bin limits, T303 the type-level defaults and the maximum bin depth in handling units.

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 — LGNUM plus 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 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.

Fields

13 fields · 3 key

13 fields.

Table fields: position, field name, description, data type, and flags. 13 fields.
#	Field	Description	Type	Flags
1	MANDT	Client	CLNT(3)	Key
2	LGNUM	EWM warehouse number	CHAR(4)	Key
3	LPTYP	Storage bin type	CHAR(4)	Key
4	MAX_WEIGHT	Maximum weight a bin of this type can hold	QUAN(15,3)
5	UNIT_W	Weight unit	UNIT(3)
6	MAX_VOLUME	Maximum volume a bin of this type can hold	QUAN(15,3)
7	UNIT_V	Volume unit	UNIT(3)
8	MAX_CAPA	Maximum capacity figure used for packaging-material capacity checks	DEC(15,3)
9	MAX_LENGTH	Maximum packing length the bin type accepts	QUAN(15,3)
10	MAX_WIDTH	Maximum packing width the bin type accepts	QUAN(15,3)
11	MAX_HEIGHT	Maximum packing height the bin type accepts	QUAN(15,3)
12	UNIT_LWH	Dimension unit for length, width, and height	UNIT(3)
13	MAX_BIN_DEPTH	Maximum bin depth, in handling units	NUMC(2)

Field provenance: hand-curated. 3 key fields.

Boilerplate SQL

Starting point for reading the replicated copy of /SCWM/T303on 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

CatalogSchemaClient (MANDT)Warehouse number (LGNUM)Storage bin type

Include optional filters (2)

5 parameters not filled: <catalog>, <schema>, <client>, <LGNUM>, <LPTYP>

-- ============================================================
-- Table  : /SCWM/T303 — Storage bin types — the weight, volume, capacity, and packing-dimension limits a bin of each type accepts
-- Purpose: Column-selected read of /SCWM/T303 — auto-generated from field metadata
-- Grain  : One row per client + LGNUM + LPTYP
-- Notes  : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/T303; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_t303 — 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.LPTYP AS "Storage bin type",
  t.MAX_WEIGHT AS "Maximum weight a bin of this type can hold",
  t.UNIT_W AS "Weight unit",
  t.MAX_VOLUME AS "Maximum volume a bin of this type can hold",
  t.UNIT_V AS "Volume unit",
  t.MAX_CAPA AS "Maximum capacity figure used for packaging-material capacity checks",
  t.MAX_LENGTH AS "Maximum packing length the bin type accepts",
  t.MAX_WIDTH AS "Maximum packing width the bin type accepts",
  t.MAX_HEIGHT AS "Maximum packing height the bin type accepts",
  t.UNIT_LWH AS "Dimension unit for length, width, and height",
  t.MAX_BIN_DEPTH AS "Maximum bin depth, in handling units"
FROM <catalog>.<schema>.scwm_t303 t
WHERE
  t.MANDT = '<client>'  -- client filter — drop on single-client systems
  -- AND t.LGNUM = '<LGNUM>'
  -- AND t.LPTYP = '<LPTYP>'
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/LAGP/SCWM/T303foreign key · N:1
ON scwm_lagp.MANDT = scwm_t303.MANDT AND scwm_lagp.LPTYP = scwm_t303.LPTYP AND scwm_lagp.LGNUM = scwm_t303.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