Results for “operation_phase_id”
22 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
Within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment, AHL_OPERATION_PHASES_H is a history table residing in the AHL schema (Complex Maintenance Repair and Overhaul product). Its functional purpose is to retain the full historical revision trail for records held in the base table AHL_OPERATION_PHASES. Every row represents a prior state of an operation phase record, enabling the audit of how a phase definition changed over time, including the operative revision number and all descriptive flexfield attribute values that were in effect at the time of the snapshot.
From a data-modelling perspective, the ETRM metadata classifies this object heuristically as a link entity in Data Vault terms. This reflects its role in resolving relationships — it carries the surrogate association between the parent operation phase (OPERATION_PHASE_ID → AHL_OPERATION_PHASES) and the parent operation header (OPERATION_ID → AHL_OPERATIONS_B) while preserving the point-in-time history of that relationship via the OBJECT_VERSION_NUMBER and REVISION_NUMBER columns. This classification is offered as a modelling suggestion rather than an enforced schema rule.
Key Information Stored
The table is documented with 28 columns in the 12.2.2 physical schema. The most significant columns fall into three groups:
- OPERATION_PHASES_H_ID — the surrogate primary key, enforced by index
AHL_OPERATION_PHASES_H_PKand also backed by unique indexAHL_OPERATION_PHASES_H_U1. This is the business-key candidate documented for the object. - OPERATION_PHASE_ID — the foreign key to the base table
AHL_OPERATION_PHASES, linking each historical row back to its current-version counterpart. - OPERATION_ID — the foreign key to
AHL_OPERATIONS_B, identifying the parent operation to which the phase belongs. - PHASE_CODE — the coded identifier describing the phase stage.
- REVISION_NUMBER — the revision snapshot identifier that distinguishes successive historical versions.
- OBJECT_VERSION_NUMBER — the optimistic locking counter maintained through the Oracle Application Object Library framework.
- SECURITY_GROUP_ID — foreign key to
FND_SECURITY_GROUPS, governing row-level access. - LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO columns recording who created and last modified each row and when.
- ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the descriptive flexfield (DFF) segments, capturing any customer-defined context stored against the phase at the time of the snapshot.
Common Use Cases and Queries
The principal use case is audit and change-tracking: auditors and maintenance engineers query this table to establish what a given phase looked like before a modification. A typical join retrieves the revision history of a phase:
SELECT h.operation_phase_id, h.phase_code, h.revision_number,
h.last_update_date, h.last_updated_by
FROM ahl.ahl_operation_phases_h h
WHERE h.operation_id = :p_operation_id
ORDER BY h.revision_number DESC;
A second pattern correlates each history row to its current record to detect divergence:
SELECT p.operation_phase_id, p.phase_code AS current_code,
h.phase_code AS historic_code, h.revision_number
FROM ahl.ahl_operation_phases p,
ahl.ahl_operation_phases_h h
WHERE h.operation_phase_id = p.operation_phase_id
AND h.operation_id = :p_operation_id;
Reporting use cases include revision-count analyses per operation, DFF-driven extracts for regulatory compliance, and security-group–scoped audits for multi-org deployments.
Related Objects
- AHL_OPERATION_PHASES — the base (current) table joined on
OPERATION_PHASE_ID; history rows mirror this table's structure. - AHL_OPERATIONS_B — the operation header table joined on
OPERATION_ID; defines the parent operation context. - FND_SECURITY_GROUPS — joined on
SECURITY_GROUP_IDfor row-level security resolution. - AHL_OPERATION_PHASES_H_PK / _U1 — the primary key and unique index supporting
OPERATION_PHASES_H_ID. - Standard Oracle WHO/DFF infrastructure tables referenced indirectly through the
ATTRIBUTEand audit columns.
-
History table for AHL_OPERATION_PHASES.
-
View: AHL_OPERATION_PHASES_V 12.2.2
View based on the table AHL_OPERATION_PHASES and the view FND_LOOKUP_VALUES_VL to include all the corresponding descriptions of the codes.
APPS.AHL_OPERATION_PHASES_V·↳ AHL_OPERATION_PHASES·↳ FND_LOOKUP_VALUES_VL·Explore AHL module →
-
This table stores the significant phases in an Operation.
-
View: AHL_OPERATION_PHASES_V 12.1.1
View based on the table AHL_OPERATION_PHASES and the view FND_LOOKUP_VALUES_VL to include all the corresponding descriptions of the codes.
APPS.AHL_OPERATION_PHASES_V·↳ AHL_OPERATION_PHASES·↳ FND_LOOKUP_VALUES_VL·Explore AHL module →
-
This table stores the significant phases in an Operation.
-
History table for AHL_OPERATION_PHASES.
-
eTRM - AHL Tables and Views 12.1.1
Ahl Production Workorder Operations Information stored in this table
-
eTRM - AHL Tables and Views 12.1.1
Ahl Production Workorder Operations Information stored in this table
-
eTRM - AHL Tables and Views 12.2.2
Ahl Production Workorder Operations Information stored in this table
-
eTRM - AHL Tables and Views 12.2.2
Ahl Production Workorder Operations Information stored in this table