Search Results process_ata_sequences

Overview

APPS.AHL_MEL_CDL_ATA_SEQS_PVT is a private PL/SQL API package within the Oracle E-Business Suite Enterprise Asset Management (eAM) product family, specifically supporting the Maintenance Execution Library (MEL) and Common Data Library (CDL) functionality. The package encapsulates the business logic required to manage ATA (Air Transport Association) sequence definitions and their associated maintenance order procedures, which are core elements of the maintenance program authoring model in complex aerospace and defense maintenance environments.

The AHL schema underpins the Maintenance Management module, and this package operates at the intersection of ATA chapter sequencing and maintenance requirement (MR) procedures. It provides the procedural backbone for creating, validating, and copying the structured relationships that link repair categories, ATA codes, install/dispatch numbering, and maintenance order procedures. As indicated by the PVT suffix in its name, this is an internal (private) package that is not intended to be called directly by customers or external integrations; it is consumed by other packages within the AHL_MEL_CDL family, which expose the public API surface.

Key Procedures and Functions

The package exposes four documented program units, each addressing a discrete element of the MEL/CDL authoring model:

• PROCESS_ATA_SEQUENCES — Orchestrates the create, update, and delete processing of ATA sequence records against the MEL_CDL_ATA_SEQUENCES entity. It is the primary handler for maintaining the ordered list of ATA codes associated with a MEL/CDL header.
• PROCESS_MO_PROCEDURES — Manages maintenance order procedure records tied to a given ATA sequence. This procedure links maintenance requirement headers and versions to ATA sequence entries, defining the procedures to be executed against a specific ATA chapter.
• PROCESS_ATA_RELATIONSHIPS — Governs the processing of ATA relationship records, maintaining the parent/child or associated structure that connects multiple ATA sequences within a maintenance program.
• COPY_MO_PROC_REVISION — Copies a maintenance order procedure from one revision to another, supporting version management where a procedure's definition is carried forward into a new revision without manual re-entry.

Each program unit conforms to the Oracle Application Object Library (AOL) API conventions, using G_APP_NAME and G_PKG_NAME constants for message registration and debug tracing, and an OBJECT_VERSION_NUMBER column on each record type for optimistic concurrency control.

Tables Accessed

The package reads from and writes to the following documented tables and their identifying sequence/header parents:

• AHL_MEL_CDL_ATA_SEQUENCES and AHL_MEL_CDL_ATA_SEQUENCES_S — the base and translation/security tables holding ATA sequence definitions.
• AHL_MEL_CDL_HEADERS — the parent MEL/CDL header that owns one or more ATA sequences.
• AHL_MEL_CDL_MO_PROCEDURES and AHL_MEL_CDL_MO_PROCEDURES_S — the maintenance order procedure records associated with an ATA sequence.
• AHL_MEL_CDL_RELATIONSHIPS and AHL_MEL_CDL_RELATIONSHIPS_S — relationship rows connecting ATA sequences to one another.
• AHL_MR_HEADERS_B — serves as the source of maintenance requirement header and version information referenced by MO procedures.
• AHL_REPAIR_CATEGORIES — supplies repair category names and identifiers used to classify ATA sequences.
• DUAL and PLITBLM — used for singleton queries and PL/SQL table/array utility operations respectively.

Usage Notes

Because this package carries the PVT classification, it is invoked exclusively by other application code rather than by direct customer calls. It is referenced by two other AHL packages, which act as the public-facing entry points for MEL/CDL maintenance program operations. In practice, it is triggered when users create or modify ATA sequences and MO procedures through the Maintenance Management forms, or when concurrent programs and data-load routines must validate and persist bulk ATA sequence definitions. Custom extensions should never call these procedures directly; instead they should use the corresponding public APIs that wrap this private package to preserve validation, concurrency control, and message handling behavior.