Results for “mrp_forecast_updates”

50+ results




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

Overview

MRP.MRP_FORECAST_UPDATES is a transactional history table within the Oracle E-Business Suite Master Scheduling/MRP module (MRP). It records forecast consumption activity — the events through which actual sales order demand reduces (consumes) forecasted demand within a planning horizon. Each row captures the details of a single consumption transaction, including the item, organization, forecast designator, the sales order that triggered the consumption, and the quantities involved. This table therefore serves as the auditable trail behind forecast consumption logic executed by the MRP planning engine and related scheduling processes.

The ETRM metadata classifies this object heuristically as a link table under Data Vault modeling conventions. This is a reasonable modeling suggestion: the table primarily records relationships and events joining inventory items, forecasts, sales orders, and date references, rather than acting as a durable business hub or a descriptive satellite. Practitioners designing downstream models may treat MRP_FORECAST_UPDATES as an associative/link structure rather than a source of slowly changing attributes.

Key Information Stored

The documented physical schema contains 24 columns. The most significant for analysis and joins are:

The surrogate primary key is TRANSACTION_ID. Business-key candidates for uniqueness are the composite of item, organization, designator, and sales order identifiers, though the documented metadata does not explicitly list a named unique index.

Common Use Cases and Queries

Typical uses include auditing forecast consumption, reconciling consumed versus remaining forecast, and diagnosing planning discrepancies. A representative query joins to the forecast item master:

  • Trace which sales orders consumed a given item's forecast: filter by INVENTORY_ITEM_ID, ORGANIZATION_ID, and FORECAST_DESIGNATOR, ordering by FORECAST_UPDATE_DATE.
  • Analyze consumption by customer using CUSTOMER_ID and DEMAND_CLASS.
  • Reconcile with billing by joining BILL_ID to IGS_FI_BILL_ALL.
  • Attribute rows to a concurrent program run via REQUEST_ID and PROGRAM_ID for run-level audits.

A sample pattern: SELECT f.INVENTORY_ITEM_ID, f.UPDATE_SALES_ORDER, f.UPDATE_QUANTITY FROM MRP.MRP_FORECAST_UPDATES f WHERE f.ORGANIZATION_ID = :org AND f.FORECAST_UPDATE_DATE >= :start_date ORDER BY f.FORECAST_UPDATE_DATE;

Related Objects

  • MRP_FORECAST_ITEMS — referenced via INVENTORY_ITEM_ID, ORGANIZATION_ID, FORECAST_DESIGNATOR.
  • MTL_SALES_ORDERS — referenced via UPDATE_SALES_ORDER.
  • MRP_FORECAST_DATES — referenced via TRANSACTION_ID.
  • MRP_SALES_ORDER_UPDATES — referenced via UPDATE_SEQ_NUM.
  • IGS_FI_BILL_ALL — referenced via BILL_ID.

Together these relationships position MRP_FORECAST_UPDATES as the historical junction between forecast definitions and the sales order demand that consumes them.