Search Results ahl_relationships_b




Overview
Explore in AI Chat

Overview

The AHL_RELATIONSHIPS_B table is a core data object within the Complex Maintenance, Repair, and Overhaul (AHL) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It is designated as an obsolete table from the earlier 11.5.10 release, indicating its structure and data are retained for backward compatibility and potential data migration purposes. The table's primary historical function was to store the position hierarchy of a master configuration. This hierarchical data is fundamental to defining the physical or logical structure of a complex asset, such as an aircraft or industrial machine, by establishing parent-child relationships between its constituent positions or assemblies.

Key Information Stored

The table's structure centers on defining hierarchical relationships within a master configuration. The primary identifier is the RELATIONSHIP_ID column, which serves as the table's primary key. The NAME column is also a unique key, enforcing uniqueness for relationship names. A critical column is PARENT_RELATIONSHIP_ID, which creates a recursive foreign key relationship back to the table's own primary key, enabling the construction of multi-level hierarchies. The table also links to other master data entities via foreign keys, including ITEM_GROUP_ID (referencing AHL_ITEM_GROUPS_B) and COUNTER_GROUP_ID (referencing CS_COUNTER_GROUPS), allowing relationships to be associated with specific groups of items or measurement counters.

Common Use Cases and Queries

Given its obsolete status, direct transactional use in EBS 12.x is limited; however, the table remains critical for historical reporting, data validation, and understanding legacy configuration structures. Common queries involve traversing the hierarchy or joining to related transactional tables. For instance, to retrieve a full hierarchical tree for a specific master configuration, one would use a hierarchical SQL query (CONNECT BY). Analyzing which relationships were associated with Maintenance Requirements (MRs) or part changes would involve joining to AHL_MR_EFFECTIVITIES or AHL_PART_CHANGES, respectively. A typical pattern for fetching a relationship and its parent name would be:

  • SELECT r.RELATIONSHIP_ID, r.NAME, pr.NAME PARENT_NAME
  • FROM AHL_RELATIONSHIPS_B r, AHL_RELATIONSHIPS_B pr
  • WHERE r.PARENT_RELATIONSHIP_ID = pr.RELATIONSHIP_ID(+);

Related Objects

The table maintains integral relationships with several other AHL objects, as documented by its foreign key constraints. It has a recursive relationship with itself via PARENT_RELATIONSHIP_ID. For multilingual support, it is the base table for the translated AHL_RELATIONSHIPS_TL, joined on RELATIONSHIP_ID. Key transactional tables reference it, including AHL_EVENT_ASSOCIATIONS (for linking events to positions), AHL_MR_EFFECTIVITIES (for defining where maintenance requirements apply), and AHL_PART_CHANGES (for tracking part modifications at specific positions). It also references master data tables AHL_ITEM_GROUPS_B and CS_COUNTER_GROUPS to associate the hierarchical position with relevant item and counter groupings.