R3482
Batch UBEMRP/MPS Requirements Planning — the batch job that runs single-facility MRP/MPS, netting forecasts, sales orders, and on-hand supply into time-phased plans and action messages.
Rows written by R3482 carry …PID = 'R3482' in their audit columns — a ready-made marker for isolating the records this program produced. See the audit-columns guide
Single-plant generation; planning BOMs are only supported here, not in R3483.
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.
2 parameters not filled: <catalog>, <schema_data>
-- ============================================================
-- Program: R3482 MRP/MPS Requirements Planning — the batch job that runs single-facility MRP/MPS, netting forecasts, sales orders, and on-hand supply into time-phased plans and action messages.
-- Purpose: MRP/MPS Requirements Planning — the batch job that runs single-facility MRP/MPS, netting forecasts, sales orders, and on-hand supply into time-phased plans and action messages. — 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: F3413, F3460, F4102 are cataloged for this program, but no verified join condition connects them to F3411, so they are 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 f3
ON f3.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
Primary tables
- F3411MRP action messages — one row per recommendation the planning run generates (order, expedite, defer, cancel, increase, decrease) for an item/branch; planners work this queue after each runWrite accesstransaction
- F3413MRP time series — one row per item/branch/quantity-type/date bucket; the quantity-type dimension (demand, supply, projected on-hand, ATP, etc.) turns this narrow table into the full planning gridWrite accesstransaction
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 itWrite accesstransaction
- F3460One row per forecast quantity/amount — keyed by item, branch, forecast type, requested date, year, and customer — holding the demand forecasts (both generated and adjusted) that feed MRP/DRP.Read 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 analyticsRead accesstransaction