Results for “consumed_qty”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MSC_FORECAST_UPDATES_V is a view owned by the APPS schema within the Oracle E-Business Suite Advanced Supply Chain Planning module (MSC). Its function, as documented in the ETRM metadata, is to surface all forecast update records generated by the planning engine. These records capture changes in forecast demand quantities and the associated consumption of forecast against actual sales order demand, information essential to understanding how forecasted demand is being offset by firm orders during a planning run.

The view places particular emphasis on the FORECAST_QTY column, which holds the forecast quantity associated with a given demand update. Because the view is defined over the forecast update staging area rather than the operational demand tables alone, it provides a consolidated, plan-aware picture of forecast movements across plan, organization, and source instance contexts. It is commonly used in custom reporting, diagnostics of forecast consumption behavior, and integration scenarios where downstream systems need to read forecast updates from the planning schema.

Underlying Base Objects

The documented base objects referenced by the view are MSC_FORECAST_UPDATES (exposed through a synonym) and the package MSC_GET_NAME. Internally, the view text joins MSC_FORECAST_UPDATES (aliased MFU) to MSC_DEMANDS (aliased MD) on a set of plan, organization, source instance, and demand identifier keys. A UNION combines two passes over the same data to capture both the SALES_ORDER_ID matching MD.DEMAND_ID and the case where it matches MD.GROUP_ID.

The MSC_GET_NAME package is invoked to translate internal foreign keys into readable names: DESIGNATOR, FORECASTSETNAME, and ITEM_NAME for both the demand and originating items. A critical filter is applied — NVL(MFU.FORECAST_QTY, 0) <> 0 — meaning only forecast update rows with a non-zero forecast quantity are returned.

Key Columns

• FORECAST_QTY: the primary forecast quantity for the update; rows with a null or zero value are excluded by the view definition.
• FORECAST_DEMAND_ID, SALES_ORDER_ID, SALES_ORDER_NUMBER: identifiers linking the forecast update to its underlying demand and sales order.
• SALES_ORDER_QTY, CONSUMED_QTY, OVERCONSUMPTION_QTY: quantities describing how much sales order demand was consumed against the forecast and any excess consumption.
• PLAN_ID, ORGANIZATION_ID, SR_INSTANCE_ID: planning and multi-org context keys; also used in the join conditions.
• DESIGNATOR_ID, FORECAST_SET_ID: forecast designator and forecast set identifiers, resolved to names via MSC_GET_NAME.
• INVENTORY_ITEM_ID, CUSTOMER_ID, SHIP_ID, BILL_ID, DEMAND_CLASS: item, customer, and classification attributes of the forecast.
• LAST_UPDATE_DATE, CREATION_DATE, LAST_UPDATED_BY, CREATED_BY: standard audit columns.
• Derived name columns from MSC_GET_NAME: designator name, forecast set name, item name, and original item name.

Common Use Cases and Queries

The view is typically used to report forecast consumption activity and to reconcile forecast quantities against sales orders for a given plan. A representative query filtering on forecast quantity is:

SELECT plan_id, organization_id, inventory_item_id, forecast_qty, consumed_qty, sales_order_number FROM apps.msc_forecast_updates_v WHERE forecast_qty <> 0 AND plan_id = :plan_id;

Additional scenarios include extracting non-zero forecast updates for a specific source instance to feed a downstream planning or analytics process, and auditing overconsumption by comparing OVERCONSUMPTION_QTY across organizations. Because the view already excludes zero forecast quantities, queries addressing forecast_qty can rely on every returned row carrying a meaningful forecast value.