Skip to content
JDE Reference

F3412

transactionAlso in JDE World

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

Notes

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

KeyFieldAliasDescriptionTypeLengthFlags
MWITMITMComponent short item number the requirement is forNumeric8
MWMCUMCUComponent branch/plant — right-justified 12-characterString12
MWDRQJDRQJDate the component is required (Julian CYYDDD)Numeric6
MWLOVDLOVDLeadtime offset days applied when exploding the requirement down from the parentNumeric6
MWKITKITParent short item number whose planned or actual order generated this demandNumeric8
MWMMCUMMCUParent branch/plant — right-justified 12-characterString12
MWUORGUORGRequirement quantity pegged to the parentNumeric15
MWDOCODOCOOrder number of the pegged supply/demand order (work order, purchase order, etc.)Numeric8
MWDCTODCTOOrder type of the pegged orderString2
MWRKCORKCOCompany of the related orderString5
MWRORNRORNRelated order number — carries the originating order reference through the pegString8
MWRCTORCTORelated order typeString2
MWRLLNRLLNRelated order line number; 3 implied decimalsNumeric7
Primary keyMWUKIDUKIDInternal unique key — the primary key; no business meaningNumeric15
MWPLNKPLNKPegging record link — internal pointer chaining related pegging rows across levelsNumeric15
MWPRJMPRJMProject number for project-driven requirementsNumeric8
MWSRDMSRDMSource demand reference for replenishment-driven requirementsNumeric8
MWPNSPNSProduction number short for production-number-controlled peggingNumeric10

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.

Query parameters
-- ============================================================
-- 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