/SCWM/TU_STATUS

-- ============================================================
-- Table  : /SCWM/TU_STATUS — Transportation unit activity statuses — one row per activity per status type, with its value, the posting time, and a reason code
-- Purpose: Column-selected read of /SCWM/TU_STATUS — auto-generated from field metadata
-- Grain  : One row per client + TU_NUM + TU_SR_ACT_NUM + STATUS_TYPE
-- Caution: Long and narrow — filter STATUS_TYPE before pivoting, or one activity fans out across every status type it has ever carried
-- 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_STATUS; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_tu_status — adjust to your landing convention (see quirks #namespace-slashes). 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",
  t.TU_SR_ACT_NUM AS "Activity number the status belongs to",
  t.STATUS_TYPE AS "Status type — part of the key, which is what makes this table long and narrow rather than one row per activity",
  t.STATUS_VALUE AS "Value the status type currently carries",
  t.BOOKTST AS "Posting time of the status — the stamp a status-to-status duration is measured from",  -- UTC
  t.REASON AS "Reason code recorded with the status"
FROM <catalog>.<schema>.scwm_tu_status t
WHERE
  t.MANDT = '<client>'  -- client filter — drop on single-client systems
  -- AND t.STATUS_TYPE = '<STATUS_TYPE>'
  -- AND t.BOOKTST >= <TS_FROM>  -- UTC yyyymmddhhmmss — convert warehouse-local dates first (#utc-timestamps)
  -- AND t.BOOKTST <= <TS_TO>
ORDER BY t.TU_NUM;