JDE Reference
P4960
InteractiveWork With Loads — the interactive workbench that builds and maintains loads by grouping shipments onto vehicles, assigning carriers, and sequencing stops
Lineage hook
Rows written by P4960 carry …PID = 'P4960' in their audit columns — a ready-made marker for isolating the records this program produced. See the audit-columns guide →
Boilerplate SQL
Databricks SQLStarting point for querying the tables behind this program. Set your Unity Catalog location and filter values below — they’re substituted into the SQL and the copy button.
Query parameters
-- ============================================================
-- 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, F4215, F4941 — 1:N joins yield one row per detail line
-- Tables : F4960, F4961, F4215, 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.
-- ============================================================
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.",
f4.XHSHPN AS "Shipment number - the system-assigned key that groups order lines for transport; the same value lands on F4211.SDSHPN.",
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>.f4215 f4
ON 1 = 1 -- TODO: define join condition (no shared aliases detected)
LEFT JOIN <catalog>.<schema_data>.f4941 f49
ON f49.RSLDNM = h.TMLDNM
ORDER BY h.TMVMCU;2 parameters not filled: <catalog>, <schema_data>
Tables Used by This Program
How these tables connect. Nodes are clickable.
Secondary tables
- F4215One row per shipment - the anchor record Transportation Management creates when order lines are grouped for delivery; despite the F42xx name it belongs to system 49. Carries status, mode, geography, weight, value, and promised dates.Read/write accesstransaction
- F4941One row per routing step of a shipment - where the carrier, mode, load assignment, scheduled vs. actual ship/delivery timestamps, and billable vs. payable freight totals live. The workhorse table for carrier performance and freight cost analysis.Read accesstransaction
- F4961One row per leg of a load - a depot-to-stop slice of the trip with scheduled versus confirmed weight, volume, and cube, plus scheduled and actual ship dates.Read/write accesstransaction