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:
- TRANSACTION_ID — Surrogate/transaction identifier; also a foreign key to
MRP_FORECAST_DATES, anchoring the row to a forecast date reference. - INVENTORY_ITEM_ID, ORGANIZATION_ID, FORECAST_DESIGNATOR — Composite foreign key to
MRP_FORECAST_ITEMS; together these identify which forecast (item, org, designator) was consumed. - UPDATE_SALES_ORDER — Foreign key to
MTL_SALES_ORDERS; identifies the order driving consumption. - UPDATE_SEQ_NUM — Foreign key to
MRP_SALES_ORDER_UPDATES; sequences the update event. - BILL_ID — Foreign key to
IGS_FI_BILL_ALL; links the consumption to billing information where applicable. - CUSTOMER_ID and SHIP_ID — Identify the customer and ship-to associated with the consuming demand.
- SALES_ORDER_QUANTITY and UPDATE_QUANTITY — Quantities consumed by the sales order and the net update amount.
- SALES_ORDER_SCHEDULE_DATE and FORECAST_UPDATE_DATE — The schedule date of the consuming order line and the date the forecast was updated.
- DEMAND_CLASS — Classifies the demand stream used during consumption logic.
- LINE_NUM — Sales order line reference.
- CREATION_DATE, LAST_UPDATE_DATE, and audit columns (CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) — Standard EBS WHO-column audit trail.
- REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — Concurrent program context identifying the report/process that generated the row.
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, andFORECAST_DESIGNATOR, ordering byFORECAST_UPDATE_DATE. - Analyze consumption by customer using
CUSTOMER_IDandDEMAND_CLASS. - Reconcile with billing by joining
BILL_IDtoIGS_FI_BILL_ALL. - Attribute rows to a concurrent program run via
REQUEST_IDandPROGRAM_IDfor 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 viaINVENTORY_ITEM_ID,ORGANIZATION_ID,FORECAST_DESIGNATOR.MTL_SALES_ORDERS— referenced viaUPDATE_SALES_ORDER.MRP_FORECAST_DATES— referenced viaTRANSACTION_ID.MRP_SALES_ORDER_UPDATES— referenced viaUPDATE_SEQ_NUM.IGS_FI_BILL_ALL— referenced viaBILL_ID.
Together these relationships position MRP_FORECAST_UPDATES as the historical junction between forecast definitions and the sales order demand that consumes them.
-
Forecast consumption transaction history
-
Forecast consumption transaction history
-
APPS.MRPFV_FORECAST_CONSUMPTIONS·↳ INV_DECIMALS_PUB·↳ INV_SALESORDER·↳ MRP_FORECAST_UPDATES·Explore MRP module →
-
APPS.MRPBV_FORECAST_CONSUMPTIONS·↳ INV_DECIMALS_PUB·↳ INV_SALESORDER·↳ MRP_FORECAST_UPDATES·Explore MRP module →
-
APPS.MRPBV_FORECAST_CONSUMPTIONS·↳ INV_DECIMALS_PUB·↳ INV_SALESORDER·↳ MRP_FORECAST_UPDATES·Explore MRP module →
-
Forecast Consumptions View
APPS.ICX_MRP_FORECAST_UPDATES_V·↳ MRP_FORECAST_UPDATES·↳ MTL_SALES_ORDERS·Explore ICX module →
-
APPS.MRPFV_FORECAST_CONSUMPTIONS·↳ INV_DECIMALS_PUB·↳ INV_SALESORDER·↳ MRP_FORECAST_UPDATES·Explore MRP module →
-
Forecast Consumptions View
APPS.ICX_MRP_FORECAST_UPDATES_V·↳ MRP_FORECAST_UPDATES·↳ MTL_SALES_ORDERS·Explore ICX module →
-
View: MRP_FORECAST_UPDATES_V 12.2.2
Forecast consumption transaction history view
APPS.MRP_FORECAST_UPDATES_V·↳ HZ_CUST_ACCOUNTS·↳ HZ_CUST_ACCT_SITES·↳ HZ_CUST_SITE_USES·Explore MRP module →
-
View: MRP_FORECAST_UPDATES_V 12.1.1
Forecast consumption transaction history view
APPS.MRP_FORECAST_UPDATES_V·↳ HZ_CUST_ACCOUNTS·↳ HZ_CUST_ACCT_SITES·↳ HZ_CUST_SITE_USES·Explore MRP module →
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2