/SCWM/TDOOR
configMixed keyDoors — 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
Ships in R1 as the structural anchor for the yard module that lands in R3: the yard-side columns here (YARD_LGNUM, YARD_DOOR_BIN, YARD_LGTYP, YARD_LGBER) are the join into the yard warehouse. A second supply-chain-unit GUID for the loading point exists on the DDIC page and was not curated.
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
16 fields · 3 key
16 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | LGNUM | EWM warehouse number | CHAR(4) | Key |
| 3 | DOOR | Warehouse door | CHAR(4) | Key |
| 4 | DOOR_BIN | Storage bin representing the door — the join to the bin master | CHAR(18) | |
| 5 | LOAD_DIR | Loading direction of the door (inbound or outbound use) | CHAR(1) | |
| 6 | STAREA_GR_DEF | Default staging area group served by the door | CHAR(4) | |
| 7 | STAREA_DEF | Default staging area served by the door | CHAR(4) | |
| 8 | MTR_DEF | Default means of transport at the door | CHAR(10) | |
| 9 | SC_UNIT | Supply chain unit representing the door, in its readable form | CHAR(20) | |
| 10 | SCUGUID | Supply chain unit GUID for the door | RAW(16) | |
| 11 | ROUTE_PROP | Route proposed for shipments over this door | CHAR(10) | |
| 12 | YARD_LGNUM | Warehouse number of the attached yard | CHAR(4) | |
| 13 | YARD_DOOR_BIN | Yard bin that mirrors the door on the yard side | CHAR(18) | |
| 14 | YARD_LGTYP | Yard storage type of that bin | CHAR(4) | |
| 15 | YARD_LGBER | Yard storage section of that bin | CHAR(4) | |
| 16 | NR_RANGE | Number range used for documents created at the door | CHAR(2) |
Field provenance: hand-curated. 3 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /SCWM/TDOORon 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>, <DOOR>
-- ============================================================
-- Table : /SCWM/TDOOR — Doors — 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
-- Purpose: Column-selected read of /SCWM/TDOOR — auto-generated from field metadata
-- Grain : One row per client + LGNUM + DOOR
-- Notes : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/TDOOR; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_tdoor — adjust to your landing convention (see quirks #namespace-slashes). RAW16 GUID columns are joined raw; the hex aliases are for display only (#guid-keys). 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.DOOR AS "Warehouse door",
t.DOOR_BIN AS "Storage bin representing the door — the join to the bin master",
t.LOAD_DIR AS "Loading direction of the door (inbound or outbound use)",
t.STAREA_GR_DEF AS "Default staging area group served by the door",
t.STAREA_DEF AS "Default staging area served by the door",
t.MTR_DEF AS "Default means of transport at the door",
t.SC_UNIT AS "Supply chain unit representing the door, in its readable form",
t.SCUGUID AS "Supply chain unit GUID for the door",
lower(hex(t.SCUGUID)) AS "Supply chain unit GUID for the door (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.ROUTE_PROP AS "Route proposed for shipments over this door",
t.YARD_LGNUM AS "Warehouse number of the attached yard",
t.YARD_DOOR_BIN AS "Yard bin that mirrors the door on the yard side",
t.YARD_LGTYP AS "Yard storage type of that bin",
t.YARD_LGBER AS "Yard storage section of that bin",
t.NR_RANGE AS "Number range used for documents created at the door"
FROM <catalog>.<schema>.scwm_tdoor t
WHERE
t.MANDT = '<client>' -- client filter — drop on single-client systems
-- AND t.LGNUM = '<LGNUM>'
-- AND t.DOOR = '<DOOR>'
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_tdoor.MANDT = scwm_lagp.MANDT AND scwm_tdoor.DOOR_BIN = scwm_lagp.LGPLA AND scwm_tdoor.LGNUM = scwm_lagp.LGNUMON scwm_tdoor.MANDT = scmb_toentity.MANDT AND scwm_tdoor.SCUGUID = scmb_toentity.SCUGUID -- RAW16 GUID equality — join raw; hex is for display/conformance onlyON scwm_door_sract.MANDT = scwm_tdoor.MANDT AND scwm_door_sract.DOOR = scwm_tdoor.DOOR AND scwm_door_sract.LGNUM = scwm_tdoor.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
More Warehouse Structure tables
- /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
- /SCWM/T301Storage type definition — one row per storage type in a warehouse; the first level of structure below the warehouse number
- /SCWM/T301GStorage type groups — the grouping of storage types that share one stock-removal rule, putaway rule, and maximum-quantity check