Skip to content
JDE Reference

F3413

transactionAlso in JDE World

MRP 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 grid

Notes

Only 5 columns — the whole MPS/MRP/DRP time-series screen pivots out of it. QT (UDC 34/QT) is the row dimension. Pivot QT across STRT buckets to rebuild the planning grid. Fully regenerated each run; snapshot for plan-over-plan comparisons.

Fields

5 fields · 4 key

KeyFieldAliasDescriptionTypeLengthFlags
Primary keyMRITMITMShort item number — part of the primary keyNumeric8
Primary keyMRMCUMCUBranch/plant — part of the primary key; right-justified 12-characterString12
Primary keyMRQTQTQuantity type — the row dimension of the time series (forecast, gross requirements, planned orders, projected available, ATP, ...); part of the primary keyString2
Primary keyMRSTRTSTRTBucket start date (Julian CYYDDD) — part of the primary keyNumeric6
MRTRQTTRQTQuantity in the bucket for this quantity typeNumeric15

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading F3413on 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  : F3413 MRP 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 grid
-- Purpose: Column-selected read of F3413 — auto-generated from field metadata
-- Grain  : One row per MRITM + MRMCU + MRQT + MRSTRT
-- 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.MRITM AS "Short item number — part of the primary key",
  TRIM(f.MRMCU) AS "Branch/plant — part of the primary key; right-justified 12-character",
  f.MRQT AS "Quantity type — the row dimension of the time series (forecast, gross requirements, planned orders, projected available, ATP, ...); part of the primary key",
  CASE WHEN f.MRSTRT IS NULL OR f.MRSTRT = 0 THEN NULL ELSE DATE_ADD(MAKE_DATE(1900 + CAST(f.MRSTRT AS INT) DIV 1000, 1, 1), CAST(f.MRSTRT AS INT) % 1000 - 1) END AS "Bucket start date (Julian CYYDDD) — part of the primary key",  -- CYYDDD Julian → DATE
  f.MRTRQT AS "Quantity in the bucket for this quantity type"
FROM <catalog>.<schema_data>.f3413 f
WHERE
  f.MRITM = <ITM>
  -- AND f.MRMCU = '<MCU>'
ORDER BY f.MRITM;

4 parameters not filled: <catalog>, <schema_data>, <ITM>, <MCU>

Relationships

1-hop neighbors — click a table to navigate there. UDC decode edges point coded fields at their F0005 lookup.

Join details

  • F3413F0005UDC decode · N:1
    ON f3413.MRQT = f0005.DRKY

Programs That Use This Table