Search Results mrp_bis_forecast_trend_v




Overview
Explore in AI Chat

Overview

MRP_BIS_FORECAST_TREND_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the MRP (Master Scheduling/MRP) product family. Its purpose is to expose forecast-versus-actual trend information in a business-intelligence-friendly format, supporting the Oracle Business Intelligence System (BIS) style of analytic reporting embedded in the manufacturing modules. The view presents forecast demand alongside the corresponding order and shipment activity, expressed in both quantity and monetary terms, so that planners and analysts can measure forecast accuracy and consumption over time.

In the context of a user searching for "forecast_set," this view is directly relevant: the FORECAST_SET column is the primary grouping key that identifies which forecast set the trend data belongs to. Because forecast sets are the organizational mechanism by which planners segment demand forecasts in Oracle MRP, this view allows reporting to be scoped to a specific forecast set. The view is a thin projection over a single worktable-style base object and contains no business logic beyond column aliasing and unit scaling, making it a straightforward read-only reporting surface valid in both 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined exclusively over MRP_BIS_FORECAST_WB, referenced through a synonym. MRP_BIS_FORECAST_WB is the underlying collection or worktable that stores the aggregated forecast, order, and shipment measures used by the BIS forecast trending reports. The view does not join to additional tables; instead, it selects a curated subset of columns from that base object and applies arithmetic transformations to the amount columns (dividing by 1000).

Because the base object is a single worktable populated by the forecast trending concurrent program or data collection process, the view reflects the state of that data as of its last refresh. The synonym resolution places the object under the APPS schema, which is standard for EBS reporting views. No base table outside the MRP_BIS_FORECAST_WB lineage is documented, so downstream dependencies are limited to that single object.

Key Columns

  • FORECAST_SET — The forecast set identifier, central to filtering and grouping forecast trend data. Appears twice in the projection (aliased as FORECAST_DESIGNATOR and FORECAST_SET in the column list).
  • DEMAND_CLASS — The demand class associated with the forecast, enabling segmentation by market or demand category.
  • ORGANIZATION_ID — The inventory organization to which the data pertains, supporting multi-org reporting.
  • FORECAST_QUANTITY / ORDER_QUANTITY / SHIPPED_QUANTITY — Quantity measures for forecast, booked orders, and shipments respectively.
  • FORECAST_AMOUNT / ORDER_AMOUNT / SHIPPED_AMOUNT — Monetary measures, scaled by dividing by 1000 to express values in thousands.
  • FORECAST_DATE — The date dimension for trending analysis.

Common Use Cases and Queries

Typical use is forecast accuracy and consumption reporting, comparing forecast, order, and shipped measures by forecast set, demand class, organization, and date.

SELECT forecast_set,
       demand_class,
       organization_id,
       forecast_date,
       forecast_quantity,
       order_quantity,
       shipped_quantity
FROM   apps.mrp_bis_forecast_trend_v
WHERE  forecast_set = :forecast_set
ORDER  BY forecast_date;

A second common pattern aggregates monetary measures for trend charts:

SELECT forecast_date,
       SUM(forecast_amount) forecast_amt_k,
       SUM(shipped_amount)  shipped_amt_k
FROM   apps.mrp_bis_forecast_trend_v
WHERE  organization_id = :org_id
GROUP  BY forecast_date;

These queries are appropriate for BI Publisher reports, custom dashboards, and ad hoc trend analysis across forecast sets.