Search Results building_pc_unit_effectivities




Overview
Explore in AI Chat

Overview

APPS.AHL_UMP_UNITMAINT_PVT is a private PL/SQL package within the Oracle Enterprise Asset Management (eAM) and Maintenance Management family of modules in Oracle E-Business Suite. Its header identifies it as the private implementation component (the _PVT suffix) that supports the public unit maintenance APIs used by the Asset Lifecycle (AHL) product domain. The package is concerned with the lifecycle of unit effectivities — the intersection of a maintained unit (a specific item instance tracked in CSI) with a maintenance requirement (MR), interval, and program. In practical terms, it is the engine that determines when maintenance is due, records accomplishment, manages deferrals and thresholds, and maintains the relationships between a unit's maintenance configuration and the plans that drive it.

The searched term building_pc_unit_effectivities corresponds to the documented procedure BUILDING_PC_UNIT_EFFECTIVITIES, which is one of the build routines in this package responsible for generating unit effectivity rows from preventive maintenance (PM) definitions associated with PC (preventive/counter) headers and nodes. This routine is part of a family of "building" procedures that translate plan and requirement definitions into concrete, dated unit-level maintenance obligations.

Key Procedures and Functions

The package exposes ten documented procedures. The following describes their purpose without presuming their parameter signatures.

  • PROCESS_UNITEFFECTIVITY — Core orchestrator that applies processing logic to unit effectivity records, driving status transitions, due-date computation, and accomplishment handling.
  • BUILD_UNITEFFECTIVITY — Generic builder that creates unit effectivity rows from the applicable maintenance requirements for a unit.
  • BUILD_SIMULATIONPLAN_UE — Builds unit effectivities associated with simulation plans, allowing what-if scheduling without committing to live maintenance commitments.
  • CAPTURE_MR_UPDATES — Captures changes to maintenance requirements and propagates their effect onto existing or pending unit effectivities.
  • VALIDATE_FOR_INITIALIZE — Performs pre-initialization validation checks before effectivity data is generated or initialized.
  • TERMINATE_MR_INSTANCES — Ends active maintenance requirement instances, typically when a unit is retired, reconfigured, or a requirement is superseded.
  • BUILDING_PM_UNIT_EFFECTIVITIES — Constructs unit effectivities derived from PM (preventive maintenance) definitions.
  • BUILDING_AHL_UNIT_EFFECTIVITY — Constructs unit effectivities originating from AHL plan structures.
  • BUILDING_PC_UNIT_EFFECTIVITIES — The routine matched by the user's search; builds unit effectivities from PC header and node definitions, linking them to the unit's maintenance program.
  • PROCESS_TERMINATED_MRS — Handles cleanup and status reconciliation following termination of maintenance requirements.

Tables Accessed

The package operates across the AHL and CSI schemas via APPS synonyms. The central write target is AHL_UNIT_EFFECTIVITIES_B, supported by AHL_MR_EFFECTIVITIES, AHL_MR_HEADERS_B, and AHL_MR_INTERVALS, which define the requirement, its header, and interval cadence. AHL_PC_HEADERS_B and AHL_PC_NODES_B supply the PC structure consumed by BUILDING_PC_UNIT_EFFECTIVITIES. AHL_FLEET_UNIT_ASSOCS associates units with fleet/maintenance programs, while AHL_UNIT_CONFIG_HEADERS provides configuration context. Accomplishment data flows through AHL_UNIT_ACCOMPLISHMNTS, and deferral and threshold logic uses AHL_UNIT_DEFERRALS_B and AHL_UNIT_THRESHOLDS. Relationships between effectivities are held in AHL_UE_RELATIONSHIPS. Simulation support uses AHL_SIMULATION_PLANS_B, and counter data is drawn from CSI_COUNTERS_B and CSI_COUNTER_ASSOCIATIONS.

Usage Notes

As a private package, AHL_UMP_UNITMAINT_PVT is not intended for direct invocation by end users or custom extensions. It is called by the public unit maintenance APIs and by the eAM/Asset Lifecycle forms and concurrent programs that generate or refresh unit effectivities. It is referenced by five other packages, reflecting its role as a shared internal utility. The term searched — building_pc_unit_effectivities — indicates a likely interest in how PC-based effectivities are generated, which normally occurs through the standard unit maintenance initialization and rebuild flows rather than through ad-hoc coding. Any customization should target the public API layer, not this private package.