Search Results ahl_uc_headers_h




Overview
Explore in AI Chat

Overview

The AHL_UC_HEADERS_H table is a critical history table within the Oracle E-Business Suite's Complex Maintenance, Repair, and Overhaul (AHL) module. Its primary function is to maintain a historical record of all changes made to unit configuration headers, which are master records defining the structure and composition of a configurable asset or unit. This table works in conjunction with the base table, AHL_UNIT_CONFIG_HEADERS, to provide a complete audit trail. By capturing each version of a unit configuration, it enables compliance, traceability, and analysis of how an asset's configuration has evolved over its lifecycle, which is a fundamental requirement in regulated industries like aviation, defense, and heavy machinery.

Key Information Stored

The table stores a complete snapshot of a unit configuration header for each version. Its structure is defined by a composite primary key consisting of UNIT_CONFIG_HEADER_ID and VERSION_NO. The UNIT_CONFIG_HEADER_ID links the historical record back to the primary key in the AHL_UNIT_CONFIG_HEADERS table. The VERSION_NO sequentially tracks each change. Other essential foreign key columns include MASTER_CONFIG_ID, which references the master configuration template (AHL_MC_HEADERS_B) the unit is based upon, and CSI_ITEM_INSTANCE_ID, which links to the specific serialized item instance in the CSI (Common Service Item) module. The PARENT_UC_HEADER_ID column establishes hierarchical relationships between unit configurations. The table will also contain all other descriptive and control columns from the base header table, such as configuration name, status, dates, and revision details, as they existed at the time each version was created.

Common Use Cases and Queries

The primary use case is auditing and reporting on the change history of asset configurations. This is vital for understanding the "as-maintained" state of an asset at any point in time, supporting maintenance investigations, regulatory audits, and warranty claims. A common query retrieves the full version history for a specific unit configuration to analyze its evolution.

  • Version History Report: SELECT version_no, creation_date, last_updated_by, status FROM ahl_uc_headers_h WHERE unit_config_header_id = :1 ORDER BY version_no DESC;
  • Configuration Snapshot at a Point in Time: Queries often join this table with related detail tables (like AHL_UC_NODES_H) using both the header ID and version number to reconstruct the complete configuration state for a given version.
  • Change Analysis: Comparing consecutive versions (by joining the table to itself on UNIT_CONFIG_HEADER_ID and adjacent VERSION_NO) can programmatically identify which attributes were modified in each revision.

Related Objects

The AHL_UC_HEADERS_H table has defined foreign key relationships with several core EBS tables, as documented in the ETRM metadata.

  • AHL_UNIT_CONFIG_HEADERS: The base transactional table. The foreign key on UNIT_CONFIG_HEADER_ID establishes the core link between a current header and all its historical versions.
  • AHL_MC_HEADERS_B: References the master configuration template via MASTER_CONFIG_ID, providing the design blueprint from which the unit configuration was instantiated.
  • CSI_ITEM_INSTANCES: Links the configuration to the specific physical asset or serialized item instance in Inventory via CSI_ITEM_INSTANCE_ID.
  • AHL_UNIT_CONFIG_HEADERS (as Parent): The self-referential foreign key on PARENT_UC_HEADER_ID manages hierarchical relationships between different unit configurations, allowing for complex, multi-level asset structures.

In practice, this history table is also closely related to other AHL history tables, such as AHL_UC_NODES_H, which stores the versioned hierarchy of components within each unit configuration.