Results for “ahl_operations_h_b”

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

Overview

In Oracle E-Business Suite 12.1.1 and 12.2.2, AHL.AHL_OPERATIONS_H_B is a table within the AHL product family, Complex Maintenance Repair and Overhaul. As its name and documentation indicate, it is the history (or revision) table for the base operations table AHL_OPERATIONS_B. Whereas the base table holds the current definition of maintenance and repair operations used in complex MRO routing and work definition, AHL_OPERATIONS_H_B preserves prior or alternate revisions of those operations, allowing the application to retain a versioned audit trail of an operation's configuration over time. The "_H_" designation is the conventional EBS pattern denoting a history or version-enabled companion table to a "_B_" base table. The table is owned by the AHL schema and is marked VALID in the data dictionary.

The metadata carries a heuristic Data Vault classification of satellite-leaning. This is a modeling suggestion rather than an enforced classification: it reflects that the table attaches descriptive, time-stamped attribute columns (revision status, active dates, business attributes) around a key, which is the behavior of a Data Vault satellite. Note that the table also references both an operation parent and a security group, giving it some link-like characteristics, so the satellite classification should be treated as guidance only.

Key Information Stored

Physically the table documents 53 columns. The most significant, per the ETRM schema, include the following:

• OPERATIONS_H_ID — the surrogate primary key, enforced by AHL_OPERATIONS_H_B_PK and additionally covered by unique index AHL_OPERATIONS_H_B_U1, making it the primary business-key candidate at the AHL level.
• OPERATION_ID — foreign key to the base table AHL_OPERATIONS_B, identifying which base operation this history row versions.
• REVISION_NUMBER and REVISION_STATUS_CODE — the revision sequence and its lifecycle state.
• ACTIVE_START_DATE / ACTIVE_END_DATE — the effective dating window of the revision.
• OPERATION_NUMBER — the human-readable operation identifier.
• SEGMENT1 through SEGMENT7 — the flexible key segments (Key Flexfield) that qualify the operation.
• OPERATION_TYPE_CODE, OPERATION_CATEGORY_CODE, PRODUCT_TYPE_CODE, ZONE_CODE, SUB_ZONE_CODE, WORK_CENTER_CODE — classification and routing attributes.
• PROCESS_CODE and OPERATOR_CODE / OPERATOR_PARTY_ID — process and responsible-operator identification.
• TIME_SPAN — the planned duration associated with the operation revision.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, governing multi-org / data-security visibility.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the descriptive flexfield (DFF) columns for customer-extended data.
• Standard WHO audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER for optimistic locking.

Common Use Cases and Queries

Because this is a history table, its principal uses are audit, revision comparison, and point-in-time reporting. A typical query joins the history rows back to the base operation to reconcile present versus prior configuration:

SELECT h.OPERATION_ID, h.REVISION_NUMBER, h.REVISION_STATUS_CODE,
       h.ACTIVE_START_DATE, h.ACTIVE_END_DATE, h.OPERATION_NUMBER
 FROM AHL.AHL_OPERATIONS_H_B h
 WHERE h.OPERATION_ID = :operation_id
 ORDER BY h.REVISION_NUMBER DESC;

Reporting scenarios include reconstructing an operation's state as of a given date using the ACTIVE_START_DATE/ACTIVE_END_DATE range, and auditing revision-status transitions. Retrieving the translated revision text requires joining AHL_OPERATIONS_H_TL on OPERATIONS_H_ID. Security-scoped extracts filter by SECURITY_GROUP_ID for responsibility-based access.

Related Objects

• AHL_OPERATIONS_B — the base/current operations table; joined on this table's OPERATION_ID foreign key.
• AHL_OPERATIONS_H_TL — the translation table for this history entity; it references AHL_OPERATIONS_H_B via OPERATIONS_H_ID as a foreign key.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID to enforce data-security grouping.
• The primary key object AHL_OPERATIONS_H_B_PK and unique index AHL_OPERATIONS_H_B_U1, which together define the row identity used by dependent objects.

Collectively these relationships confirm that AHL_OPERATIONS_H_B functions as the versioned companion to the base operation definition, anchored by OPERATIONS_H_ID and consumed primarily through its translation table and its parent operation record.