Search Results build_simulationplan_ue




Overview
Explore in AI Chat

Overview

APPS.AHL_UMP_UNITMAINT_PVT is a private (PVT) PL/SQL package within the Oracle E-Business Suite Enterprise Asset Management (EAM) and Complex Maintenance, Repair, and Overhaul (CMRO) product family. It is part of the AHL (Asset Health / Maintenance) module and belongs to the Unit Maintenance processing subsystem, identified by the AHL_UMP prefix. The package encapsulates the core business logic that builds, validates, and maintains unit effectivity records—the association between a physical asset (a CSI item instance) and a maintenance requirement (MR) interval or program node, including its scheduled due date or due counter value.

Because it is a private package, AHL_UMP_UNITMAINT_PVT is not intended to be called directly by external consumers. Instead, it exposes the internal implementation behind the public unit-maintenance APIs and serves as the engine that generates and terminates unit effectivities when maintenance programs are instantiated against a fleet of units. The header declares strongly typed record structures, most prominently Unit_Effectivity_Rec_Type, which mirrors the AHL_UNIT_EFFECTIVITIES_B columns and carries derived display fields (instance number, MR title, MR version number, status description) alongside scheduling attributes such as DUE_DATE, DUE_COUNTER_VALUE, FORECAST_SEQUENCE, and tolerance/repetitive flags.

Key Procedures and Functions

  • BUILD_UNITEFFECTIVITY — The procedure the user search targeted. It constructs unit effectivity records for a unit or set of units, deriving scheduling data from the associated maintenance requirement interval. It is the primary builder entry point within this package.
  • PROCESS_UNITEFFECTIVITY — Processes the built unit effectivity records, applying validation, insert/update logic, and the master-detail linkage through AHL_UE_RELATIONSHIPS.
  • BUILD_SIMULATIONPLAN_UE — Builds unit effectivities in the context of a simulation plan, allowing what-if analysis without committing live schedules to the maintenance program.
  • CAPTURE_MR_UPDATES — Captures changes made to maintenance requirements and propagates the relevant updates to affected unit effectivities.
  • VALIDATE_FOR_INITIALIZE — Performs pre-initialization validation, confirming the data prerequisites required before unit effectivities are generated.
  • TERMINATE_MR_INSTANCES — Terminates maintenance requirement instances, ending the active effectivity cycle for the affected units.
  • PROCESS_TERMINATED_MRS — Post-processes maintenance requirements that have been terminated, reconciling dependent unit effectivity and deferral records.
  • BUILDING_PM_UNIT_EFFECTIVITIES — Builds unit effectivities for preventive maintenance programs.
  • BUILDING_AHL_UNIT_EFFECTIVITY — Builds unit effectivities from the AHL (Asset Health) source, covering AHL-specific maintenance requirements.
  • BUILDING_PC_UNIT_EFFECTIVITIES — Builds unit effectivities driven by program/collection node structures (the PC, or Program Collection, entities).

Tables Accessed

The package reads and writes across the unit maintenance data model. Base and transactional tables include AHL_UNIT_EFFECTIVITIES_B (the master effectivity records), AHL_UE_RELATIONSHIPS (predecessor/successor sequencing between effectivities), AHL_MR_EFFECTIVITIES, AHL_MR_HEADERS_B, and AHL_MR_INTERVALS, which supply the maintenance requirement and interval definitions that drive scheduling. Program structures are read from AHL_PC_HEADERS_B, AHL_PC_NODES_B, and AHL_SIMULATION_PLANS_B. Unit-level context comes from AHL_FLEET_UNIT_ASSOCS, AHL_UNIT_CONFIG_HEADERS, AHL_UNIT_ACCOMPLISHMNTS, AHL_UNIT_DEFERRALS_B, and AHL_UNIT_THRESHOLDS. Counter data used to compute due counter values is drawn from CSI_COUNTERS_B and CSI_COUNTER_ASSOCIATIONS.

Usage Notes

AHL_UMP_UNITMAINT_PVT is invoked indirectly. Oracle's Unit Maintenance and maintenance-program forms call the public wrapper APIs, which in turn delegate to this private package to build and process effectivities. Concurrent programs that initialize maintenance programs against fleets, as well as program-termination and MR-update business flows, also route through these procedures. Because the package is classified PVT and is listed as referenced by five other packages, customizations should not call it directly; developers should use the supported public AHL unit maintenance APIs instead. Direct invocation risks bypassing validation and object-version handling and is not upgrade-safe across 12.1.1 and 12.2.2.