Search Results mo_proc

Overview

Within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment, AHL_MEL_CDL_MO_PROCEDURES belongs to the AHL – Complex Maintenance Repair and Overhaul product family. It is a VALID base table owned by the AHL schema and serves a single, well-defined purpose: it stores the association between Maintenance & Overhaul (M&O) procedures — specifically Maintenance Requirements whose program_type is MO_PROC — and ATA sequences. In effect it is the junction that links a maintenance requirement header to the ATA chapter/section reference used by the MEL/CDL (Minimum Equipment List / Configuration Deviation List) structures.

From a data-modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure is link. This is consistent with the design: the table has no descriptive payload of its own beyond audit and attribute columns, and its purpose is to resolve a many-to-many relationship between M&O procedures and ATA sequences. The documented schema contains 26 columns, of which the vast majority are the standard EBS WHO columns plus a fifteen-column ATTRIBUTE flex block, reinforcing the link interpretation.

Key Information Stored

• MEL_CDL_MO_PROCEDURE_ID — the single-column surrogate primary key, backed by AHL_MEL_CDL_MO_PROCEDURES_PK and also by unique index AHL_MEL_CDL_MO_PROCEDURES_U1. This is the row identifier used by all downstream references.
• MR_HEADER_ID — foreign key to AHL_MR_HEADERS_B. Identifies the M&O procedure (maintenance requirement header) being associated.
• ATA_SEQUENCE_ID — foreign key to AHL_MEL_CDL_ATA_SEQUENCES. Identifies the ATA sequence to which the procedure is bound.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, providing the multi-org/security-group partitioning used throughout AHL.
• OBJECT_VERSION_NUMBER — optimistic locking column, essential for concurrent updates through the OAF/BC4J framework.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard EBS "WHO" audit columns used for traceability and incremental extraction.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the descriptive flexfield (DFF) segment, reserved for customer-specific extensions to the procedure-to-ATA association.

The business-key candidate documented for this object is MR_HEADER_ID combined with ATA_SEQUENCE_ID, represented by unique index AHL_MEL_CDL_MO_PROCEDURES_UK1. This confirms that a given procedure may be associated with a given ATA sequence only once, and it is the natural key for lookups and validation logic.

Common Use Cases and Queries

The primary consumption patterns for this table are MEL/CDL reporting and the maintenance-program builder. Typical scenarios include: listing every M&O procedure attached to a given ATA chapter; finding which ATA sequences reference a specific maintenance requirement; and validating that no duplicate associations exist before publishing a maintenance program.

A representative join query is:

• SELECT p.MEL_CDL_MO_PROCEDURE_ID, h.MR_HEADER_ID, h.NAME, s.ATA_SEQUENCE_ID, s.ATA_CODE FROM AHL.AHL_MEL_CDL_MO_PROCEDURES p, AHL.AHL_MR_HEADERS_B h, AHL.AHL_MEL_CDL_ATA_SEQUENCES s WHERE p.MR_HEADER_ID = h.MR_HEADER_ID AND p.ATA_SEQUENCE_ID = s.ATA_SEQUENCE_ID AND p.SECURITY_GROUP_ID = :sg_id;

For incremental extracts, filter on LAST_UPDATE_DATE > :last_run. For duplicate detection, group by MR_HEADER_ID, ATA_SEQUENCE_ID having COUNT(*) > 1. When integrating with external MRO systems, the surrogate MEL_CDL_MO_PROCEDURE_ID should be treated as the stable cross-reference key, since the business key may be re-sequenced during program revisions.

Related Objects

• AHL_MR_HEADERS_B — joined via MR_HEADER_ID; provides the maintenance requirement header (the M&O procedure).
• AHL_MEL_CDL_ATA_SEQUENCES — joined via ATA_SEQUENCE_ID; supplies the ATA chapter/section sequence.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID; defines the security partitioning for the row.
• AHL_MR_HEADERS_TL — the translation table for maintenance requirement names and descriptions, frequently joined for multilingual reports.
• AHL_MR_OPERATIONS / AHL_MR_RELATIONSHIPS — sibling AHL structures that further decompose a requirement and often drive the procedure content referenced here.

Because the table is a pure link with no dependents, deletions should be handled through the AHL maintenance-program APIs rather than direct DML, preserving OBJECT_VERSION_NUMBER consistency and security-group integrity.