P4960

-- ============================================================
-- Program: P4960 Work With Loads — the interactive workbench that builds and maintains loads by grouping shipments onto vehicles, assigning carriers, and sequencing stops
-- Purpose: Work With Loads — the interactive workbench that builds and maintains loads by grouping shipments onto vehicles, assigning carriers, and sequencing stops — auto-generated boilerplate from program-table-map
-- Grain  : F4960 × F4961, F4941 — 1:N joins yield one row per detail line
-- Tables : F4960, F4961, F4941
-- Notes  : Auto-generated skeleton. Julian dates are converted to DATE and implied-decimal amounts are scaled (verify decimals in F9210). Audit columns (…USER/…PID/…UPMJ) are omitted — see the quirks guide. Set catalog/schema to your Unity Catalog location; fill remaining placeholders (<...>) for your tenant.
-- Omitted: F4215 is cataloged for this program, but no verified join condition connects it to F4960, so it is left out of this skeleton. Add the join yourself using the key fields on each table's page.
-- ============================================================
SELECT
  TRIM(h.TMVMCU) AS "Trip depot business unit - first half of the load key.",
  h.TMLDNM AS "Load number - second half of the load key; join to F4960/F4961.",
  h.TMDSCD AS "Disposition code.",
  f.LLTRPL AS "Load leg number within the load.",
  f49.RSSHPN AS "Shipment number - the system-assigned key that groups order lines for transport; the same value lands on F4211.SDSHPN.",
  f49.RSRSSN / POWER(10, 1) AS "Routing step number within the shipment."  -- implied decimals: 1 (verify in F9210)
FROM <catalog>.<schema_data>.f4960 h
LEFT JOIN <catalog>.<schema_data>.f4961 f
  ON f.LLLDNM = h.TMLDNM
 AND f.LLVMCU = h.TMVMCU
LEFT JOIN <catalog>.<schema_data>.f4941 f49
  ON f49.RSLDNM = h.TMLDNM
ORDER BY h.TMVMCU;