Search Results ahl_simulation_pvt




Overview
Explore in AI Chat

Overview

APPS.AHL_SIMULATION_PVT is a private PL/SQL package within the Oracle Enterprise Asset Management (eAM) and Asset Lifecycle Management (ALM) modules of Oracle E-Business Suite. It belongs to the AHL product family, which governs asset tracking, fleet maintenance, and unit maintenance planning. As indicated by the "_PVT" suffix and the API classification "PVT", this package is designated as a private implementation package rather than a public application programming interface. It is not intended for direct invocation by external consumers; instead, it serves as the internal engine supporting simulation planning operations within the AHL subsystem. The package operates on the AHL simulation data model, which allows maintenance planners to model and evaluate proposed maintenance plans before committing them to actual execution. In both EBS 12.1.1 and 12.2.2, the package resides in the APPS schema and holds a VALID status in the ETRM repository.

Key Procedures and Functions

The package exposes three documented procedures, each corresponding to a distinct phase of the simulation lifecycle:

  • DELETE_SIMULATION_PLAN — Removes a simulation plan and its associated data from the simulation schema. This procedure supports cleanup and rollback of planning scenarios that are no longer required.
  • IMPLEMENT_SIMULATION_PLAN — Commits a validated simulation plan, transitioning it from a modeled scenario into actual maintenance requirements. This is the central procedure for converting simulation output into actionable maintenance demand.
  • REMOVE_UNIT_FROM_PLAN — Detaches a specific unit (via its fleet unit association) from an existing simulation plan, allowing planners to refine the scope of a scenario without discarding the entire plan.

The ETRM metadata does not expose parameter signatures for these procedures. They should be treated as internal interfaces invoked by the public wrapper package AHL_SIMULATION_API rather than called directly.

Tables Accessed

The package reads and writes through APPS synonyms for the following documented tables and built-in packages:

  • AHL_SIMULATION_PLANS_B — the base table storing simulation plan headers. Central to all three procedures.
  • AHL_UE_SIMULATIONS — stores user-entered simulation results and unit-level simulation details.
  • AHL_FLEET_UNIT_ASSOCS — links fleet units to plans; accessed by REMOVE_UNIT_FROM_PLAN and IMPLEMENT_SIMULATION_PLAN.
  • AHL_UMP_MAINT_REQMNTS — unit maintenance plan maintenance requirements generated when a simulation is implemented.
  • AHL_UMP_MATERIAL_REQMNTS — material requirements derived from the implemented plan.
  • AHL_UMP_RESOURCE_REQMNTS — resource requirements derived from the implemented plan.
  • DBMS_LOCK — used for serialization/concurrency control during plan implementation.
  • PLITBLM — the Oracle PL/SQL integer table utility, used for array processing.

The dependency listing also shows references to FND_API and STANDARD, indicating use of the Oracle Application Object Library API error-handling conventions and standard PL/SQL constructs.

Usage Notes

APPS.AHL_SIMULATION_PVT is invoked indirectly. The ETRM dependency record shows that it is referenced by APPS.AHL_SIMULATION_PVT itself (self-reference) and that it references FND_API. It is not referenced by any other package in the repository, which reinforces its private classification. In practice, the procedures are called from the corresponding simulation forms in the eAM/ALM responsibility, typically the Simulation Plan and Unit Maintenance Plan (UMP) workbenches, or from concurrent programs that process simulation batches. Custom code should not call this package directly because it bypasses public API validation and is subject to change between patch levels. Developers requiring simulation functionality should use the documented public package AHL_SIMULATION_API, which wraps the private procedures with proper FND_API error handling and security checks. Given the presence of DBMS_LOCK, callers should ensure that concurrent implementation of the same simulation plan is avoided to prevent lock contention.