Search Results eng_revised_operations




Overview
Explore in AI Chat

Overview

The ENG_REVISED_OPERATIONS table is a core data object within the Engineering (ENG) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It serves as the central repository for storing revised manufacturing operation details associated with an engineering change order (ECO). When an item's manufacturing routing is revised through an ECO, the new, pending, or historical operational steps are captured in this table. Its primary role is to maintain the integrity and revision history of manufacturing process data, enabling controlled changes to production methodologies before they are implemented in live production environments.

Key Information Stored

The table's structure is designed to define revised operations within the context of a specific engineering change. The documented primary and unique keys indicate the critical columns for data integrity. The OPERATION_SEQUENCE_ID is the primary identifier for each operation record. The combination of OPERATION_SEQUENCE_ID, ROUTING_SEQUENCE_ID, DEPARTMENT_ID, and OPERATION_TYPE enforces a unique constraint (UK1), ensuring no duplicate operational definitions exist for a given revision context. The foreign key column REVISED_ITEM_SEQUENCE_ID links the operation to its parent revised item record, establishing the core relationship within the engineering change structure.

Common Use Cases and Queries

This table is essential for reporting and validation during the engineering change management lifecycle. Common use cases include generating a bill of operations for a pending ECO, comparing revised operations against current routing steps to audit changes, and extracting data for integration with manufacturing execution systems. A typical query would join this table to ENG_REVISED_ITEMS to list all revised operations for a specific change order.

SELECT eri.CHANGE_NOTICE, eri.REVISED_ITEM_ID, ero.*
FROM ENG_REVISED_OPERATIONS ero,
     ENG_REVISED_ITEMS eri
WHERE ero.REVISED_ITEM_SEQUENCE_ID = eri.REVISED_ITEM_SEQUENCE_ID
AND eri.CHANGE_NOTICE = 'ECO12345';

Another common pattern is to query operations by department or operation type to analyze the impact of a change across manufacturing segments.

Related Objects

The table's primary documented relationship is a foreign key dependency to the ENG_REVISED_ITEMS table. This is a critical hierarchical link where revised operations roll up to a revised item, which in turn belongs to an engineering change order.

  • ENG_REVISED_ITEMS: The parent table. The join is made on the column ENG_REVISED_OPERATIONS.REVISED_ITEM_SEQUENCE_ID referencing the primary key of ENG_REVISED_ITEMS. This relationship ensures every revised operation is associated with a valid item revision.

While not explicitly listed in the provided metadata, this table is logically related to base tables like BOM_OPERATIONAL_ROUTINGS and, through ENG_REVISED_ITEMS, to ENG_ENGINEERING_CHANGES and the master item table, MTL_SYSTEM_ITEMS.