Results for “mrp_sales_order_updates”

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

Overview

The MRP_SALES_ORDER_UPDATES table resides in the MRP schema and belongs to the Master Scheduling/MRP product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to capture sales order changes that are consumed by the forecast consumption process. When a sales order is created, rescheduled, or modified in Order Management, the changes are recorded here so that the MRP planning engine can net firm demand against forecast entries and avoid double-counting demand.

From a Data Vault modeling perspective, this table is heuristic-classified as satellite-leaning. It is a child of the core demand record and stores descriptive change attributes keyed by a surrogate identifier, rather than acting as a hub of business entities. The table is owned by MRP, has status VALID, and contains 38 documented columns in the 12.2.2 physical schema.

Key Information Stored

The table is anchored by the surrogate primary key UPDATE_SEQ_NUM, which is also the only unique business-key candidate documented (MRP_SALES_ORDER_UPDATES_U1). Significant columns include:

• SALES_ORDER_ID — identifies the originating sales order demand line; joins to MTL_DEMAND.
• INVENTORY_ITEM_ID and ORGANIZATION_ID — the planned item and inventory organization context.
• NEW_SCHEDULE_DATE / OLD_SCHEDULE_DATE — the prior and revised schedule dates that drive forecast consumption.
• NEW_SCHEDULE_QUANTITY / OLD_SCHEDULE_QUANTITY — quantity changes between the old and new demand.
• CURRENT_CUSTOMER_ID / PREVIOUS_CUSTOMER_ID, CURRENT_SHIP_ID / PREVIOUS_SHIP_ID, CURRENT_BILL_ID / PREVIOUS_BILL_ID — before/after attributes identifying demand ownership shifts.
• CURRENT_DEMAND_CLASS / PREVIOUS_DEMAND_CLASS, CURRENT_TERRITORY_ID / PREVIOUS_TERRITORY_ID — classification changes used for grouping forecast consumption.
• BASE_MODEL_ID and ORDERED_ITEM_ID — model and configuration references for configured items.
• PROCESS_STATUS and ERROR_MESSAGE — outcome of processing the update record.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID — concurrent program context that generated the row.

Common Use Cases and Queries

Planners and developers use this table to audit why forecast consumption behaved as it did, and to reconcile sales order changes against the MRP plan. A typical query returns changes for a given organization and item over a date range:

• Select UPDATE_SEQ_NUM, SALES_ORDER_ID, NEW_SCHEDULE_DATE, OLD_SCHEDULE_DATE, NEW_SCHEDULE_QUANTITY, OLD_SCHEDULE_QUANTITY from MRP_SALES_ORDER_UPDATES where ORGANIZATION_ID and INVENTORY_ITEM_ID match the planning scope.
• Filter on PROCESS_STATUS to find rows that failed consumption and review ERROR_MESSAGE.
• Join to MRP_FORECAST_UPDATES on UPDATE_SEQ_NUM to trace consumption output downstream.
• Group by CURRENT_DEMAND_CLASS and CURRENT_TERRITORY_ID to report demand shifts by classification.

Related Objects

• MTL_DEMAND — joined via SALES_ORDER_ID; holds the authoritative demand record.
• MTL_SYSTEM_ITEMS_B — joined via INVENTORY_ITEM_ID and BASE_MODEL_ID for item and model attributes.
• MRP_PARAMETERS — joined via ORGANIZATION_ID for planning parameters.
• MRP_FORECAST_UPDATES — references this table via UPDATE_SEQ_NUM; carries consumption results.