Search Results shipped_amount




Overview
Explore in AI Chat

Overview

APPS.MRP_BIS_FORECAST_TREND_V is a reporting view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases, owned by the APPS schema. The view exposes forecast-versus-actual demand trend data drawn from the Oracle Advanced Supply Chain Planning (ASCP) and MRP business intelligence schema (the MRP_BIS objects). Its purpose is to support forecast accuracy analysis by presenting forecasted demand, ordered demand, and shipped demand side by side across forecast sets, demand classes, organizations, and forecast dates.

The "BIS" prefix indicates a Business Intelligence System construct, meaning the view was designed as a reporting-friendly projection rather than a transactional entity. Because it is defined over a workbench object (MRP_BIS_FORECAST_WB), it is intended for read-only consumption in reports, discoverer workbooks, and downstream analytical queries. The view is commonly surfaced when users search for the "forecast_set" concept, as the forecast set identifier is the primary grouping dimension exposed by this view.

Underlying Base Objects

The view is defined over a single documented base object:

  • MRP_BIS_FORECAST_WB (referenced as a SYNONYM) — the forecast workbench data source that holds the consolidated forecast and actuals figures.

The ETRM metadata lists no additional joined tables. The view is a straight-line projection of the workbench object with two notable transformations: the duplicated FORECAST_SET column and the arithmetic division applied to the amount columns. The workbench itself is populated by concurrent processes that aggregate forecasting data for BI reporting. Because the view depends on a workbench object rather than a base transactional table, its data freshness is governed by the schedule of the associated data-collection programs.

The synonym reference indicates that MRP_BIS_FORECAST_WB is resolved through the standard APPS synonym layer, consistent with normal EBS schema-public object access patterns.

Key Columns

  • FORECAST_SET — the forecast set name or identifier. This is the principal grouping key and appears twice in the select list, effectively aliasing the same value for reporting convenience.
  • DEMAND_CLASS — the demand class associated with the forecast, allowing segmentation across distinct demand streams.
  • ORGANIZATION_ID — the inventory organization for which the data applies.
  • FORECAST_QUANTITY — the forecasted quantity for the period.
  • ORDER_QUANTITY — the booked/ordered quantity, used as the actual demand measure.
  • SHIPPED_QUANTITY — the shipped quantity, used as the fulfillment measure.
  • FORECAST_AMOUNT/1000, ORDER_AMOUNT/1000, SHIPPED_AMOUNT/1000 — monetary values scaled down by a factor of 1000 so reported figures appear in thousands.
  • FORECAST_DATE — the date bucket against which forecast and actuals are compared.

Common Use Cases and Queries

The primary use case is forecast accuracy and trend reporting: comparing forecast against orders and shipments by forecast set, demand class, organization, and date.

SELECT forecast_set,
       demand_class,
       organization_id,
       forecast_date,
       forecast_quantity,
       order_quantity,
       shipped_quantity,
       forecast_amount/1000,
       order_amount/1000,
       shipped_amount/1000
FROM   apps.mrp_bis_forecast_trend_v
WHERE  forecast_set = :p_forecast_set
AND    organization_id = :p_org_id
ORDER  BY forecast_date;

A second common scenario filters by date range to produce a period-over-period trend line, grouping on forecast_set to compare accuracy across competing forecasts. Accuracy can be derived in the query itself, for example dividing order_quantity by forecast_quantity to compute a consumption ratio, or using the amount columns for value-based variance analysis.

Because the amount columns are pre-scaled by 1000 in the view definition, report consumers should not re-scale these values. Any aggregation should account for the fact that the view already normalizes monetary figures to thousands.