Results for “operation_sequence_num”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AHL_WORKORDER_OPERATIONS is a core transactional table in the Oracle E-Business Suite product AHL — Complex Maintenance Repair and Overhaul (CMRO). It stores work order operation information, representing the individual operations that must be executed against a work order in order to complete a maintenance, repair, or overhaul task. In the CMRO execution model, an operation is a discrete unit of work — such as a disassembly step, an inspection, a repair action, or a reassembly step — sequenced within a work order and associated with resources, materials, and transactions.

The table is owned by the AHL schema and is valid in both EBS 12.1.1 and 12.2.2. The documented physical schema at 12.2.2 contains 33 columns. Under the heuristic Data Vault classification mined from the foreign-key structure, this object is best modeled as a hub: its primary key, WORKORDER_OPERATION_ID, is referenced by multiple dependent tables (resources, part changes, scheduled materials, material transactions, and operation transactions), making it the central business entity around which those satellites and links are organized.

Key Information Stored

The documented structure distinguishes the surrogate primary key from the business-key candidates:

• WORKORDER_OPERATION_ID — surrogate primary key, enforced by AHL_WORKORDER_OPERATIONS_PK1 and by the unique index AHL_WORKORDER_OPERATIONS_U2.
• WORKORDER_ID — foreign key to AHL_WORKORDERS; identifies the parent work order to which the operation belongs.
• OPERATION_ID — foreign key to AHL_OPERATIONS_B; identifies the operation definition being performed.
• OPERATION_SEQUENCE_NUM — the ordering of the operation within the work order. Together with WORKORDER_ID, this forms the business-key candidate enforced by the unique index AHL_WORKORDER_OPERATIONS_U1.
• STATUS_CODE — the lifecycle status of the operation (for example, pending, in progress, or complete).
• OPERATION_TYPE_CODE — classifies the nature of the operation.
• PLAN_ID and COLLECTION_ID — associate the operation with its originating maintenance plan or collection context.
• ACTUAL_START_DATE and ACTUAL_END_DATE — capture actual execution start and completion timestamps, supporting variance and duration reporting.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting data security and access partitioning.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — standard concurrent-program and audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS extensibility flexfield columns.

Common Use Cases and Queries

This table is typically queried when reporting work order progress, sequencing operations, or tracing resources and materials consumed at the operation level. A common pattern joins operations to their parent work order:

SELECT wo.WORKORDER_ID, wo.OPERATION_SEQUENCE_NUM, wo.STATUS_CODE,
       wo.ACTUAL_START_DATE, wo.ACTUAL_END_DATE
FROM AHL.AHL_WORKORDER_OPERATIONS wo
WHERE wo.WORKORDER_ID = :p_workorder_id
ORDER BY wo.OPERATION_SEQUENCE_NUM;

Resource consumption is retrieved by joining to AHL_OPERATION_RESOURCES on WORKORDER_OPERATION_ID. Material movement and part-change history are retrieved through AHL_WORKORDER_MTL_TXNS, AHL_SCHEDULE_MATERIALS, and AHL_PART_CHANGES, all keyed by the same column. Operation-level transaction history is available in AHL_WO_OPERATIONS_TXNS. Typical reporting includes operation status summaries by work order, duration analysis comparing actual start and end dates, resource utilization by operation, and material consumption reporting for a given maintenance event.

Related Objects

• AHL_WORKORDERS — parent work order; joined via WORKORDER_ID.
• AHL_OPERATIONS_B — operation definition; joined via OPERATION_ID.
• AHL_OPERATION_RESOURCES — resources assigned to the operation; references WORKORDER_OPERATION_ID.
• AHL_PART_CHANGES — part replacement and change history per operation.
• AHL_SCHEDULE_MATERIALS — material requirements scheduled against the operation.
• AHL_WORKORDER_MTL_TXNS — material transactions posted for the operation.
• AHL_WO_OPERATIONS_TXNS — transaction history at the operation level.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for row-level security.