JDE Reference
P3411
InteractiveMRP/MPS Detail Message Revisions — the screen where planners review and process the action messages MRP generated, releasing them into work orders or purchase orders.
Lineage hook
Rows written by P3411 carry …PID = 'P3411' 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
2 parameters not filled: <catalog>, <schema_data>
-- ============================================================
-- Program: P3411 MRP/MPS Detail Message Revisions — the screen where planners review and process the action messages MRP generated, releasing them into work orders or purchase orders.
-- Purpose: MRP/MPS Detail Message Revisions — the screen where planners review and process the action messages MRP generated, releasing them into work orders or purchase orders. — auto-generated boilerplate from program-table-map
-- Grain : F3411 × F3412, F4801 — 1:N joins yield one row per detail line
-- Tables : F3411, F3412, F4801
-- 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: F4102 is cataloged for this program, but no verified join condition connects it to F3411, so it is left out of this skeleton. Add the join yourself using the key fields on each table's page.
-- ============================================================
SELECT
h.MMUKID AS "Internal unique key — single-column primary key with no business meaning",
h.MMDSC1 AS "Message text shown to the planner"
FROM <catalog>.<schema_data>.f3411 h
LEFT JOIN <catalog>.<schema_data>.f3412 f
ON f.MWUKID = h.MMUKID
LEFT JOIN <catalog>.<schema_data>.f4801 f4
ON f4.WADOCO = h.MMDOCO
ORDER BY h.MMUKID;Tables Used by This Program
How these tables connect — join details in the list below.
Loading relationship diagram…
R read · W write · R/W read + write
Secondary tables
- F3412MRP pegging — one row per lower-level requirement showing which parent item/order generated demand for a component, so you can trace a shortage up to the end-item order that caused itRead accesstransaction
- F4102Item branch — branch/plant-level item attributes, planning parameters, and sourcing responsibilityRead accessmaster
- F4801Work order header — one row per work order carrying the item being made, branch, quantities ordered/completed/scrapped, status, and the requested/start/completion dates that drive shop floor and maintenance analyticsWrite accesstransaction