Search Results ue_relationship_id




Overview
Explore in AI Chat

Overview

The AHL_UE_RELATIONSHIPS table is a core data repository within the Oracle E-Business Suite Complex Maintenance, Repair, and Overhaul (CMRO) module. It is designed to manage and store the structural and logical relationships between different Unit Effectivities (UEs). A Unit Effectivity defines the applicability of a service bulletin, engineering change order, or maintenance requirement to a specific unit or a range of serialized units. This table is essential for establishing dependency, hierarchy, and association rules between these effectivities, enabling the accurate modeling of complex maintenance programs and ensuring that related modifications or inspections are tracked and applied correctly across an asset fleet.

Key Information Stored

The table's primary purpose is to link one Unit Effectivity (UE_ID) to another related Unit Effectivity (RELATED_UE_ID) under a specific type of relationship. The critical columns that facilitate this are the UE_ID and RELATED_UE_ID, both foreign keys to the AHL_UNIT_EFFECTIVITIES_B table, which stores the master definition of each effectivity. The RELATIONSHIP_CODE column defines the nature of the association between the two linked effectivities, such as a parent-child hierarchy, a prerequisite, or a supersedence link. Each record is uniquely identified by the UE_RELATIONSHIP_ID primary key. The table also enforces a unique constraint (AHL_UE_RELATIONSHIPS_UK1) on the combination of RELATIONSHIP_CODE, RELATED_UE_ID, and UE_ID to prevent duplicate relationship definitions.

Common Use Cases and Queries

A primary use case is tracing the dependency chain of engineering changes. For instance, a query can identify all Unit Effectivities that are prerequisites for performing a specific modification. This is critical for maintenance planning and ensuring compliance. Another common scenario is generating a hierarchical report of all related effectivities for a given unit or serial number to understand its complete modification history. Sample SQL to find all relationships for a specific UE_ID would be:

  • SELECT relationship_code, related_ue_id FROM ahl_ue_relationships WHERE ue_id = :p_ue_id;

Conversely, to find all effectivities that depend on a given UE_ID, the query would reference the RELATED_UE_ID column. Reporting often joins this table with AHL_UNIT_EFFECTIVITIES_B and item/serial number tables to produce human-readable lists of related maintenance actions.

Related Objects

The AHL_UE_RELATIONSHIPS table has fundamental dependencies within the AHL schema. Its two foreign keys directly reference the AHL_UNIT_EFFECTIVITIES_B table, which is the master source for all unit effectivity definitions. Any process, API, or user interface that creates, updates, or deletes relationships will interact with this table. While not listed in the provided metadata, it is typically referenced by various CMRO application programming interfaces (APIs) and user interface forms that manage effectivity relationships. Furthermore, key business logic governing these relationships is likely encapsulated within PL/SQL packages in the AHL module, which would query and manipulate data in this table to enforce business rules.