Search Results validate_effectivity

Overview

APPS.AHL_UMP_UNITMAINT_PVT is a private (PVT) PL/SQL package body within the Oracle Enterprise Asset Management (eAM) and Complex Maintenance, Repair, and Overhaul (CMRO) product family, accessed through the AHL schema objects exposed under APPS synonyms. The package encapsulates the core business logic used to create, validate, and maintain unit effectivity definitions for maintainable units, meters, and their associated maintenance programs. It is the engine behind unit maintenance processing, translating maintenance requirements, preventive maintenance (PM) definitions, and maintenance program instances into effective, date-ranged unit effectivity records that drive scheduling and execution of maintenance activities. Because the package is classified as PVT, it is not a public API; it exists to be called by the public AHL packages, concurrent programs, and the eAM CMRO forms layer rather than by external integrations directly. The header revision string (AHLVUMXB.pls 120.20.12010000.3) indicates this object is delivered as part of the 12.1.1 baseline and carried forward into 12.2.2. The documented body includes a set of local helper procedures, including Validate_Effectivity, Validate_Thresholds, Validate_Accomplishments, Convert_Effectivity_Val_To_ID, and Update_Unit_Effectivity, which together provide the validation and identifier-resolution services consumed by the public procedures.

Key Procedures and Functions

• BUILD_UNITEFFECTIVITY — Constructs unit effectivity records for a maintainable unit, applying the relevant maintenance program and interval definitions.
• BUILDING_PM_UNIT_EFFECTIVITIES — Builds unit effectivities specifically derived from preventive maintenance program definitions.
• BUILDING_AHL_UNIT_EFFECTIVITY — Generates unit effectivity rows for the AHL maintenance program context.
• BUILDING_PC_UNIT_EFFECTIVITIES — Builds unit effectivities associated with a maintenance program (PC) header and node structure.
• BUILD_SIMULATIONPLAN_UE — Produces unit effectivity records for simulation plans, enabling what-if planning of maintenance schedules.
• PROCESS_UNITEFFECTIVITY — Orchestrates the end-to-end processing of unit effectivity, invoking the build and validation helpers.
• VALIDATE_FOR_INITIALIZE — Validates the state of maintenance objects before initialization, ensuring prerequisites are satisfied before effectivities are generated.
• CAPTURE_MR_UPDATES — Captures updates to maintenance requirements so that dependent effectivity records remain synchronized.
• TERMINATE_MR_INSTANCES — Terminates maintenance requirement instances, including their associated effectivities.
• PROCESS_TERMINATED_MRS — Processes maintenance requirements that have been terminated, cleaning up related unit effectivity data.

Local helper routines (per the documented body) include Validate_Effectivity, Validate_Thresholds, Validate_Accomplishments, Convert_Threshold_Val_To_ID, Convert_Accomplish_Val_To_ID, and Convert_Effectivity_Val_To_ID. A query context matching "validate_effectivity" most directly concerns Validate_Effectivity, which performs validation of a unit effectivity record prior to persistence.

Tables Accessed

• AHL_UNIT_EFFECTIVITIES_B — primary store of unit effectivity definitions; read and written during build and termination.
• AHL_MR_HEADERS_B, AHL_MR_INTERVALS, AHL_MR_EFFECTIVITIES — maintenance requirement headers, their intervals, and resultant effectivities.
• AHL_UNIT_THRESHOLDS, AHL_UNIT_ACCOMPLISHMNTS, AHL_UNIT_DEFERRALS_B — threshold, accomplishment, and deferral data validated alongside effectivity.
• AHL_SIMULATION_PLANS_B — supports simulation plan effectivity generation.
• AHL_UE_RELATIONSHIPS — parent/child effectivity relationships.
• AHL_PC_HEADERS_B, AHL_PC_NODES_B — maintenance program headers and nodes.
• AHL_FLEET_UNIT_ASSOCS, AHL_UNIT_CONFIG_HEADERS — unit configuration and fleet associations.
• CSI_COUNTERS_B, CSI_COUNTER_ASSOCIATIONS — meter/counter definitions associated with unit effects.

Usage Notes

This package is invoked indirectly through the public AHL maintenance APIs and the CMRO/eAM forms and concurrent programs that build, validate, and terminate unit effectivity and maintenance program instances. It is referenced by five other packages, confirming its role as an internal dependency rather than an entry point. Custom code should invoke the corresponding public AHL_UMP APIs instead of calling AHL_UMP_UNITMAINT_PVT directly, since private signatures may change across patch levels (12.1.1 to 12.2.2).