Results for “related_ata_sequence_id”

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

Overview

In Oracle E-Business Suite Release 12.1.1 and 12.2.2, AHL.AHL_MEL_CDL_RELATIONSHIPS is a transactional relationship table owned by the AHL (Complex Maintenance Repair and Overhaul) product. It stores directional relationships between pairs of ATA (Air Transport Association) sequence records that belong to the same MEL (Minimum Equipment List) or CDL (Configuration Deviation List) definition. Each row therefore captures a dependency, grouping, or cross-reference between two ATA items within one MEL/CDL document, which is essential for accurately modeling dispatch-critical maintenance logic in aviation MRO operations.

From a dimensional modeling perspective, the ETRM heuristic classification for this object is link. It should be viewed as a many-to-many association table that resolves a relationship between two occurrences of the ATA sequence entity rather than holding descriptive attributes of its own.

Key Information Stored

The table contains 26 documented columns. The most significant are:

• MEL_CDL_RELATIONSHIP_ID — the surrogate primary key, enforcing uniqueness of each relationship row via AHL_MEL_CDL_RELATIONSHIPS_PK and AHL_MEL_CDL_RELATIONSHIPS_U1.
• ATA_SEQUENCE_ID — foreign key to AHL_MEL_CDL_ATA_SEQUENCES identifying the first (source) ATA sequence in the relationship.
• RELATED_ATA_SEQUENCE_ID — foreign key to AHL_MEL_CDL_ATA_SEQUENCES identifying the second (related) ATA sequence.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS enforcing multi-org/multi-tenant data access control.
• OBJECT_VERSION_NUMBER — supports optimistic locking during concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns recording who created and last modified each relationship.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard descriptive flexfield (DFF) columns available for client-specific extensions.

The pair (ATA_SEQUENCE_ID, RELATED_ATA_SEQUENCE_ID) is also covered by the unique business-key candidate AHL_MEL_CDL_RELATIONSHIPS_U2, meaning a given ordered pair of ATA sequences may appear only once.

Common Use Cases and Queries

Typical scenarios include validating MEL/CDL dependencies before dispatch, generating relationship reports for engineering review, and detecting orphaned or circular ATA relationships.

Sample query resolving both endpoints of the relationship:

• SELECT r.MEL_CDL_RELATIONSHIP_ID, a1.ATA_SEQUENCE_NAME source_ata, a2.ATA_SEQUENCE_NAME related_ata FROM AHL_MEL_CDL_RELATIONSHIPS r, AHL_MEL_CDL_ATA_SEQUENCES a1, AHL_MEL_CDL_ATA_SEQUENCES a2 WHERE r.ATA_SEQUENCE_ID = a1.ATA_SEQUENCE_ID AND r.RELATED_ATA_SEQUENCE_ID = a2.ATA_SEQUENCE_ID;
• Filter by SECURITY_GROUP_ID to honor organizational data segregation.
• Join to the parent MEL/CDL headers through the ATA sequence records for a complete document view.
• Reconcile relationships by checking for missing counterparts (WHERE RELATED_ATA_SEQUENCE_ID IS NULL or unmatched joins) to flag data-entry gaps.

Related Objects

• AHL.AHL_MEL_CDL_ATA_SEQUENCES — referenced twice, via ATA_SEQUENCE_ID and RELATED_ATA_SEQUENCE_ID.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for access control.
• AHL_MEL_CDL_RELATIONSHIPS_PK / U1 / U2 — primary and unique index definitions enforcing integrity.
• MEL/CDL header entities in the AHL schema — reachable via the ATA sequence table for full document context.
• AHL MEL/CDL user interfaces and concurrent programs that maintain these relationships through the parent ATA sequence maintenance flows.