EWM Reference

/SCWM/T300

configSemantic key

The warehouse number definition — one row per EWM warehouse, the four-character key every structure, bin, stock, and task row is striped by

Identity

Module: Warehouse StructureBronze: scwm_t300Texts: /SCWM/T300T

Classic WM

In the SAP reference: T300 WM → EWM crosswalk

Notes

Deliberately thin at the DDIC level: the warehouse's behavioral configuration lives in separate control tables, not here. LGNUM is four characters in EWM against classic WM's three — a fixed-width parsing trap when both systems land in one lakehouse.

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.

Text companion

/SCWM/T300 keeps its readable descriptions in /SCWM/T300T — one row per language. Filter to one SPRAS or rows multiply.

Fields

3 fields · 2 key

3 fields.

Table fields: position, field name, description, data type, and flags. 3 fields.
#	Field	Description	Type	Flags
1	MANDT	Client	CLNT(3)	Key
2	LGNUM	EWM warehouse number — four characters, one more than classic WM's three	CHAR(4)	Key
3	CTRL_CIF	Control flag for CIF master-data transfer, the legacy SCM-stack mechanism; S/4HANA-based decentralized EWM receives master data over ALE and the Data Replication Framework instead	CHAR(1)

Field provenance: hand-curated. 2 key fields.

Boilerplate SQL

Starting point for reading the replicated copy of /SCWM/T300on 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)Language key (SPRAS)Warehouse number (LGNUM)

Include optional filters (1)

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

-- ============================================================
-- Table  : /SCWM/T300 — The warehouse number definition — one row per EWM warehouse, the four-character key every structure, bin, stock, and task row is striped by
-- Purpose: Column-selected read of /SCWM/T300 — auto-generated from field metadata
-- Grain  : One row per client + LGNUM
-- Notes  : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/T300; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_t300 — 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 — four characters, one more than classic WM's three",
  t.CTRL_CIF AS "Control flag for CIF master-data transfer, the legacy SCM-stack mechanism; S/4HANA-based decentralized EWM receives master data over ALE and the Data Replication Framework instead",
  tx.LNUMT AS "Warehouse number description in the row's language"
FROM <catalog>.<schema>.scwm_t300 t
LEFT JOIN <catalog>.<schema>.scwm_t300t tx
  ON tx.MANDT = t.MANDT
 AND tx.LGNUM = t.LGNUM
 AND tx.SPRAS = '<language>'  -- one language or rows multiply
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

/SCWM/T300/SCWM/T300Ttext table · 1:N
ON scwm_t300.MANDT = scwm_t300t.MANDT AND scwm_t300.LGNUM = scwm_t300t.LGNUM AND scwm_t300t.SPRAS = '<language>'
/SCWM/T301/SCWM/T300foreign key · N:1
ON scwm_t301.MANDT = scwm_t300.MANDT AND scwm_t301.LGNUM = scwm_t300.LGNUM
/SCWM/TAAREA/SCWM/T300foreign key · N:1
ON scwm_taarea.MANDT = scwm_t300.MANDT AND scwm_taarea.LGNUM = scwm_t300.LGNUM
/SCWM/T300_MD/SCWM/T300foreign key · 1:1
ON scwm_t300_md.MANDT = scwm_t300.MANDT AND scwm_t300_md.LGNUM = scwm_t300.LGNUM
/SCWM/LAGP/SCWM/T300foreign key · N:1
ON scwm_lagp.MANDT = scwm_t300.MANDT AND scwm_lagp.LGNUM = scwm_t300.LGNUM

Browse more Warehouse Structure tables