/SCWM/TU_SR_ACT

-- ============================================================
-- Table  : /SCWM/TU_SR_ACT — Transportation 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
-- Purpose: Column-selected read of /SCWM/TU_SR_ACT — auto-generated from field metadata
-- Grain  : One row per client + TU_NUM + TU_SR_ACT_NUM
-- Caution: The activity is the grain, not the transportation unit — one trailer visiting twice in a week is two rows, and a per-TU count is not a count of visits
-- Notes  : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/TU_SR_ACT; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_tu_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.TU_NUM AS "Internal transportation unit number the activity belongs to",
  t.TU_SR_ACT_NUM AS "Shipping-and-receiving activity number — one visit of this transportation unit",
  t.ACT_ID AS "GUID of the shipping-and-receiving activity — the same identifier the vehicle and door activity tables carry",
  lower(hex(t.ACT_ID)) AS "GUID of the shipping-and-receiving activity — the same identifier the vehicle and door activity tables carry (hex)",  -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
  t.ACT_TYPE AS "Activity type — what is being done during the visit",
  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 activity — the open end of the arrival window",  -- UTC
  t.START_PLAN_TSTTO AS "Latest planned start — the close of the arrival window; against the actual start this is the arrival-punctuality measure",  -- UTC
  t.START_ACTUAL AS "Actual start of the activity",  -- 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 activity — the open end of the departure window",  -- UTC
  t.END_PLAN_TSTTO AS "Latest planned end of the activity — the close of the departure window",  -- UTC
  t.END_ACTUAL AS "Actual end of the activity — with the actual start, the dwell time of the visit",  -- UTC
  t.END_TZONE AS "Time zone the end times are read in locally",
  t.TSP_CURR AS "Carrier actually serving this visit, which can differ from the one on the transportation unit master",
  t.TU_WEIGHT AS "Weighed total weight of the transportation unit for this visit",
  t.TU_WEIGHT_UOM AS "Unit the weighed weight is expressed in",
  t.YARD AS "Warehouse number of the yard the activity takes place in, where the yard is modeled as its own warehouse"
FROM <catalog>.<schema>.scwm_tu_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.TU_NUM;