Results for “ahl_unit_config_headers”

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

Overview

AHL_UNIT_CONFIG_HEADERS is the master table in the Oracle E-Business Suite Complex Maintenance Repair and Overhaul (AHL) module that defines a unit configuration. In AHL terminology, a unit configuration represents a single complex, tracked piece of equipment — for example an aircraft, engine, or other serialized asset — that is built from a master configuration template. Each row in this table captures the identity of one such unit configuration and the master configuration template from which it was instantiated, thereby establishing the relationship between a generic equipment definition and a specific physical asset maintained in the field.

The table resides in the AHL schema and is classified as a VALID database object in both Oracle EBS 12.1.1 and 12.2.2. Under a heuristic Data Vault classification mined from its foreign key structure, AHL_UNIT_CONFIG_HEADERS most closely resembles a hub: it holds a stable business key (NAME) and a surrogate primary key (UNIT_CONFIG_HEADER_ID), and serves as the central anchor to which transactional and descriptive satellites attach. This classification is offered as a modeling suggestion only; the physical table is a standard EBS transactional entity governed by the Multi-Org/security model via SECURITY_GROUP_ID.

Key Information Stored

The physical schema documents 32 columns. The most significant are summarized below.

• UNIT_CONFIG_HEADER_ID — the surrogate primary key (AHL_UNIT_CONFIG_HEADERS_PK), a system-generated identifier that uniquely distinguishes each unit configuration row.
• NAME — the business-key candidate, enforced by unique index AHL_UNIT_CONFIG_HEADERS_U2. It holds the user-recognizable unit configuration name.
• MASTER_CONFIG_ID — foreign key to AHL_MC_HEADERS_B, identifying the master configuration template from which this unit was constructed.
• CSI_ITEM_INSTANCE_ID — foreign key to CSI_ITEM_INSTANCES, linking the configuration to the deployed item instance (the physical asset record) in Oracle's Install Base.
• PARENT_UC_HEADER_ID — self-referencing foreign key that establishes a parent/child hierarchy among unit configurations, supporting nested or sub-assembly structures.
• UNIT_CONFIG_STATUS_CODE and ACTIVE_UC_STATUS_CODE — status codes describing the lifecycle and active state of the configuration.
• ACTIVE_START_DATE and ACTIVE_END_DATE — date-effective range defining the validity window of the configuration.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing data-level access control.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — standard EBS who-columns and optimistic-locking attributes maintained by the framework.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF (Descriptive Flexfield) extension columns provided for customer-specific data.

Common Use Cases and Queries

Typical reporting and integration scenarios resolve the unit configuration to its master template and installed asset, validate lifecycle status, or traverse the parent/child hierarchy. A representative join pattern is:

• Reporting all configurations derived from a given master template:
  SELECT uch.UNIT_CONFIG_HEADER_ID, uch.NAME FROM AHL.AHL_UNIT_CONFIG_HEADERS uch WHERE uch.MASTER_CONFIG_ID = :master_config_id;
• Associating a configuration with its installed item instance and master header:
  SELECT uch.NAME, mch.NAME master_name, cii.SERIAL_NUMBER FROM AHL.AHL_UNIT_CONFIG_HEADERS uch, AHL.AHL_MC_HEADERS_B mch, CSI.CSI_ITEM_INSTANCES cii WHERE uch.MASTER_CONFIG_ID = mch.MASTER_CONFIG_ID AND uch.CSI_ITEM_INSTANCE_ID = cii.ITEM_INSTANCE_ID;
• Traversing the parent/child hierarchy through the self-referencing key:
  SELECT child.NAME, parent.NAME parent_name FROM AHL.AHL_UNIT_CONFIG_HEADERS child, AHL.AHL_UNIT_CONFIG_HEADERS parent WHERE child.PARENT_UC_HEADER_ID = parent.UNIT_CONFIG_HEADER_ID;
• Filtering active configurations by date-effective range and status for operational dashboards.

Because the table is referenced by part-change, unit-effectivity, and header-historical tables, it is also the anchor for change history and effectivity reporting.

Related Objects

The following related objects are the most significant, based on the documented foreign key relationships.

• AHL_MC_HEADERS_B — referenced via MASTER_CONFIG_ID; supplies the master configuration template definition.
• CSI_ITEM_INSTANCES — referenced via CSI_ITEM_INSTANCE_ID; the Install Base item instance representing the physical asset.
• AHL_UNIT_CONFIG_HEADERS (self) — referenced via PARENT_UC_HEADER_ID; defines parent/child configuration hierarchy.
• AHL_UC_HEADERS_H — references UNIT_CONFIG_HEADER_ID and PARENT_UC_HEADER_ID; the historical/audit header table mirroring unit configuration changes.
• AHL_PART_CHANGES — references UNIT_CONFIG_HEADER_ID; records part changes executed against the unit configuration.
• AHL_PC_ASSOCIATIONS — references the configuration via UNIT_ITEM_ID; stores part-change associations.
• AHL_UF_HEADERS — references UNIT_CONFIG_HEADER_ID; holds unit-effectivity header records.
• AHL_UNIT_EFFECTIVITIES_B — references UNIT_CONFIG_HEADER_ID; stores date-effective configuration details.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; enforces data-level security.

Together these objects form the core of the AHL configuration management data model, with AHL_UNIT_CONFIG_HEADERS acting as the central hub connecting equipment definitions, installed assets, change history, and effectivity data.