Search Results ahl_unit_config_headers

Overview

The AHL_UNIT_CONFIG_HEADERS table is a core data object within the Oracle E-Business Suite Complex Maintenance, Repair, and Overhaul (CMRO) application. It serves as the primary repository for defining and managing unit configurations, which represent complex, configurable equipment or assets within the maintenance framework. A unit configuration is instantiated from a master configuration template, which defines the allowable structure and components. This table stores the header-level information for these live, operational instances, forming the structural backbone for managing the hierarchical relationships and lifecycles of complex assets throughout their service period.

Key Information Stored

The table's primary identifier is the UNIT_CONFIG_HEADER_ID, a system-generated unique key. The NAME column is also a unique key, enforcing business-level uniqueness for the unit configuration. The table's structure establishes critical relationships: the MASTER_CONFIG_ID foreign key links the unit to its source template in AHL_MC_HEADERS_B. The CSI_ITEM_INSTANCE_ID links the configuration to a specific physical item instance in the Installed Base (CSI). Perhaps most importantly, the PARENT_UC_HEADER_ID column enables the representation of hierarchical equipment structures by creating a recursive relationship within the same table, allowing a unit configuration to be a child of another. Additional columns typically track lifecycle status, effective dates, and audit information.

Common Use Cases and Queries

This table is central to CMRO processes. Common use cases include generating asset hierarchies for maintenance planning, tracing the configuration history of a unit, and identifying all components within a parent asset. A frequent reporting need is to retrieve the complete hierarchical tree for a top-level unit. This can be achieved using hierarchical SQL queries (CONNECT BY or recursive WITH clauses in Oracle). For example, to find all child configurations for a given unit:

• SELECT LEVEL, ucht.NAME, ucht.UNIT_CONFIG_HEADER_ID FROM AHL_UNIT_CONFIG_HEADERS ucht START WITH ucht.NAME = '<Top_Unit_Name>' CONNECT BY PRIOR ucht.UNIT_CONFIG_HEADER_ID = ucht.PARENT_UC_HEADER_ID;

Another common pattern joins to the Installed Base to fetch item details: SELECT uch.NAME, csi.INSTANCE_NUMBER, csi.SERIAL_NUMBER FROM AHL_UNIT_CONFIG_HEADERS uch, CSI_ITEM_INSTANCES csi WHERE uch.CSI_ITEM_INSTANCE_ID = csi.INSTANCE_ID;

Related Objects

The table maintains extensive relationships within the AHL schema, as documented by its foreign keys. Key related objects include:

• AHL_MC_HEADERS_B: Joined via MASTER_CONFIG_ID to reference the source master configuration template.
• CSI_ITEM_INSTANCES: Joined via CSI_ITEM_INSTANCE_ID to link the logical configuration to a physical asset in Installed Base.
• AHL_UNIT_CONFIG_HEADERS (Self-Referential): Joined via PARENT_UC_HEADER_ID to build equipment hierarchies.
• AHL_UC_HEADERS_H: A history table that tracks changes to records in this header table, joined on UNIT_CONFIG_HEADER_ID and PARENT_UC_HEADER_ID.
• AHL_PART_CHANGES, AHL_PC_ASSOCIATIONS, AHL_UF_HEADERS: Key transactional tables that reference the unit configuration header to track part changes, associations, and unit effectivities, respectively.