Search Results ahl_mr_relationships




Overview
Explore in AI Chat

Overview

The AHL_MR_RELATIONSHIPS table is a core data object within the Oracle E-Business Suite (EBS) module for Complex Maintenance, Repair, and Overhaul (AHL). It serves as the central repository for defining and storing hierarchical relationships between different maintenance requirements (MRs). In the context of managing complex assets, such as aircraft or industrial machinery, maintenance procedures are often structured as parent-child hierarchies, where a top-level requirement comprises multiple sub-tasks or dependent procedures. This table enables the modeling of these essential relationships, ensuring that maintenance planning, scheduling, and execution reflect the structured and interdependent nature of the work. Its integrity is critical for accurate work order generation, compliance tracking, and resource planning within the AHL application.

Key Information Stored

The table's primary function is to link two maintenance requirement headers via a relationship record. The most critical columns are the foreign keys that establish these links. The MR_HEADER_ID column typically stores the identifier for the parent maintenance requirement. The RELATED_MR_HEADER_ID column stores the identifier for the child (or related) maintenance requirement. The primary key for the table is MR_RELATIONSHIP_ID, a unique system-generated identifier for each relationship record. While the provided metadata does not list additional descriptive columns, such a table would commonly include attributes to define the relationship type (e.g., mandatory, optional), sequence, and effective date ranges to manage the lifecycle of the dependency.

Common Use Cases and Queries

A primary use case is the retrieval of a complete maintenance procedure tree for a given top-level MR. This is essential for generating a comprehensive work package or bill of materials for a maintenance visit. For example, to find all child requirements for a specific parent MR header ID, a query would join AHL_MR_RELATIONSHIPS to AHL_MR_HEADERS_B twice: once to get the parent details and once to get the child details. Conversely, identifying the parent of a given MR is crucial for understanding procedural context. Reporting on relationship structures helps analyze maintenance complexity and standardize procedure templates. Data integrity checks often involve queries to identify orphaned relationships or circular dependencies that could break the hierarchy.

Related Objects

The AHL_MR_RELATIONSHIPS table has a direct and fundamental dependency on the AHL_MR_HEADERS_B table, which stores the master definition of all maintenance requirements. As documented, two foreign key constraints exist:

  • From AHL_MR_RELATIONSHIPS.MR_HEADER_ID to AHL_MR_HEADERS_B (likely the MR_HEADER_ID column). This links the relationship to the parent MR.
  • From AHL_MR_RELATIONSHIPS.RELATED_MR_HEADER_ID to AHL_MR_HEADERS_B (likely the MR_HEADER_ID column). This links the relationship to the child MR.
This structure means that any valid relationship must reference two existing records in the MR headers table. The table is also expected to be referenced by various AHL application forms, workflows, and public APIs (such as the AHL Maintenance Requirements Public API) that create, update, or navigate MR hierarchies.