Skip to content
EWM Reference

/SCWM/TDOOR

configMixed key

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

Identity
Module: Warehouse StructureBronze: scwm_tdoor
Notes

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.

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

16 fields · 3 key

16 fields.

Table fields: position, field name, description, data type, and flags. 16 fields.
#FieldDescriptionTypeFlags
1MANDTClientCLNT(3)
Key
2LGNUMEWM warehouse numberCHAR(4)
Key
3DOORWarehouse doorCHAR(4)
Key
4DOOR_BINStorage bin representing the door — the join to the bin masterCHAR(18)
5LOAD_DIRLoading direction of the door (inbound or outbound use)CHAR(1)
6STAREA_GR_DEFDefault staging area group served by the doorCHAR(4)
7STAREA_DEFDefault staging area served by the doorCHAR(4)
8MTR_DEFDefault means of transport at the doorCHAR(10)
9SC_UNITSupply chain unit representing the door, in its readable formCHAR(20)
10SCUGUIDSupply chain unit GUID for the doorRAW(16)
11ROUTE_PROPRoute proposed for shipments over this doorCHAR(10)
12YARD_LGNUMWarehouse number of the attached yardCHAR(4)
13YARD_DOOR_BINYard bin that mirrors the door on the yard sideCHAR(18)
14YARD_LGTYPYard storage type of that binCHAR(4)
15YARD_LGBERYard storage section of that binCHAR(4)
16NR_RANGENumber range used for documents created at the doorCHAR(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.

Query parameters

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

  • /SCWM/TDOOR/SCWM/LAGPforeign key · N:1
    ON scwm_tdoor.MANDT = scwm_lagp.MANDT AND scwm_tdoor.DOOR_BIN = scwm_lagp.LGPLA AND scwm_tdoor.LGNUM = scwm_lagp.LGNUM
  • /SCWM/TDOOR/SCMB/TOENTITYGUID join · N:1
    ON scwm_tdoor.MANDT = scmb_toentity.MANDT AND scwm_tdoor.SCUGUID = scmb_toentity.SCUGUID -- RAW16 GUID equality — join raw; hex is for display/conformance only
  • /SCWM/DOOR_SRACT/SCWM/TDOORforeign key · N:1
    ON 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

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.