Results for “forecast_quantity_consumed”

10 results




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

Overview

MRPFV_FORECAST_CONSUMPTIONS is an APPS-owned read-only view in the Oracle E-Business Suite Master Scheduling/MRP (MRP) product family. It reports the consumption of forecast entries against actual sales order demand, a process Oracle MRP performs during the forecast consumption routine when firm sales orders are netted against forecast quantities within the consumption window. The view presents one row per forecast consumption transaction, linking the originating sales order header and line to the forecast update record and the corresponding MTL_DEMAND_OMOE demand row. In EBS 12.1.1 and 12.2.2 the object is documented as VALID in the APPS schema, and its view text carries a read-only constraint (WITH READ ONLY) plus an ORG security predicate (_SEC:FORUPD.ORGANIZATION_ID), meaning access is filtered by the organization security profile of the querying responsibility.

The view is relevant to the search term "sales_order_quantity" because SALES_ORDER_QUANTITY is one of its principal exposed columns, representing the quantity on the sales order schedule that participated in the forecast consumption calculation.

Underlying Base Objects

The documented base objects are MRP_FORECAST_UPDATES, MTL_DEMAND_OMOE, SO_HEADERS_ALL, and SO_LINES_ALL (all referenced through synonyms), together with the packages INV_DECIMALS_PUB, INV_SALESORDER, MRP_OE, and OE_INSTALL.

  • MRP_FORECAST_UPDATES — the driving table, aliased FORUPD. It stores the forecast update/consumption transaction records, including quantity consumed, demand class, and organizational context.
  • MTL_DEMAND_OMOE — the demand table, aliased DEMAND, joined on UPDATE_SEQ_NUM = DEMAND_ID and LINE_NUM = USER_LINE_NUM in an outer-join direction, providing the demand source line linkage.
  • SO_LINES_ALL — aliased SOLINE, outer-joined via DEMAND.DEMAND_SOURCE_LINE = SOLINE.LINE_ID.
  • SO_HEADERS_ALL — aliased SOHEADER, outer-joined via SOLINE.HEADER_ID = SOHEADER.HEADER_ID and supplying ORDER_NUMBER.

The outer joins ((+)) ensure forecast consumption rows are retained even when no matching demand or sales order line exists.

Key Columns

Common Use Cases and Queries

Typical uses include analyzing forecast accuracy (consumed versus ordered), auditing demand class consumption, and reconciling sales order demand with forecast updates. A representative query is:

  • SELECT sales_order_number, sales_order_line_number, sales_order_schedule_date, sales_order_quantity, forecast_quantity_consumed, demand_class FROM mrp.mrpfv_forecast_consumptions WHERE sales_order_number = :order_number;
  • SELECT demand_class, SUM(sales_order_quantity), SUM(forecast_quantity_consumed) FROM mrp.mrpfv_forecast_consumptions GROUP BY demand_class;

Because the view is read-only and organization-secured, queries should be issued from a responsibility with the correct inventory organization context.