Skip to content
EWM Reference

/SCWM/DOOR_SRACT

transactionMixed key

Door activities — the shipping-and-receiving activities assigned to a warehouse door, with the planned and actual occupancy window

Identity
Module: Yard & Material FlowBronze: scwm_door_sract
Grain note

Door occupancy, not dock throughput — a row says the door was reserved for an activity between two stamps, and overlapping planned windows are the door-scheduling problem this table exposes

Notes

The one activity table keyed by warehouse number, because doors are only unique within a warehouse; the transportation-unit and vehicle activity tables key on their own object number instead. The door itself is configuration and resolves against the door table in the warehouse-structure module. ACT_ID shares its data element with the transportation-unit activity's, which is what lets a door occupancy be tied to the trailer standing at it.

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 · 4 key

16 fields.

Table fields: position, field name, description, data type, and flags. 16 fields.
#FieldDescriptionTypeFlags
1MANDTClientCLNT(3)
Key
2LGNUMEWM warehouse number — doors are unique only within itCHAR(4)
Key
3DOORWarehouse door the activity is assigned toCHAR(4)
Key
4DOOR_SR_ACT_NUMActivity number at that door — one occupancy of the doorNUMC(10)
Key
5ACT_IDGUID of the shipping-and-receiving activity — the same identifier the transportation unit's activity row carries, which is how a door occupancy is tied to the trailer standing at itRAW(16)
6ACT_TYPEActivity typeCHAR(1)
7ACT_CATActivity categoryCHAR(1)
8ACT_DIRDirection of the activity — inbound against outboundCHAR(1)
9START_PLAN_TSTFREarliest planned start of the door occupancyDEC(15)
10START_PLAN_TSTTOLatest planned start of the door occupancyDEC(15)
11START_ACTUALActual start of the door occupancyDEC(15)
UTCFilter date
12START_TZONETime zone the start times are read in locally — the stored values are UTCCHAR(6)
13END_PLAN_TSTFREarliest planned end of the door occupancyDEC(15)
14END_PLAN_TSTTOLatest planned end of the door occupancy — the pair of planned windows is what a door-scheduling conflict is measured againstDEC(15)
15END_ACTUALActual end of the door occupancyDEC(15)
16END_TZONETime zone the end times are read in locallyCHAR(6)

Field provenance: hand-curated. 4 key fields.

Boilerplate SQL

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

7 parameters not filled: <catalog>, <schema>, <client>, <LGNUM>, <DOOR>, <TS_FROM>, <TS_TO>

-- ============================================================
-- Table  : /SCWM/DOOR_SRACT — Door activities — the shipping-and-receiving activities assigned to a warehouse door, with the planned and actual occupancy window
-- Purpose: Column-selected read of /SCWM/DOOR_SRACT — auto-generated from field metadata
-- Grain  : One row per client + LGNUM + DOOR + DOOR_SR_ACT_NUM
-- Caution: Door occupancy, not dock throughput — a row says the door was reserved for an activity between two stamps, and overlapping planned windows are the door-scheduling problem this table exposes
-- Notes  : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/DOOR_SRACT; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_door_sract — 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 — doors are unique only within it",
  t.DOOR AS "Warehouse door the activity is assigned to",
  t.DOOR_SR_ACT_NUM AS "Activity number at that door — one occupancy of the door",
  t.ACT_ID AS "GUID of the shipping-and-receiving activity — the same identifier the transportation unit's activity row carries, which is how a door occupancy is tied to the trailer standing at it",
  lower(hex(t.ACT_ID)) AS "GUID of the shipping-and-receiving activity — the same identifier the transportation unit's activity row carries, which is how a door occupancy is tied to the trailer standing at it (hex)",  -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
  t.ACT_TYPE AS "Activity type",
  t.ACT_CAT AS "Activity category",
  t.ACT_DIR AS "Direction of the activity — inbound against outbound",
  t.START_PLAN_TSTFR AS "Earliest planned start of the door occupancy",  -- UTC
  t.START_PLAN_TSTTO AS "Latest planned start of the door occupancy",  -- UTC
  t.START_ACTUAL AS "Actual start of the door occupancy",  -- UTC
  t.START_TZONE AS "Time zone the start times are read in locally — the stored values are UTC",
  t.END_PLAN_TSTFR AS "Earliest planned end of the door occupancy",  -- UTC
  t.END_PLAN_TSTTO AS "Latest planned end of the door occupancy — the pair of planned windows is what a door-scheduling conflict is measured against",  -- UTC
  t.END_ACTUAL AS "Actual end of the door occupancy",  -- UTC
  t.END_TZONE AS "Time zone the end times are read in locally"
FROM <catalog>.<schema>.scwm_door_sract t
WHERE
  t.MANDT = '<client>'  -- client filter — drop on single-client systems
  -- AND t.LGNUM = '<LGNUM>'
  -- AND t.DOOR = '<DOOR>'
  -- AND t.START_ACTUAL >= <TS_FROM>  -- UTC yyyymmddhhmmss — convert warehouse-local dates first (#utc-timestamps)
  -- AND t.START_ACTUAL <= <TS_TO>
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/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
  • /SCWM/DOOR_SRACT/SCWM/TU_SR_ACTGUID join · N:1
    ON scwm_door_sract.MANDT = scwm_tu_sr_act.MANDT AND scwm_door_sract.ACT_ID = scwm_tu_sr_act.ACT_ID -- RAW16 GUID equality — join raw; hex is for display/conformance only · both pages type this column on the same shipping-and-receiving activity identifier, which is what ties a door occupancy to the trailer standing at it; one activity can occupy more than one door over a visit, so this is not a 1:1

    both pages type this column on the same shipping-and-receiving activity identifier, which is what ties a door occupancy to the trailer standing at it; one activity can occupy more than one door over a visit, so this is not a 1:1

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 Yard & Material Flow tables

More Yard & Material Flow 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.