Search Results ahl_fmp_mr_header_pvt




Overview
Explore in AI Chat

Overview

APPS.AHL_FMP_MR_HEADER_PVT is a private PL/SQL package within the Oracle E-Business Suite Enterprise Asset Management (EAM) module, specifically belonging to the Asset Lifecycle Management (AHL) schema family. It forms part of the Maintenance Requirement (MR) framework used by Enterprise Asset Management to define, manage, and maintain preventative maintenance programs and their associated requirements. In Oracle EBS 12.1.1 and 12.2.2 the package carries an API classification of PVT (private), indicating that it is intended as an internal implementation layer rather than a publicly callable interface. Public consumers are expected to reach the underlying functionality through the corresponding public package, AHL_FMP_MR_PUB, which in turn invokes this private package. The package encapsulates the core create, update, and delete logic for Maintenance Requirement header records, providing a controlled, centralized mechanism for DML against the header tables while enforcing the business rules and validation patterns of the AHL foundation layer. By separating the private execution logic from the public interface, Oracle preserves the ability to evolve implementation details without impacting external callers.

Key Procedures and Functions

The documented package exposes three procedures, each of which is a private wrapper for header lifecycle operations:

  • CREATE_MR_HEADER — Handles the creation of a new Maintenance Requirement header record. It is responsible for inserting the primary header row and any dependent child records required to establish a complete MR definition.
  • UPDATE_MR_HEADER — Applies modifications to an existing Maintenance Requirement header. The procedure manages changes to header attributes while maintaining consistency across the related detail tables.
  • DELETE_MR_HEADER — Removes a Maintenance Requirement header and its associated dependent records, ensuring referential integrity is upheld across the MR entity relationships.

The parameter lists are not disclosed in the available metadata and are therefore not enumerated here. As a private package following Oracle's API conventions, these procedures typically accept identifiers and attribute structures and integrate with FND_API-based error handling and message propagation, evidenced by the package's dependency on APPS.FND_API.

Tables Accessed

The package reads and writes a substantial set of AHL Maintenance Requirement tables, accessed through APPS synonyms. The principal DML target is AHL_MR_HEADERS_B and its translation/sequence companion AHL_MR_HEADERS_B_S, which store the header itself. Supporting tables include AHL_MR_ACTIONS_B, AHL_MR_EFFECTIVITIES, AHL_MR_EFFECTIVITY_DTLS, AHL_MR_INTERVALS, AHL_MR_LOOP_CHAIN_RELNS, AHL_MR_ORGANIZATIONS, AHL_MR_RELATIONSHIPS, AHL_MR_ROUTES, AHL_MR_ROUTE_SEQUENCES, and AHL_MR_VISIT_TYPES, which together define the actions, effectivity ranges, scheduling intervals, organizational scope, route structures, and visit type associations of a maintenance requirement. Reference tables AHL_DOC_TITLE_ASSOS_B, AHL_DOC_TITLE_ASSOS_TL, and AHL_PROG_TYPE_SUBTYPES supply document title associations and program type subtype validation used during header creation and update.

Usage Notes

AHL_FMP_MR_HEADER_PVT is not invoked directly by end users. It is referenced by three other packages: AHL_FMP_MR_PUB, which exposes the public Maintenance Requirement API; AHL_FMP_MR_APPROVAL_PVT, which manages MR approval workflows; and AHL_FMP_MR_HEADER_PVT_W, the Oracle Forms-based wrapper typically bound to the EAM Maintenance Requirement setup form. It also references itself recursively. Accordingly, the package is exercised when users define or maintain maintenance requirements through the relevant EAM setup forms, when approval processing requires header manipulation, or when custom code calls the public MR API. In Oracle EBS 12.1.1 and 12.2.2 this structure remains consistent, with FND_API providing the standard validation and error-stack services that underpin all AHL foundation APIs. Customizations should call AHL_FMP_MR_PUB rather than the private package, since no commitment is made to the stability of the private interface.