F3412
transactionAlso in JDE WorldMRP 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 it
At 9.20 this is the pegging (lower-level requirements) table, not a time series — F3413 holds the buckets. ITM/MCU is the component with demand; KIT/MMCU is the parent that drove it; DOCO/DCTO points at the pegged order and PLNK chains pegging records. Regenerated by each planning run.
Fields
18 fields · 1 key
| Key | Field | Alias | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| MWITM | ITM | Component short item number the requirement is for | Numeric | 8 | ||
| MWMCU | MCU | Component branch/plant — right-justified 12-character | String | 12 | ||
| MWDRQJ | DRQJ | Date the component is required (Julian CYYDDD) | Numeric | 6 | ||
| MWLOVD | LOVD | Leadtime offset days applied when exploding the requirement down from the parent | Numeric | 6 | ||
| MWKIT | KIT | Parent short item number whose planned or actual order generated this demand | Numeric | 8 | ||
| MWMMCU | MMCU | Parent branch/plant — right-justified 12-character | String | 12 | ||
| MWUORG | UORG | Requirement quantity pegged to the parent | Numeric | 15 | ||
| MWDOCO | DOCO | Order number of the pegged supply/demand order (work order, purchase order, etc.) | Numeric | 8 | ||
| MWDCTO | DCTO | Order type of the pegged order | String | 2 | ||
| MWRKCO | RKCO | Company of the related order | String | 5 | ||
| MWRORN | RORN | Related order number — carries the originating order reference through the peg | String | 8 | ||
| MWRCTO | RCTO | Related order type | String | 2 | ||
| MWRLLN | RLLN | Related order line number; 3 implied decimals | Numeric | 7 | ||
| Primary key | MWUKID | UKID | Internal unique key — the primary key; no business meaning | Numeric | 15 | |
| MWPLNK | PLNK | Pegging record link — internal pointer chaining related pegging rows across levels | Numeric | 15 | ||
| MWPRJM | PRJM | Project number for project-driven requirements | Numeric | 8 | ||
| MWSRDM | SRDM | Source demand reference for replenishment-driven requirements | Numeric | 8 | ||
| MWPNS | PNS | Production number short for production-number-controlled pegging | Numeric | 10 |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading F3412on Databricks — Julian dates, implied decimals, and padded strings are already converted. Set your Unity Catalog location and filter values below; they’re substituted into the SQL and the copy button.
-- ============================================================
-- Table : F3412 MRP 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 it
-- Purpose: Column-selected read of F3412 — auto-generated from field metadata
-- Grain : One row per MWUKID
-- Notes : Auto-generated skeleton. Julian dates (CYYDDD) are converted to DATE and implied-decimal amounts are scaled (verify decimals in F9210); padded business-unit/UDC keys are TRIMmed. 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
f.MWUKID AS "Internal unique key — the primary key; no business meaning",
f.MWITM AS "Component short item number the requirement is for",
TRIM(f.MWMCU) AS "Component branch/plant — right-justified 12-character",
CASE WHEN f.MWDRQJ IS NULL OR f.MWDRQJ = 0 THEN NULL ELSE DATE_ADD(MAKE_DATE(1900 + CAST(f.MWDRQJ AS INT) DIV 1000, 1, 1), CAST(f.MWDRQJ AS INT) % 1000 - 1) END AS "Date the component is required (Julian CYYDDD)", -- CYYDDD Julian → DATE
f.MWLOVD AS "Leadtime offset days applied when exploding the requirement down from the parent",
f.MWKIT AS "Parent short item number whose planned or actual order generated this demand",
TRIM(f.MWMMCU) AS "Parent branch/plant — right-justified 12-character",
f.MWUORG AS "Requirement quantity pegged to the parent",
f.MWDOCO AS "Order number of the pegged supply/demand order (work order, purchase order, etc.)",
f.MWDCTO AS "Order type of the pegged order",
f.MWRKCO AS "Company of the related order",
f.MWRORN AS "Related order number — carries the originating order reference through the peg",
f.MWRCTO AS "Related order type",
f.MWRLLN / POWER(10, 3) AS "Related order line number; 3 implied decimals", -- implied decimals: 3 (verify in F9210)
f.MWPLNK AS "Pegging record link — internal pointer chaining related pegging rows across levels",
f.MWPRJM AS "Project number for project-driven requirements",
f.MWSRDM AS "Source demand reference for replenishment-driven requirements",
f.MWPNS AS "Production number short for production-number-controlled pegging"
FROM <catalog>.<schema_data>.f3412 f
ORDER BY f.MWUKID;2 parameters not filled: <catalog>, <schema_data>
Relationships
1-hop neighbors — click a table to navigate there. UDC decode edges point coded fields at their F0005 lookup.
Programs That Use This Table
Secondary programs
- P3411MRP/MPS Detail Message Revisions — the screen where planners review and process the action messages MRP generated, releasing them into work orders or purchase orders.Read accessInteractive
- R3482MRP/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.Write accessBatch UBE
- R3483Master Planning Schedule - Multiple Plant — the batch job that runs multifacility requirements planning, generating transfer-order messages and time series across a network of branch/plants.Write accessBatch UBE