Search Results msd_mfg_fcst_v




Overview
Explore in AI Chat

Overview

The APPS.MSD_MFG_FCST_V view is a reporting and integration object within the Oracle E-Business Suite Demand Planning (MSD) module. Its documented purpose is to expose the Manufacturing Forecast in a denormalized, query-friendly form suitable for downstream reporting, analytics, and integration with Planning Central and other MSCA/MSC consumers. The view's status in ETRM is VALID, and it is owned by the APPS schema.

A distinguishing characteristic noted in the ETRM description is that this view is not stripped by the demand plan id. Instead, it carries a FORECAST_DESIGNATOR that a consumer can join with the Demand Plan parameter's name to filter the manufacturing forecast by a specific demand plan. This design makes the view flexible for multi-plan scenarios, where a single result set may legitimately contain forecast rows belonging to more than one demand plan.

Underlying Base Objects

The view is defined over two referenced base objects, both accessed through synonyms in the APPS schema:

Each join is anchored on the matching INSTANCE plus the corresponding SR_*_PK surrogate, constrained by a fixed LEVEL_ID: 7 for Inventory Org, 1 for Item, 15 for Customer, 27 for Sales Channel, and 11 for Ship-To Location. The Org and Item joins are inner joins (mandatory dimensions), while the Customer, Sales Channel, and Ship-To Location joins are outer joins, which means forecast rows without a value at those levels are retained. The forecast designator that supports demand-plan stripping is sourced directly from MSD_MFG_FORECAST.FORECAST_DESIGNATOR.

Key Columns

  • FORECAST_DESIGNATOR — identifies the manufacturing forecast and is the field used with the Demand Plan parameter name to isolate a specific demand plan.
  • INV_ORG / INV_ORG_PK — inventory organization level value and its surrogate key.
  • ITEM / ITEM_PK — item level value and surrogate key.
  • CUSTOMER / CUSTOMER_PK — customer level value and surrogate key (nullable, outer join).
  • SALES_CHANNEL / SALES_CHANNEL_PK — sales channel level value and surrogate key (nullable, outer join).
  • SHIP_TO_LOC / SHIP_TO_LOC_PK — ship-to location level value and surrogate key (nullable, outer join).
  • USER_DEFINED1, USER_DEFINED2 — user-defined attribute columns; the corresponding *_PK columns are emitted as NULL.
  • BUCKET_TYPE — granularity of the forecast bucket (for example, day, week, period).
  • FORECAST_DATE, RATE_END_DATE — the bucket start and rate end boundaries.
  • ORIGINAL_QUANTITY, CURRENT_QUANTITY — the originally generated forecast quantity and the currently effective quantity.

Common Use Cases and Queries

Typical uses include reconciling manufacturing forecast quantities by organization, item, and bucket, and feeding downstream planning or BI extracts. Because the view is not pre-filtered by demand plan, queries commonly constrain on the designator and date range.

Forecast by item and bucket for a given designator:

  • SELECT item, inv_org, bucket_type, forecast_date, original_quantity, current_quantity FROM apps.msd_mfg_fcst_v WHERE forecast_designator = :designator AND forecast_date BETWEEN :from_date AND :to_date ORDER BY item, forecast_date;

Aggregated manufacturing forecast by organization:

  • SELECT inv_org, SUM(current_quantity) total_qty FROM apps.msd_mfg_fcst_v WHERE forecast_designator = :designator GROUP BY inv_org;

Detailed breakdown including optional dimensions (outer-joined columns may be NULL):

  • SELECT item, customer, sales_channel, ship_to_loc, forecast_date, current_quantity FROM apps.msd_mfg_fcst_v WHERE forecast_designator = :designator AND item = :item;

When consuming the view programmatically, callers should apply the forecast designator together with the demand plan parameter name to achieve the demand-plan-level striping that the base object deliberately omits.