Skip to content
EWM Reference

/SCWM/VEH_SR_ACT

transactionMixed key

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

Identity
Module: Yard & Material FlowBronze: scwm_veh_sr_act
Grain note

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

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.

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

20 fields · 3 key

20 fields.

Table fields: position, field name, description, data type, and flags. 20 fields.
#FieldDescriptionTypeFlags
1MANDTClientCLNT(3)
Key
2VEH_NUMInternal vehicle number the activity belongs toCHAR(20)
Key
3VEH_SR_ACT_NUMShipping-and-receiving activity number — one visit of this vehicleNUMC(10)
Key
4ACT_IDGUID of the shipping-and-receiving activityRAW(16)
5ACT_TYPEActivity typeCHAR(1)
6ACT_CATActivity categoryCHAR(1)
7ACT_DIRDirection of the activity — inbound against outboundCHAR(1)
8START_PLAN_TSTFREarliest planned start of the visitDEC(15)
9START_PLAN_TSTTOLatest planned start of the visitDEC(15)
10START_ACTUALActual start of the visitDEC(15)
UTCFilter date
11START_TZONETime zone the start times are read in locally — the stored values are UTCCHAR(6)
12END_PLAN_TSTFREarliest planned end of the visit — the open end of the departure windowDEC(15)
13END_PLAN_TSTTOLatest planned end of the visit — the close of the departure windowDEC(15)
14END_ACTUALActual end of the visitDEC(15)
15END_TZONETime zone the end times are read in locallyCHAR(6)
16DRIVERDriver on this visit — recorded per activity, not on the vehicle master, because it changes visit to visitCHAR(40)
17TSP_CURRCarrier actually serving this visitCHAR(10)
18VEH_WEIGHTWeighed total weight of the vehicle for this visitQUAN(15,3)
19VEH_WEIGHT_UOMUnit the weighed weight is expressed inUNIT(3)
20YARDWarehouse number of the yard the activity takes place inCHAR(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.

Query parameters

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

  • /SCWM/VEH_SR_ACT/SCWM/VEHICLEforeign key · N:1
    ON scwm_veh_sr_act.MANDT = scwm_vehicle.MANDT AND scwm_veh_sr_act.VEH_NUM = scwm_vehicle.VEH_NUM

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.