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:

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

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.