Search Results include_in_rollup

Overview

ENG_REVISED_OPERATIONS is an Engineering (ENG) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the operation-level detail of engineering-revised routings. Where ENG_REVISED_ITEMS captures revised item and routing header information, ENG_REVISED_OPERATIONS holds the individual operations that belong to those revised routings — the sequence of steps, their associated departments, standard operation references, effectivity windows, planning percentages, and computed time values. The table is central to the Engineering Change Order (ECO) and revised routing workflow, allowing engineering to model proposed changes to manufacturing operations before they are released to production.

Under a heuristic Data Vault classification mined from its foreign-key structure, the table leans toward the satellite pattern: it carries descriptive, time-stamped attributes (LAST_UPDATE_DATE, CREATION_DATE, EFFECTIVITY_DATE, DISABLE_DATE) attached to a parent hub-like entity (the revised item/routing) rather than acting as a pure hub or a link between two hubs. This is a modeling suggestion only; natively the object is a standard Oracle EBS transactional detail table.

Key Information Stored

The surrogate primary key is OPERATION_SEQUENCE_ID, defined by the constraint ENG_REVISED_OPERATIONS_PK. A secondary unique key, ENG_REVISED_OPERATIONS_UK1, combines OPERATION_SEQUENCE_ID, ROUTING_SEQUENCE_ID, DEPARTMENT_ID, and OPERATION_TYPE — these columns therefore act as business-key candidates for identifying a distinct operation within a routing.

The most significant columns include:

• OPERATION_SEQUENCE_ID — surrogate primary key and unique identifier for the operation.
• ROUTING_SEQUENCE_ID — links the operation to its parent revised routing.
• REVISED_ITEM_SEQUENCE_ID — foreign key to ENG_REVISED_ITEMS, tying the operation to the revised item.
• STANDARD_OPERATION_ID — foreign key to WSM_OPERATION_DETAILS, the standard operation referenced.
• DEPARTMENT_ID — foreign key to BOM_DEPARTMENTS, the performing department.
• OPERATION_SEQ_NUM — the displayed sequence number of the operation.
• OPERATION_TYPE — classification of the operation.
• EFFECTIVITY_DATE / DISABLE_DATE — the effective window for the operation.
• OPERATION_DESCRIPTION — free-text description of the operation.
• BACKFLUSH_FLAG, COUNT_POINT_TYPE, OPTION_DEPENDENT_FLAG — manufacturing control flags.
• YIELD, CUMULATIVE_YIELD, REVERSE_CUMULATIVE_YIELD — yield metrics across the routing.
• LABOR_TIME_CALC, MACHINE_TIME_CALC, TOTAL_TIME_CALC and their *_USER counterparts — calculated versus user-entered time values.
• MINIMUM_TRANSFER_QUANTITY, NET_PLANNING_PERCENT, OPERATION_LEAD_TIME_PERCENT — planning attributes.
• CHANGE_NOTICE, IMPLEMENTATION_DATE, ECO_FOR_PRODUCTION — ECO linkage and production-release flags.

Standard EBS audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the fifteen ATTRIBUTE flex columns are also present.

Common Use Cases and Queries

Typical uses include retrieving the operations of a revised routing, comparing proposed versus current operation times, and reporting on ECO-driven routing changes.

SELECT operation_sequence_id, operation_seq_num, department_id,
       operation_description, yield, total_time_calc
FROM   eng_revised_operations
WHERE  revised_item_sequence_id = :revised_item_seq_id
ORDER BY operation_seq_num;

SELECT o.operation_seq_num, o.operation_description,
       d.department_code, o.total_time_user
FROM   eng_revised_operations o,
       bom_departments d
WHERE  o.department_id = d.department_id
AND    o.routing_sequence_id = :routing_seq_id;

Related Objects

• ENG_REVISED_ITEMS — parent revised item; join on ENG_REVISED_OPERATIONS.REVISED_ITEM_SEQUENCE_ID = ENG_REVISED_ITEMS.REVISED_ITEM_SEQUENCE_ID.
• WSM_OPERATION_DETAILS — standard operation reference via STANDARD_OPERATION_ID.
• BOM_DEPARTMENTS — performing department via DEPARTMENT_ID.
• ENG_REVISED_OPERATION_RESOURCES / ENG_REVISED_OPERATION_RSC — child resource requirements per revised operation.
• ENG_REVISED_OPERATIONS_UK1 — unique constraint used to resolve a specific operation by routing, department, and type.
• BOM_OPERATION_SEQUENCES — the released production routing counterpart used for comparison during ECO propagation.

Because the table carries process/program audit columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID), it is typically populated by concurrent engineering programs rather than directly by end users.