/SCWM/TU
ChangeMaintain a transportation unit — arrival, door assignment, loading and unloading, and departure for one trailer or container visit
Everything this transaction records is per VISIT, not per trailer: the times, the door, the carrier, and the statuses all land on a shipping-and-receiving activity row, while the transportation unit master stays static.
Tables behind this transaction
Curated: these are the tables an analyst reads to see what this transaction did, and how it touches each of them. Every table page carries its own field list and Databricks SQL.
How these tables connect — join details in the list below. GUID joins and text-table joins are highlighted.
Join details
ON scwm_tu_sr_act.MANDT = scwm_tunit.MANDT AND scwm_tu_sr_act.TU_NUM = scwm_tunit.TU_NUM -- many visits per transportation unit — a per-TU count is not a count of visitsmany visits per transportation unit — a per-TU count is not a count of visits
ON scwm_tunit.MANDT = scwm_vehicle.MANDT AND scwm_tunit.FIXED_VEH_NUM = scwm_vehicle.VEH_NUM -- the PERMANENT pairing only, and the two columns share a data element; the vehicle actually pulling a trailer on a given visit is not on this row — that pairing lives in the two activity tablesthe PERMANENT pairing only, and the two columns share a data element; the vehicle actually pulling a trailer on a given visit is not on this row — that pairing lives in the two activity tables
ON scwm_tu_status.MANDT = scwm_tu_sr_act.MANDT AND scwm_tu_status.TU_NUM = scwm_tu_sr_act.TU_NUM AND scwm_tu_status.TU_SR_ACT_NUM = scwm_tu_sr_act.TU_SR_ACT_NUM -- a status sidecar, not a header/item pair — one row per status type per activity, so filter STATUS_TYPE before joining or the activity fans outa status sidecar, not a header/item pair — one row per status type per activity, so filter STATUS_TYPE before joining or the activity fans out
ON scwm_tu_dlv.MANDT = scwm_tu_sr_act.MANDT AND scwm_tu_dlv.TU_NUM = scwm_tu_sr_act.TU_NUM AND scwm_tu_dlv.TU_SR_ACT_NUM = scwm_tu_sr_act.TU_SR_ACT_NUM -- the exact-grain parent: an assignment belongs to one visit of the transportation unit, not to the unit itself — the TU master is one hop further onthe exact-grain parent: an assignment belongs to one visit of the transportation unit, not to the unit itself — the TU master is one hop further on
ON scwm_door_sract.MANDT = scwm_tdoor.MANDT AND scwm_door_sract.DOOR = scwm_tdoor.DOOR AND scwm_door_sract.LGNUM = scwm_tdoor.LGNUMON 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:1both 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
R read · W write · R/W read + write
Primary tables
- /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 weightRead/write accessMixed keytransaction
- /SCWM/TUNITTransportation units — the trailers, containers, and swap bodies goods are loaded into, with the internal and external number, the means of transport, the carrier, and the license plateRead/write accessMixed keymaster
Secondary tables
- /SCWM/DOOR_SRACTDoor activities — the shipping-and-receiving activities assigned to a warehouse door, with the planned and actual occupancy windowRead/write accessMixed keytransaction
- /SCWM/TDOORDoors — the loading and unloading points of the warehouse, each mapped to a bin, a default staging area, and (where a yard exists) the matching yard binRead accessMixed keyconfig
- /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 activityRead/write accessMixed keytransaction
- /SCWM/TU_STATUSTransportation unit activity statuses — one row per activity per status type, with its value, the posting time, and a reason codeRead/write accessSemantic keytransaction
- /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 unitRead accessMixed keymaster