Search Results ahl_ump_unitmaint_pub




Overview
Explore in AI Chat

Overview

The APPS.AHL_UMP_UNITMAINT_PUB package is a public (PUB-classified) PL/SQL API belonging to the Oracle Enterprise Asset Management (eAM) and Asset Lifecycle Management (ALM) family within Oracle E-Business Suite, specifically the AHL schema modules. Its name reflects its role as the unit maintenance public interface: the "UMP" segment denotes Unit Maintenance Processing, and the "_PUB" suffix indicates that it exposes a supported, externally callable API surface that other application modules and customizations are permitted to invoke. The package serves as the transactional entry point for creating, updating, and terminating maintenance requirements (MRs) attached to maintainable units such as assets, serialized equipment, and production machinery.

Functionally, AHL_UMP_UNITMAINT_PUB acts as a thin public wrapper over the private implementation package AHL_UMP_UNITMAINT_PVT, which is its primary documented dependency. All business validation, direct table manipulation, and workflow/notification logic reside in the private package; the public package enforces the standard Oracle FND_API error-handling and concurrency conventions (via FND_API, another documented dependency) before delegating to the private layer.

Key Procedures and Functions

  • CAPTURE_MR_UPDATES — Captures and persists changes made to maintenance requirement records for a unit. This procedure is the standard mechanism for propagating MR definition or scheduling updates into the UMP processing model, ensuring that the unit maintenance program reflects current requirement data.
  • TERMINATE_MR_INSTANCES — Terminates active maintenance requirement instances associated with a unit. It is typically used when a unit is retired, decommissioned, or otherwise removed from the maintenance program, closing out outstanding MR occurrences cleanly.
  • PROCESS_UNITEFFECTIVITY — Processes unit effectivity, that is, the effective dating or applicability of a unit to a maintenance program or requirement. This procedure reconciles the change in a unit's effective status or date range against its maintenance requirements.

No parameter signatures are documented in the ETRM metadata; callers should reference the package specification in the database for exact argument lists.

Tables Accessed

The ETRM metadata for this object does not enumerate the base tables read or written by AHL_UMP_UNITMAINT_PUB through APPS synonyms. Given the documented delegation to AHL_UMP_UNITMAINT_PVT, all table access occurs in the private package and would logically target the unit maintenance requirement entities (units, maintenance requirements, and MR instances) within the eAM/ALM data model. Consumers requiring a definitive table list should query the dependency views USER_DEPENDENCIES or examine AHL_UMP_UNITMAINT_PVT directly.

Usage Notes

AHL_UMP_UNITMAINT_PUB is documented as being referenced by three objects: AHL_FMP_MR_REVISION_PVT, CSF_PREVENTIVE_MAINTENANCE_PVT, and recursively by AHL_UMP_UNITMAINT_PUB itself. The dependency on CSF_PREVENTIVE_MAINTENANCE_PVT confirms the package sits within the preventive maintenance flow used by Oracle Field Service and eAM. The dependency on AHL_FMP_MR_REVISION_PVT indicates it participates in maintenance requirement revision processing.

The package is typically invoked from the eAM/ALM maintenance requirement and unit management forms, from concurrent programs that process MR instances in batch, and from custom PL/SQL that must programmatically terminate or update unit maintenance requirements. Because it is a PUB API and uses FND_API conventions, callers should initialize and check the returned API status and message stack in the standard manner. The object status is VALID in the documented 12.2.2 environment, and its behavior is consistent across 12.1.1 and 12.2.2 releases.