Search Results eng_change_order_revisions_uk1

Overview

The ENG_CHANGE_ORDER_REVISIONS table is a core data object within the Oracle E-Business Suite (EBS) Engineering (ENG) module, specifically for versions 12.1.1 and 12.2.2. It serves as the master repository for managing revision identifiers associated with Engineering Change Orders (ECOs). An ECO is a formal document that authorizes and tracks modifications to a product's design, bill of materials, or manufacturing process. This table is critical for maintaining a precise and auditable history of all revision levels assigned to items as they are altered through the change management lifecycle. Its role is to establish and enforce the relationship between a specific change notice, the implementing organization, and the unique revision identifier.

Key Information Stored

The table's structure is designed to uniquely define a revision within the context of a specific change order and organization. The primary columns, as defined by its constraints, are fundamental. The REVISION_ID column is the table's unique primary key (ENG_CHANGE_ORDER_REVISIONS_PK). The combination of CHANGE_NOTICE, ORGANIZATION_ID, and REVISION forms a unique key (ENG_CHANGE_ORDER_REVISIONS_UK1), ensuring that a given revision level cannot be duplicated for the same change order within the same business unit. This structure explicitly links a revision (e.g., 'B', 'C', '02') to the specific ECO document (CHANGE_NOTICE) that authorized it for a particular inventory organization.

Common Use Cases and Queries

This table is central to queries that trace the revision history of an item or validate change order data. A common reporting use case involves listing all revisions created by a specific ECO to understand the full scope of a change. For integration or data validation, a typical query would join this table to the item master (MTL_SYSTEM_ITEMS_B) via revision-specific interfaces. For example, to find all items and their new revision created by a change notice 'ECO1001' in organization 204, one might use a query pattern that joins ENG_CHANGE_ORDER_REVISIONS (ECOR) to ENG_ENGINEERING_CHANGES (EEC) on CHANGE_NOTICE and ORGANIZATION_ID, and then to item revision tables. It is also frequently referenced in workflows that automatically assign the next sequential revision when an engineer submits a change.

Related Objects

The table has defined foreign key relationships that anchor it within the Engineering schema. Its primary relationship is with the ENG_ENGINEERING_CHANGES table, which stores the header information for the change order itself. The foreign key on CHANGE_NOTICE and ORGANIZATION_ID enforces that a revision record cannot exist without a valid parent ECO. In practice, this table is closely linked to item revision control tables in the Inventory (INV) and Bills of Material (BOM) modules, such as MTL_ITEM_REVISIONS_B and BOM_BILL_OF_MATERIALS. Business logic and data validation involving this table are often encapsulated within Engineering and Inventory APIs, which should be preferred over direct DML for any application integration.