P4915
InteractiveWork With Shipments — the interactive workbench for reviewing, revising, routing, rating, and approving shipments after order entry creates them
Rows written by P4915 carry …PID = 'P4915' in their audit columns — a ready-made marker for isolating the records this program produced. See the audit-columns guide →
Central Transportation Management application; processing options control manual shipment consolidation. Operates on the shipment header F4215 (the F49xx name does not exist at 9.20).
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.
-- ============================================================
-- Program: P4915 Work With Shipments — the interactive workbench for reviewing, revising, routing, rating, and approving shipments after order entry creates them
-- Purpose: Work With Shipments — the interactive workbench for reviewing, revising, routing, rating, and approving shipments after order entry creates them — auto-generated boilerplate from program-table-map
-- Grain : F4215 × F4941, F4211 — 1:N joins yield one row per detail line
-- Tables : F4215, F4941, F4211
-- 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
h.XHSHPN AS "Shipment number - the system-assigned key that groups order lines for transport; the same value lands on F4211.SDSHPN.",
f.RSRSSN / POWER(10, 1) AS "Routing step number within the shipment.", -- implied decimals: 1 (verify in F9210)
d.SDKCOO AS "Order key company - disambiguates order numbers across companies",
d.SDDOCO AS "Order number",
d.SDDCTO AS "Order type code (SO, ST, CO, ...)",
d.SDLNID / POWER(10, 3) AS "Order line number, stored x1000 (3 implied decimals)" -- implied decimals: 3 (verify in F9210)
FROM <catalog>.<schema_data>.f4215 h
LEFT JOIN <catalog>.<schema_data>.f4941 f
ON f.RSSHPN = h.XHSHPN
LEFT JOIN <catalog>.<schema_data>.f4211 d
ON 1 = 1 -- TODO: define join condition (no shared aliases detected)
ORDER BY h.XHSHPN;2 parameters not filled: <catalog>, <schema_data>
Tables Used by This Program
How these tables connect. Nodes are clickable.
Secondary tables
- F4211Sales order detail — one row per order line; the core sales transaction tableRead 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/write accesstransaction