Search Results update_seq_num




Overview
Explore in AI Chat

Overview

The MRP_SALES_ORDER_UPDATES table is a core transactional entity within the Oracle E-Business Suite (EBS) Master Scheduling/MRP module. It serves as a critical staging and tracking table for sales order modifications that directly impact the forecast consumption process. When a sales order is created, changed, or deleted, relevant details are recorded in this table. These records are subsequently processed by the Master Scheduling and MRP engines to accurately consume the forecast, ensuring that production and procurement plans reflect real customer demand and preventing double-counting between forecasts and firm orders. Its role is integral to maintaining the integrity of the demand planning and supply planning functions in releases 12.1.1 and 12.2.2.

Key Information Stored

The table captures a snapshot of the sales order change for consumption logic. While the full column list is not detailed in the provided metadata, the primary and foreign key relationships reveal essential data points. The primary key, UPDATE_SEQ_NUM, uniquely identifies each change record. Critical foreign keys include SALES_ORDER_ID, linking to the demand source in MTL_DEMAND; ORGANIZATION_ID, linking to MRP_PARAMETERS for organizational context; INVENTORY_ITEM_ID, identifying the specific item changed; and BASE_MODEL_ID, which may link to a model item for configuration or option class forecasting. The table likely also holds columns for the transaction type (e.g., new order, update, cancellation), changed quantity, schedule date, and a processed flag.

Common Use Cases and Queries

The primary use case is the automated forecast consumption process during a Master Schedule or MRP run. Planners may also query this table to audit consumption history or troubleshoot planning discrepancies. Common SQL patterns involve joining to item and demand tables to analyze changes. For example, to find unprocessed sales order updates for a specific organization, a query might filter on a PROCESSED_FLAG and join to MTL_SYSTEM_ITEMS_B. Another typical query would trace the consumption impact of a specific sales order line by joining MRP_SALES_ORDER_UPDATES to MRP_FORECAST_UPDATES via the UPDATE_SEQ_NUM to see which forecast records were consumed.

Related Objects

  • MRP_FORECAST_UPDATES: Has a foreign key relationship to this table on UPDATE_SEQ_NUM. This links the sales order change to the corresponding forecast consumption transaction.
  • MTL_DEMAND: Foreign key from MRP_SALES_ORDER_UPDATES.SALES_ORDER_ID. This relates the update record to the original sales order demand detail.
  • MRP_PARAMETERS: Foreign key from MRP_SALES_ORDER_UPDATES.ORGANIZATION_ID. Provides organizational planning parameters.
  • MTL_SYSTEM_ITEMS_B: Has two foreign key relationships. One on (BASE_MODEL_ID, ORGANIZATION_ID) for model-level tracking, and another on (INVENTORY_ITEM_ID, ORGANIZATION_ID) for the specific item changed.