/SCWM/VEH_SR_ACT
transactionMixed keyVehicle activities — the same shipping-and-receiving activity shape for a vehicle: planned and actual times, activity type and direction, the driver, the carrier, and the weighed weight
One row per vehicle visit, not per vehicle — and the vehicle's activity is a different row from the transportation unit's, so a yard dwell measure must decide which object it is measuring
The driver is recorded here rather than on the vehicle master, because it changes per visit. The activity GUID shares its data element with the transportation-unit and door activity tables, which is how one arrival can be seen from the vehicle, the trailer, and the door it was assigned to.
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
20 fields · 3 key
20 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | VEH_NUM | Internal vehicle number the activity belongs to | CHAR(20) | Key |
| 3 | VEH_SR_ACT_NUM | Shipping-and-receiving activity number — one visit of this vehicle | NUMC(10) | Key |
| 4 | ACT_ID | GUID of the shipping-and-receiving activity | RAW(16) | |
| 5 | ACT_TYPE | Activity type | CHAR(1) | |
| 6 | ACT_CAT | Activity category | CHAR(1) | |
| 7 | ACT_DIR | Direction of the activity — inbound against outbound | CHAR(1) | |
| 8 | START_PLAN_TSTFR | Earliest planned start of the visit | DEC(15) | |
| 9 | START_PLAN_TSTTO | Latest planned start of the visit | DEC(15) | |
| 10 | START_ACTUAL | Actual start of the visit | DEC(15) | UTCFilter date |
| 11 | START_TZONE | Time zone the start times are read in locally — the stored values are UTC | CHAR(6) | |
| 12 | END_PLAN_TSTFR | Earliest planned end of the visit — the open end of the departure window | DEC(15) | |
| 13 | END_PLAN_TSTTO | Latest planned end of the visit — the close of the departure window | DEC(15) | |
| 14 | END_ACTUAL | Actual end of the visit | DEC(15) | |
| 15 | END_TZONE | Time zone the end times are read in locally | CHAR(6) | |
| 16 | DRIVER | Driver on this visit — recorded per activity, not on the vehicle master, because it changes visit to visit | CHAR(40) | |
| 17 | TSP_CURR | Carrier actually serving this visit | CHAR(10) | |
| 18 | VEH_WEIGHT | Weighed total weight of the vehicle for this visit | QUAN(15,3) | |
| 19 | VEH_WEIGHT_UOM | Unit the weighed weight is expressed in | UNIT(3) | |
| 20 | YARD | Warehouse number of the yard the activity takes place in | CHAR(4) |
Field provenance: hand-curated. 3 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /SCWM/VEH_SR_ACTon 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>, <TS_FROM>, <TS_TO>
-- ============================================================
-- Table : /SCWM/VEH_SR_ACT — Vehicle activities — the same shipping-and-receiving activity shape for a vehicle: planned and actual times, activity type and direction, the driver, the carrier, and the weighed weight
-- Purpose: Column-selected read of /SCWM/VEH_SR_ACT — auto-generated from field metadata
-- Grain : One row per client + VEH_NUM + VEH_SR_ACT_NUM
-- Caution: One row per vehicle visit, not per vehicle — and the vehicle's activity is a different row from the transportation unit's, so a yard dwell measure must decide which object it is measuring
-- Notes : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/VEH_SR_ACT; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_veh_sr_act — 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.VEH_NUM AS "Internal vehicle number the activity belongs to",
t.VEH_SR_ACT_NUM AS "Shipping-and-receiving activity number — one visit of this vehicle",
t.ACT_ID AS "GUID of the shipping-and-receiving activity",
lower(hex(t.ACT_ID)) AS "GUID of the shipping-and-receiving activity (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 visit", -- UTC
t.START_PLAN_TSTTO AS "Latest planned start of the visit", -- UTC
t.START_ACTUAL AS "Actual start of the visit", -- 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 visit — the open end of the departure window", -- UTC
t.END_PLAN_TSTTO AS "Latest planned end of the visit — the close of the departure window", -- UTC
t.END_ACTUAL AS "Actual end of the visit", -- UTC
t.END_TZONE AS "Time zone the end times are read in locally",
t.DRIVER AS "Driver on this visit — recorded per activity, not on the vehicle master, because it changes visit to visit",
t.TSP_CURR AS "Carrier actually serving this visit",
t.VEH_WEIGHT AS "Weighed total weight of the vehicle for this visit",
t.VEH_WEIGHT_UOM AS "Unit the weighed weight is expressed in",
t.YARD AS "Warehouse number of the yard the activity takes place in"
FROM <catalog>.<schema>.scwm_veh_sr_act t
WHERE
t.MANDT = '<client>' -- client filter — drop on single-client systems
-- AND t.START_ACTUAL >= <TS_FROM> -- UTC yyyymmddhhmmss — convert warehouse-local dates first (#utc-timestamps)
-- AND t.START_ACTUAL <= <TS_TO>
ORDER BY t.VEH_NUM;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_veh_sr_act.MANDT = scwm_vehicle.MANDT AND scwm_veh_sr_act.VEH_NUM = scwm_vehicle.VEH_NUM
More Yard & Material Flow tables
- /SCWM/VEHICLEVehicles — the tractors and trucks that move transportation units through the yard, with the means of transport, carrier, license plate, and the flag that marks a permanently coupled transportation unit
- /SCWM/DOOR_SRACTDoor activities — the shipping-and-receiving activities assigned to a warehouse door, with the planned and actual occupancy window
- /SCWM/TMFSCPCommunication points — the identification points, scanners, and segments of the conveyor network a controller reports against, each mapped to a storage bin, with its capacity and the clarification point faults are routed to
- /SCWM/TMFSPLCProgrammable logic controllers — the material flow system's definition of each controller EWM exchanges telegrams with, including the warehouse process types used for conveyor putaway, fault handling, and stock transfer
- /SCWM/TU_DLVTransportation unit assignments — one row per delivery or handling unit loaded onto (or unloaded from) a transportation unit for one shipping-and-receiving activity
- /SCWM/TU_SR_ACTTransportation unit activities — one row per shipping-and-receiving activity of a transportation unit, carrying the planned and actual start and end times, the activity type, category and direction, the carrier of the day, and the weighed weight