Results for “mrp_forecast_dates_v”
28 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The APPS.MRP_FORECAST_DATES_V view is a denormalized reporting object within the Oracle E-Business Suite Master Scheduling/MRP (MRP) product family, valid in both release 12.1.1 and 12.2.2. It presents forecast entry records — the dated demand quantities that drive Master Production Scheduling and Material Requirements Planning — enriched with human-readable descriptive attributes drawn from multiple reference schemas. Its purpose is to expose the raw planning transactions held in the MRP_FORECAST_DATES table alongside lookup meanings, organization codes, item numbers, project and task descriptors, and WIP line codes, so that consumers do not have to resolve these joins themselves.
The view is primarily consumed by planning workbenches, forecast inquiry forms, custom reports, and integration extracts that require a flattened, presentation-ready picture of forecast consumption. Because it is an APPS-owned view rather than a table, it carries no triggers and inherits read-only semantics; all data manipulation must target MRP_FORECAST_DATES directly.
Underlying Base Objects
The view joins the MRP_FORECAST_DATES synonym (the genuine forecast fact table) to five supporting objects:
- MFG_LOOKUPS (VIEW) — supplies the MEANING for ORIGINATION_TYPE via LOOKUP_TYPE = 'MRP_FORECAST_ORIG'.
- MTL_ITEM_FLEXFIELDS (VIEW) — resolves INVENTORY_ITEM_ID and ORGANIZATION_ID to ITEM_NUMBER using the key flexfield definition.
- MTL_PARAMETERS (SYNONYM) — resolved with an outer join on SOURCE_ORGANIZATION_ID to yield ORGANIZATION_CODE.
- WIP_LINES (SYNONYM) — outer-joined on LINE_ID to provide LINE_CODE for forecasts tied to repetitive schedules.
- MRP_GET_PROJECT (PACKAGE) — invoked through MRP_GET_PROJECT.PROJECT and MRP_GET_PROJECT.TASK to translate PROJECT_ID and TASK_ID into descriptive project/task values.
The base joins to MTL_ITEM_FLEXFIELDS and MFG_LOOKUPS are mandatory (inner), while MTL_PARAMETERS and WIP_LINES are joined with the (+) outer-join operator so that forecasts lacking a source organization or WIP line are not dropped. PL/SQL function calls inside the SELECT list mean the package must be valid for the view to compile, and calls are executed per row at query time.
Key Columns
- TRANSACTION_ID / INVENTORY_ITEM_ID / ORGANIZATION_ID — primary identifiers of the forecast record.
- FORECAST_DESIGNATOR, FORECAST_DATE, BUCKET_TYPE, RATE_END_DATE — designate the forecast and the date bucket against which quantity is measured.
- ORIGINAL_FORECAST_QUANTITY / CURRENT_FORECAST_QUANTITY / CONFIDENCE_PERCENTAGE — the planned quantity before and after consumption, plus planner confidence.
- FORECAST_MAD — the forecast mean absolute deviation, a statistical measure of forecast error retained on the record and central to forecast accuracy reporting; the column the user searched for.
- FORECAST_TREND, FOCUS_TYPE, DEMAND_CLASS — planning classification attributes.
- ORIGINATION_TYPE and MEANING — coded and decoded source of the forecast entry.
- CUSTOMER_ID, SHIP_ID, BILL_ID — demand channel references for customer-sourced forecasts.
- PROJECT_ID / TASK_ID and their MRP_GET_PROJECT descriptions — project and task context.
- ITEM_NUMBER, ORGANIZATION_CODE, LINE_CODE — resolved descriptive values for the key IDs.
- ATTRIBUTE1–15, DDF_CONTEXT, ATTRIBUTE_CATEGORY — descriptive flexfield context columns.
- REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — concurrency audit columns identifying the program that last wrote the row.
Common Use Cases and Queries
Typical scenarios include forecast accuracy dashboards, demand-versus-consumption reconciliations, and extract programs feeding external planning engines. The FORECAST_MAD column is frequently the target of accuracy analysis, since it quantifies dispersion between forecast and actual demand.
- Forecast accuracy by item: extract FORECAST_MAD alongside ORIGINAL_FORECAST_QUANTITY and CURRENT_FORECAST_QUANTITY to compute error ratios over a date range.
- Demand channel analysis: group by MEANING (ORIGINATION_TYPE) and DEMAND_CLASS to attribute forecasted demand to its source.
- Project-linked demand: filter on PROJECT_ID or the MRP_GET_PROJECT description to report forecasts tied to specific projects.
- Repetitive schedule alignment: use LINE_CODE to compare forecasted quantities against WIP repetitive schedules.
A representative query:
SELECT organization_code, item_number, forecast_designator,
forecast_date, current_forecast_quantity, forecast_mad,
meaning AS origination_meaning
FROM apps.mrp_forecast_dates_v
WHERE organization_id = :p_org_id
AND forecast_date BETWEEN :p_start AND :p_end
ORDER BY item_number, forecast_date;
Because the view embeds PL/SQL function calls and outer joins, queries should constrain ORGANIZATION_ID and FORECAST_DATE to avoid full scans and repeated package execution across the full MRP_FORECAST_DATES volume.
-
View: MRP_FORECAST_DATES_V 12.2.2
Forecast entries view
APPS.MRP_FORECAST_DATES_V·↳ MFG_LOOKUPS·↳ MRP_FORECAST_DATES·↳ MRP_GET_PROJECT·Explore MRP module →
-
View: MRP_FORECAST_DATES_V 12.1.1
Forecast entries view
APPS.MRP_FORECAST_DATES_V·↳ MFG_LOOKUPS·↳ MRP_FORECAST_DATES·↳ MRP_GET_PROJECT·Explore MRP module →
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
SYNONYM: APPS.WIP_LINES 12.2.2
-
SYNONYM: APPS.WIP_LINES 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
VIEW: APPS.MFG_LOOKUPS 12.1.1
-
VIEW: APPS.MFG_LOOKUPS 12.2.2
-
SYNONYM: APPS.MTL_PARAMETERS 12.2.2
-
SYNONYM: APPS.MTL_PARAMETERS 12.1.1
-
eTRM - MRP Tables and Views 12.1.1
Recommendations based on user criteria selected in MRP Planner WorkBench
-
eTRM - MRP Tables and Views 12.2.2
Recommendations based on user criteria selected in MRP Planner WorkBench
-
eTRM - INV Tables and Views 12.2.2
-
eTRM - INV Tables and Views 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - MRP Tables and Views 12.1.1
Recommendations based on user criteria selected in MRP Planner WorkBench
-
eTRM - MRP Tables and Views 12.2.2
Recommendations based on user criteria selected in MRP Planner WorkBench
-
eTRM - INV Tables and Views 12.1.1
-
eTRM - INV Tables and Views 12.2.2