Skip to content
JDE Reference

P4960

Interactive

Work 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 SQL

Starting 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

2 parameters not filled: <catalog>, <schema_data>

-- ============================================================
-- 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;

Tables Used by This Program

How these tables connect — join details in the list below.

Join details

  • F4215F4941header detail · 1:N
    ON f4215.XHSHPN = f4941.RSSHPN
  • F4960F4961header detail · 1:N
    ON f4960.TMLDNM = f4961.LLLDNM
  • F4941F4960foreign key · N:1
    ON f4941.RSLDNM = f4960.TMLDNM

R read · W write · R/W read + write

Secondary tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle. Oracle, JD Edwards, and EnterpriseOne are registered trademarks of Oracle and/or its affiliates.