Search Results ahl_ue_simulations_s

Overview

APPS.AHL_UMP_PROCESSUNIT_EXTN_PVT is a private (PVT-classified) PL/SQL package body in the Oracle E-Business Suite Enterprise Asset Management (EAM) / Asset Tracking module. The AHL schema prefix designates the Asset Lifecycle / Complex Maintenance, Repair and Overhaul (cMRO) and Unit Maintenance Processing (UMP) functional area. This package supports the Unit Maintenance Processing engine's simulation-based "what-if" processing, in which maintenance requirements, unit effectivities, deferrals, and visit schedules are evaluated against simulated configurations before being committed to the live maintenance plan.

Specifically, the package body provides the plumbing used to stage maintenance processing results into temporary work areas and then flush those results into the AHL simulation tables. It sits at the intersection of the Unit Effectivity (UE) and Maintenance Requirement (MR) subsystems, and acts as an extension layer on top of the core process-unit logic in APPS.AHL_UMP_PROCESSUNIT_PVT. As a PVT package, it is not intended to be called directly by end users or external customizations; it is invoked internally by the UMP processing stack.

Key Procedures and Functions

The ETRM metadata documents two procedures for this package body:

• FLUSH_FROM_TEMP_TABLE — Moves or reads data out of the temporary staging structures (such as those related to temporary unit effectivities and temporary unit service-request deferrals) during the simulation processing cycle. It is the counterpart to the flush-to-target operation and supports reconciliation of the temporary workspace with the processing context.
• FLUSH_TO_SIM_UE_TABLE — Writes the staged results into the simulation unit-effectivity table (AHL_UE_SIMULATIONS). This is the operation that persists the outcome of a simulation run so that downstream simulation plan evaluation and reporting can consume it.

Both procedures rely on the FND_API, FND_MSG_PUB, and AHL_DEBUG_PUB utilities for error handling, message stacking, and debug tracing, consistent with standard EBS API coding conventions. Parameter lists are not disclosed in the ETRM documentation and are therefore not reproduced here.

Tables Accessed

The package references a broad set of AHL base and interface tables through APPS synonyms:

• Simulation structures: AHL_UE_SIMULATIONS, AHL_UE_SIMULATIONS_S, and AHL_SIMULATION_PLANS_B — the primary targets for simulation output and the parent simulation plan definitions.
• Temporary workspace: AHL_TEMP_UNIT_EFFECTIVITIES and AHL_TEMP_UNIT_SR_DEFERRALS — the staging tables read by FLUSH_FROM_TEMP_TABLE.
• Unit effectivity and relationship data: AHL_UNIT_EFFECTIVITIES_B, AHL_UNIT_EFFECTIVITIES_VL, AHL_UNIT_EFFECTIVITIES_APP_V, AHL_UE_RELATIONSHIPS, AHL_UNIT_THRESHOLDS, and AHL_UNIT_DEFERRALS_B — governing the effectivity ranges and threshold logic applied to units.
• Maintenance requirements and scheduling: AHL_APPLICABLE_MRS, AHL_MR_HEADERS_B, AHL_SCHEDULE_MATERIALS, AHL_VISITS_B, AHL_VISIT_TASKS_B, and OKC_K_LINES_B (the service contract line reference) — the maintenance visit and material scheduling context.
• Incident reference: CS_INCIDENTS_ALL_VL — links processing to service request incidents.

It also depends on helper packages including AHL_SCHEDULE_MATERIALS_PKG, AHL_UE_RELATIONSHIPS_PKG, AHL_UNIT_DEFERRALS_PKG, AHL_UNIT_EFFECTIVITIES_PKG, AHL_UMP_UTIL_PKG, and AHL_UTIL_PKG.

Usage Notes

Because this is a PVT package, it is invoked internally by the UMP processing framework — principally by AHL_UMP_PROCESSUNIT_PVT — rather than from forms or concurrent programs directly. It is exercised when a user runs a unit maintenance process in simulation mode from the cMRO / Asset Tracking UI, where the engine evaluates proposed effectivity and deferral changes against the simulation tables without altering production data.

The search term "ahl_ue_simulations_s" corresponds to the sequence object associated with AHL_UE_SIMULATIONS, confirming that this package participates in generating primary keys for simulation rows during the flush operation. Customizations should avoid calling this package directly; the supported extension point is the public UMP API layer, and any direct dependency risks invalidation across 12.1.1 and 12.2.2 upgrades where this private body is subject to change.