F3413
transactionAlso in JDE WorldMRP 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
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
| Key | Field | Alias | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Primary key | MRITM | ITM | Short item number — part of the primary key | Numeric | 8 | |
| Primary key | MRMCU | MCU | Branch/plant — part of the primary key; right-justified 12-character | String | 12 | |
| Primary key | MRQT | QT | Quantity type — the row dimension of the time series (forecast, gross requirements, planned orders, projected available, ATP, ...); part of the primary key | String | 2 | |
| Primary key | MRSTRT | STRT | Bucket start date (Julian CYYDDD) — part of the primary key | Numeric | 6 | |
| MRTRQT | TRQT | Quantity in the bucket for this quantity type | Numeric | 15 |
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.
-- ============================================================
-- 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
ON f3413.MRQT = f0005.DRKY
Programs That Use This Table
Primary programs
- P3413MPS Time Series — the screen that shows an item's time-phased supply and demand picture (the planning time series) produced by the last MRP/MPS run.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