JDE Reference
P4906
InteractiveCarrier Master — the setup application that defines carriers (address book link, modes handled, load tender and tracking preferences) used in routing and rating
Lineage hook
Rows written by P4906 carry …PID = 'P4906' in their audit columns — a ready-made marker for isolating the records this program produced. See the audit-columns guide →
Notes
A carrier must first exist in the Address Book (F0101).
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: P4906 Carrier Master — the setup application that defines carriers (address book link, modes handled, load tender and tracking preferences) used in routing and rating
-- Purpose: Carrier Master — the setup application that defines carriers (address book link, modes handled, load tender and tracking preferences) used in routing and rating — auto-generated boilerplate from program-table-map
-- Grain : F4906 × F0101 — 1:N joins yield one row per detail line
-- Tables : F4906, F0101
-- 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.CMCARS AS "Carrier number - the address book number (F0101.ABAN8) this carrier record extends."
FROM <catalog>.<schema_data>.f4906 h
LEFT JOIN <catalog>.<schema_data>.f0101 ab
ON ab.ABAN8 = h.CMCARS
ORDER BY h.CMCARS;2 parameters not filled: <catalog>, <schema_data>
Tables Used by This Program
How these tables connect. Nodes are clickable.