Search Results mrp_pending_eng_changes




Overview
Explore in AI Chat

Overview

The MRP_PENDING_ENG_CHANGES table is a data structure within the Oracle E-Business Suite (EBS) Master Scheduling/MRP (MRP) module. Its intended purpose is to serve as a staging or tracking repository for Engineering Change Notices (ECNs) that are pending implementation and require consideration during the Material Requirements Planning (MRP) compilation process. The table's design facilitates the integration of engineering change management with production planning by linking pending changes to specific items, organizations, and MRP compile designators. However, as explicitly noted in the official ETRM documentation for both versions 12.1.1 and 12.2.2, this table is marked with the status "Not currently used." This indicates that while the table schema exists within the MRP schema, its associated application logic may be inactive, deprecated, or reserved for future functionality.

Key Information Stored

The table's structure is defined to hold key identifiers that link engineering changes to the planning system. The primary key is the ECN_ID. Critical foreign key columns establish relationships with core inventory and engineering entities. These include INVENTORY_ITEM_ID and ORGANIZATION_ID, which link to the MRP_SYSTEM_ITEMS table to identify the item affected by the change. The CHANGE_NOTICE and ORGANIZATION_ID columns reference the ENG_ENGINEERING_CHANGES table to identify the specific engineering change order. The COMPILE_DESIGNATOR column specifies which MRP plan the pending change is associated with. Additional columns such as ENG_CHANGE_USING_ASSY_ID and DRIVING_ITEM_ID, also foreign keys to MRP_SYSTEM_ITEMS, suggest the table was designed to handle complex change scenarios involving parent items or specific components driving the change requirement.

Common Use Cases and Queries

Given the documented "Not currently used" status, there are no active standard application use cases for this table in Oracle EBS 12.1.1 or 12.2.2. It is not populated or maintained by standard MRP or Engineering processes. Consequently, no standard reports or application screens utilize this data. If the table were active, its primary use case would be to query pending engineering changes for a specific MRP plan to assess their impact on material plans. A theoretical query pattern, based on its structure, might involve joining to ENG_ENGINEERING_CHANGES for change details and MRP_SYSTEM_ITEMS for item information.

SELECT pec.change_notice,
       msi.concatenated_segments item,
       pec.compile_designator
FROM mrp_pending_eng_changes pec,
     mrp_system_items msi
WHERE pec.inventory_item_id = msi.inventory_item_id
  AND pec.organization_id   = msi.organization_id
  AND pec.compile_designator = '<PLAN_NAME>';

Related Objects

The table's schema defines explicit foreign key relationships with other core EBS tables, as documented in the ETRM metadata. These relationships clarify its intended integration points even in its unused state.

  • Primary Key: MRP_PENDING_ENG_CHANGES_PK (ECN_ID)
  • Foreign Key to MRP_SYSTEM_ITEMS: Links via (INVENTORY_ITEM_ID, ORGANIZATION_ID, COMPILE_DESIGNATOR) to identify the planned item subject to the change.
  • Foreign Key to ENG_ENGINEERING_CHANGES: Links via (CHANGE_NOTICE, ORGANIZATION_ID) to the master engineering change order.
  • Foreign Key to MRP_SYSTEM_ITEMS: Links via (ENG_CHANGE_USING_ASSY_ID, ORGANIZATION_ID, COMPILE_DESIGNATOR) potentially to a parent assembly using the changed item.
  • Foreign Key to MRP_SYSTEM_ITEMS: Links via (DRIVING_ITEM_ID, ORGANIZATION_ID, COMPILE_DESIGNATOR) potentially to a component that is the driver for the change.