Results for “ahl_workorder_operations_v”

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

Overview

AHL_WORKORDER_OPERATIONS_V is a seeded Oracle E-Business Suite database view owned by the APPS schema, delivered as part of the AHL (Complex Maintenance Repair and Overhaul) product family. Its status is VALID in both EBS 12.1.1 and 12.2.2. The view presents work order operation details by joining AHL work order operation records to their associated Work in Process (WIP) operation records and to several supporting descriptive entities. In practice it acts as a consolidated read-only reporting layer over the transactional tables that store maintenance and repair work order operations, which makes it a convenient access point for operational reporting, concurrent programs, and downstream integrations that need operation-level granularity without assembling the joins manually.

The view exposes both the AHL operation identity (from AHL_WORKORDER_OPERATIONS) and the WIP execution identity (from WIP_OPERATIONS), so consumers can report on planned shop floor operations alongside their actual execution dates, status, and department assignment. Lookup meanings for operation type and status are resolved inside the view, removing the need for the caller to join FND_LOOKUP_VALUES_VL separately.

Underlying Base Objects

The view is defined as an outer-join query over six referenced objects identified in the ETRM metadata:

• AHL_WORKORDER_OPERATIONS (synonym) — the primary table, aliased WOP, supplying operation ID, sequence, type, status, actual dates, plan and collection references, and the DFF attribute columns.
• AHL_WORKORDERS (synonym) — aliased AWO, joined on WORKORDER_ID and used to bridge to the WIP entity.
• WIP_OPERATIONS (synonym) — aliased WIP, supplying the organization, WIP entity, department, first unit start and last unit completion dates, and description.
• BOM_DEPARTMENTS (synonym) — aliased BMD, providing department code and description.
• AHL_OPERATIONS_B_KFV (view) — aliased RMK, a key flexfield concatenation view supplying the operation's concatenated segments.
• FND_LOOKUP_VALUES_VL (view) — used twice, aliased OPTYPE and OPST, to resolve operation type and status lookup meanings.

The joins run from the AHL operation to its work order (inner), from the work order to the WIP operation via WIP_ENTITY_ID and sequence number (inner), and then outer joins to the operation KFF, department, and the two lookup views, so rows are not dropped when reference data is absent.

Key Columns

• WORKORDER_OPERATION_ID, WORKORDER_ID — the AHL operation and work order identifiers.
• WIP_ENTITY_ID, ORGANIZATION_ID — the WIP execution context.
• OPERATION_SEQUENCE_NUM — sequence of the operation on the work order.
• OPERATION_ID, CONCATENATED_SEGMENTS — the operation definition and its descriptive flexfield segments.
• OPERATION_TYPE_CODE/MEANING and STATUS_CODE/MEANING — coded values paired with their lookup meanings.
• DEPARTMENT_ID, DEPARTMENT_CODE, DESCRIPTION — the shop floor department performing the operation.
• FIRST_UNIT_START_DATE, LAST_UNIT_COMPLETION_DATE, ACTUAL_START_DATE, ACTUAL_END_DATE — planned versus actual execution timestamps, with hour and minute components split into separate character columns for reporting tools.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield columns carried through from the operation record.

Common Use Cases and Queries

Typical uses include work order operation status dashboards, department workload analysis, actual-versus-planned execution reporting, and interfaces that push operation data into external MES or maintenance systems.

SELECT WORKORDER_ID, OPERATION_SEQUENCE_NUM, CONCATENATED_SEGMENTS,
       MEANING_STATUS, DEPARTMENT_CODE, ACTUAL_START_DATE, ACTUAL_END_DATE
FROM   APPS.AHL_WORKORDER_OPERATIONS_V
WHERE  ORGANIZATION_ID = :org_id
AND    TRUNC(ACTUAL_START_DATE) >= TRUNC(SYSDATE) - 30;

Aggregating effort by department and operation type is equally straightforward, since the lookup meanings are already resolved:

SELECT DEPARTMENT_CODE, MEANING, COUNT(*)
FROM   APPS.AHL_WORKORDER_OPERATIONS_V
GROUP BY DEPARTMENT_CODE, MEANING;

Because the view is a simple projection without INSTEAD-OF triggers, it should be treated as read-only; any DML must target the underlying AHL_WORKORDER_OPERATIONS and WIP_OPERATIONS tables directly.