Search Results ahl_fmp_mr_effectivity_pvt




Overview
Explore in AI Chat

Overview

APPS.AHL_FMP_MR_EFFECTIVITY_PVT is an Oracle E-Business Suite private (PVT) PL/SQL package that belongs to the Oracle Complex Maintenance, Repair and Overhaul (CMRO) / Asset Lifecycle Management family of modules. The AHL schema prefix identifies objects owned by the eAM and CMRO product suite, and the FMP_MR segment of the name relates to the Maintenance Requirement (MR) functionality used within Flow Manufacturing and asset maintenance planning. This package encapsulates the internal business logic responsible for managing the validity periods, or effectivity, of maintenance requirements defined against maintenance headers.

The package is classified as PVT, meaning it is an internal implementation layer whose procedures are not intended to be called directly by external consumers. It sits beneath the public API surface — specifically the wrapper and public package layers (AHL_FMP_MR_EFFECTIVITY_PVT_W and AHL_FMP_MR_PUB) — which expose the supported interface. The private package therefore serves as the enforcement point for effectivity rules such as date-range validation, interval evaluation, and maintenance-requirement detail processing. It carries a status of VALID in the ETRM repository and is present in both Oracle EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents a single procedure within this package:

  • PROCESS_EFFECTIVITY — The core routine of the package. It is responsible for evaluating and persisting the effectivity associated with a maintenance requirement. In the CMRO data model, effectivity defines the period or interval during which a maintenance requirement is applicable to a given item or asset. This procedure coordinates the validation and update of related records, including the maintenance header, effectivity header, effectivity details, and interval rows. Being private, it is invoked by the corresponding _W wrapper and by AHL_FMP_MR_PUB rather than by end-user code.

No further public procedures or functions are documented in the metadata. The absence of additional entries reflects the narrow, focused role of this private package within the broader MR API stack.

Tables Accessed

The package references the following tables through APPS synonyms, indicating direct data manipulation rather than read-only access in most cases:

  • AHL_MR_EFFECTIVITIES and AHL_MR_EFFECTIVITIES_S — The base and translation/MLS tables holding effectivity definition records. The base table stores the entities, while the _S table provides the descriptive columns required for multi-language support.
  • AHL_MR_EFFECTIVITY_DTLS — Stores the detail lines that qualify each effectivity, such as the specific items or ranges to which a maintenance requirement applies.
  • AHL_MR_HEADERS_B — The maintenance requirement header table, providing the parent record that each effectivity is attached to.
  • AHL_MR_INTERVALS — Stores interval definitions used to schedule or phase maintenance requirements, which the effectivity logic validates against.
  • MTL_SYSTEM_ITEMS_KFV — The key flexfield view over inventory items, used to resolve and validate the item(s) referenced by a maintenance requirement effectivity.
  • PLITBLM — A standard Oracle Applications PL/SQL table type declaration (typically PL/SQL TABLE of VARCHAR2 indexed by BINARY_INTEGER) used internally for bulk processing and array handling within the routine.

Usage Notes

Because AHL_FMP_MR_EFFECTIVITY_PVT is a private package, it should not be called directly from custom code. The supported entry points are the wrapper package AHL_FMP_MR_EFFECTIVITY_PVT_W and the public API AHL_FMP_MR_PUB, both of which delegate to PROCESS_EFFECTIVITY. The package depends on FND_API and STANDARD, confirming that it follows the standard Oracle Applications API error-handling and exception pattern (returning FND_API.G_RET_STS_SUCCESS or error codes). Invocation typically occurs when a maintenance requirement is created or modified through the CMRO or eAM maintenance requirement forms, and during concurrent processing that re-evaluates requirement applicability. Implementers who need to manipulate MR effectivity programmatically should route their calls through AHL_FMP_MR_PUB, ensuring that the internal validations enforced by this private package — including item validation against MTL_SYSTEM_ITEMS_KFV and interval consistency checks — are applied consistently.