Results for “mrp_forecast_updates_v”

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

Overview

MRP_FORECAST_UPDATES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the MRP (Master Scheduling/MRP) product family. Its documented purpose is to expose forecast consumption transaction history, that is, the record of how forecast demand was relieved by actual sales order demand during the planning cycle. In EBS 12.1.1 and 12.2.2 the object carries a VALID status and is routinely surfaced in custom reports, Oracle Discoverer workbooks, and BI Publisher data templates that need to reconcile forecast versus actual demand. The view is read-only by design; it denormalizes several transactional and master tables so that planners and integration developers can obtain a single-row-per-transaction picture of forecast updates without writing multi-table joins themselves.

For users searching on the identifier "update_sales_order," the relevant point is that UPDATE_SALES_ORDER is a column exposed directly by this view, not a procedure or API. It represents the sales order number associated with the forecast update transaction. This distinction matters because it is frequently mistaken for a callable routine in customization work.

Underlying Base Objects

The view is defined over MRP_FORECAST_UPDATES, which is the driving transactional table and the source of the primary key columns including TRANSACTION_ID and ROW_ID. It is joined to MRP_SALES_ORDER_UPDATES via M.UPDATE_SEQ_NUM = MSOU.SALES_ORDER_ID, and to OE_ORDER_LINES_ALL via M.UPDATE_SEQ_NUM = DEM.LINE_ID, to resolve the sales order line context for each update.

Customer and address information is supplied through the Trading Community Architecture (TCA) and Receivables objects: HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES, HZ_LOCATIONS, HZ_PARTIES, and HZ_PARTY_SITES. In the documented 12.2.2 metadata the RA_CUSTOMERS_VIEW, RA_SITE_USES, and RA_ADDRESSES references of earlier releases are resolved through these TCA synonyms. All joins to the customer, ship-to, and bill-to objects are outer joins, so a forecast update row is retained even when customer or address data is missing.

Key Columns

• TRANSACTION_ID, ROW_ID — primary identifier of the forecast update record in MRP_FORECAST_UPDATES.
• INVENTORY_ITEM_ID, ORGANIZATION_ID — planned item and inventory organization.
• FORECAST_DESIGNATOR — the forecast set against which consumption occurred.
• UPDATE_SALES_ORDER — sales order number driving the forecast update.
• SALES_ORDER_SCHEDULE_DATE, FORECAST_UPDATE_DATE — schedule and consumption dates used for period analysis.
• SALES_ORDER_QUANTITY, UPDATE_QUANTITY, DEMAND_CLASS — demand quantities and the demand class used in planning.
• SALES_ORDER_ITEM_ID, SALES_ORDER_ITEM_ID2 — item identifiers resolved from MRP_SALES_ORDER_UPDATES and OE_ORDER_LINES_ALL respectively.
• CUSTOMER_ID, CUSTOMER_NAME, SHIP_ID, SHIP_ADDRESS, BILL_ID, BILL_ADDRESS — customer and address attributes from TCA.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns identifying the process that created the row.

Common Use Cases and Queries

Typical scenarios include auditing forecast consumption, tracing which sales orders relieved a forecast, and reconciling forecast versus booked demand by customer or item.

• List recent forecast updates with their sales order and quantity.
• Summarize consumed quantity by item and organization.
• Report forecast consumption by customer for demand planning reviews.

Sample SQL:

SELECT transaction_id, forecast_designator, update_sales_order, inventory_item_id, organization_id, sales_order_quantity, update_quantity, forecast_update_date FROM apps.mrp_forecast_updates_v WHERE update_sales_order IS NOT NULL ORDER BY forecast_update_date DESC;

SELECT inventory_item_id, organization_id, SUM(update_quantity) consumed_qty FROM apps.mrp_forecast_updates_v WHERE forecast_update_date >= SYSDATE - 30 GROUP BY inventory_item_id, organization_id;