Results for “ahl_fmp_mr_doc_asso_pvt”

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

Overview

AHL_FMP_MR_DOC_ASSO_PVT is a private PL/SQL package in the APPS schema that belongs to the Oracle Enterprise Asset Management (eAM) and Complex Maintenance, Repair and Overhaul (CMRO) product family, identified by the AHL application prefix. The package supports the management of Maintenance Requirement (MR) document associations within the Asset Lifecycle and Maintenance framework. Its name segment "FMP" points to the Forms-based maintenance planning components, "MR" denotes Maintenance Requirement, and "DOC_ASSO" denotes document association. The package is classified as PVT, indicating that it is an internal, private implementation package that is not intended to be called directly by external code; it is instead consumed by wrapper packages, most notably the AHL_FMP_MR_DOC_ASSO_PVT_W wrapper and the public API AHL_FMP_MR_PUB.

The package carries a VALID status in both Oracle EBS 12.1.1 and 12.2.2, confirming it is a supported, compiled object in the ETRM (E-Business Suite Technical Reference Manual) metadata repository. The business function it serves is to manage the relationship between maintenance requirements and the documents (such as specifications, drawings, or procedures) attached to those requirements, ensuring that document linkage data is validated and persisted consistently through the EBS APIs layer.

Key Procedures and Functions

The ETRM metadata documents one procedure or function within this package:

• PROCESS_DOC_ASSOCIATION — This is the core processing routine of the package. Its purpose is to process the association of one or more documents with a maintenance requirement entity. In keeping with the private (PVT) API convention, the procedure is designed to be invoked from the wrapper package AHL_FMP_MR_DOC_ASSO_PVT_W rather than directly from forms or concurrent programs. The procedure encapsulates the logic required to resolve and persist document-to-requirement relationships in a controlled, transaction-safe manner.

The metadata does not expose the parameter list of PROCESS_DOC_ASSOCIATION, and it should not be assumed. Callers must observe the wrapper API signature exposed through AHL_FMP_MR_DOC_ASSO_PVT_W.

Tables Accessed

The only table documented as referenced by this package via APPS synonyms is PLITBLM. In EBS, PLITBLM is a standard PL/SQL table or interface repository object used as a transient in-memory structure for passing collections of values between PL/SQL layers. Its inclusion indicates that PROCESS_DOC_ASSOCIATION constructs and consumes a PL/SQL table (collection) to stage document association records before committing them, a common pattern in EBS public/private API pairs where the private layer receives a pl/sql table payload from the wrapper.

No other database tables are documented in the ETRM excerpt, which is consistent with the package acting as a processing logic layer that delegates persistence to lower-level or public packages. Because it references FND_API, the package also relies on the standard Oracle Application Object Library API utilities for message handling, return status, and exception management.

Usage Notes

AHL_FMP_MR_DOC_ASSO_PVT is not intended for direct invocation. The ETRM dependency data shows that it is referenced by two other packages: AHL_FMP_MR_DOC_ASSO_PVT_W and AHL_FMP_MR_PUB. The "_W" wrapper is the interface layer that defines the public signature and performs input validation before delegating to this private package. The AHL_FMP_MR_PUB package is the published public API for maintenance requirements, and it may route document association processing through the wrapper or directly to the private layer depending on the operation context.

Typical invocation occurs when a user associates a document with a maintenance requirement in the eAM maintenance requirement forms, or when a concurrent program or integration loads document associations in bulk. Custom code should call the wrapper or public API, never AHL_FMP_MR_DOC_ASSO_PVT directly, to preserve API versioning and validation behavior. Because the package depends on FND_API, callers should initialize the FND global context and handle the standard API return status conventions.