Search Results forecast_entry_id




Overview
Explore in AI Chat

Overview

APPS.MRPBV_FORECAST_CONSUMPTIONS is a read-only Oracle EBS view that reconciles forecast updates against actual sales order demand. It exposes the relationship between rows in MRP_FORECAST_UPDATES (the forecast consumption/update records produced by the planning engine) and the corresponding sales order demand rows held in MTL_DEMAND_OMOE, with additional descriptive context joined from SO_LINES_ALL and SO_HEADERS_ALL. In practice, the view answers the question: "which sales order line consumed, or was matched to, a given forecast update?" and returns the schedule date, quantities, and demand class associated with that match.

The view is defined with a WITH READ ONLY clause, confirming it is intended strictly for query and reporting, not for DML. It is a common investigative object when users search for "mtl_demand_omoe," since MTL_DEMAND_OMOE is one of its principal underlying synonyms. Typical consumers are forecast consumption reconciliation reports, order-versus-forecast variance analyses, and integration extracts that need to correlate planning forecast records back to order management source documents.

Underlying Base Objects

The view is defined over four objects that appear in the FROM clause: SO_HEADERS_ALL, SO_LINES_ALL, MTL_DEMAND_OMOE, and MRP_FORECAST_UPDATES. The documented referenced base objects also include the INV_DECIMALS_PUB, INV_SALESORDER, MRP_OE, and OE_INSTALL packages, which supply supporting logic or are invoked indirectly by the underlying objects and their triggers.

The joins are all outer joins anchored on MRP_FORECAST_UPDATES (FORUPD): UPDATE_SEQ_NUM matches MTL_DEMAND_OMOE.DEMAND_ID and LINE_NUM matches MTL_DEMAND_OMOE.USER_LINE_NUM. MTL_DEMAND_OMOE.DEMAND_SOURCE_LINE then relates to SO_LINES_ALL.LINE_ID, and SO_LINES_ALL.HEADER_ID relates to SO_HEADERS_ALL.HEADER_ID. Because these are (+) outer joins, forecast updates are preserved even when no matching demand or sales order line exists, which is essential for identifying unconsumed forecast entries.

Key Columns

  • SALES_ORDER_SCHEDULE_DATE — schedule date carried on the forecast update, reflecting the sales order demand date used for consumption.
  • SALES_ORDER_QUANTITY — the sales order quantity associated with the forecast update record.
  • FORECAST_UPDATE_DATE — the date the forecast update was processed.
  • UPDATE_QUANTITY — the quantity applied against the forecast by the update record.
  • DEMAND_CLASS — classification of the demand, used to segregate forecast consumption categories.
  • TRANSACTION_ID — identifier of the transaction tied to the forecast update, useful for traceability.
  • LINE_ID — the SO_LINES_ALL line identifier of the matched sales order line.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard audit columns reflecting the most recent change to the forecast update row.

Common Use Cases and Queries

The view is most often queried to reconcile forecast consumption against sales order schedules and to locate sales order lines for a given forecast update. A representative query retrieves recent consumption records for a demand class:

SELECT sales_order_schedule_date,
       sales_order_quantity,
       update_quantity,
       demand_class,
       transaction_id,
       line_id
FROM   apps.mrpbv_forecast_consumptions
WHERE  demand_class = :p_demand_class
AND    forecast_update_date >= :p_from_date;

Because the view is read-only, it is safe to embed in custom reports. Note that the ORGANIZATION_ID filter is applied via the internal security predicate ('_SEC:FORUPD.ORGANIZATION_ID' IS NOT NULL), so results are constrained by the operating unit/organization context of the session. When MTL_DEMAND_OMOE rows are absent, the outer join yields nulls for line and header attributes — a pattern frequently used to identify forecast updates that were never matched to order demand.