Search Results ahl_visits_b_s

Overview

APPS.AHL_LTP_SIMUL_PLAN_PVT is the private (PVT) package body that implements the core business logic for Simulation Plans within the Oracle Enterprise Asset Management (EAM) and Complex Maintenance, Repair, and Overhaul (CMRO) modules of Oracle EBS 12.1.1 and 12.2.2. The AHL product prefix corresponds to the Enterprise Asset Management or, more specifically, the Asset Lifecycle Management (ALM) family of schemas. Simulation Plans are essentially "what-if" planning constructs used by maintenance planners to model a set of visits, tasks, and resource requirements without committing them to the live production schedule. This package provides the programmatic foundation for creating, cloning, updating, and removing those simulated plans and their associated visits.

The PVT designation indicates that this package is intended for internal use by the AHL_LTP_SIMUL_PLAN_PUB public API layer, rather than being called directly by external consumers. The public package wraps the private procedures with validation and error handling consistent with the Oracle Application Object Library (FND_API) message and exception framework. The dependency list confirms this relationship, as AHL_LTP_SIMUL_PLAN_PUB references this private package, which in turn invokes AHL_DEBUG_PUB for diagnostic logging, FND_MSG_PUB and FND_MESSAGE for message resolution, and FND_LOG for debug trace output.

Key Procedures and Functions

• CREATE_SIMULATION_PLAN — Establishes a new simulation plan record in the AHL_SIMULATION_PLANS_B table, initializing the master plan header and any required defaults.
• UPDATE_SIMULATION_PLAN — Modifies the attributes of an existing simulation plan header, allowing planners to revise scenario parameters.
• DELETE_SIMULATION_PLAN — Removes a simulation plan and its dependent records, typically after a scenario has been evaluated or discarded.
• COPY_VISITS_TO_PLAN — Copies existing visits into a target simulation plan, enabling rapid scenario construction by reusing established visit data.
• REMOVE_VISITS_FR_PLAN — Detaches visits from a simulation plan without deleting the underlying visit records.
• TOGGLE_SIMULATION_DELETE — Flips the deletion or active status flag on a simulation plan, supporting logical rather than physical removal.
• SET_PLAN_AS_PRIMARY — Designates a given simulation plan as the primary plan, likely affecting which plan drives downstream scheduling decisions.
• SET_VISIT_AS_PRIMARY — Marks a specific visit as primary within its plan context, controlling which visit version is authoritative.
• DELETE_SIMUL_VISITS — Performs a bulk removal of simulated visits, including associated visit tasks and links.

Tables Accessed

The package reads and writes the master simulation plan tables AHL_SIMULATION_PLANS_B and its _S sequence table alongside AHL_SIMULATION_PLANS_VL and AHL_SIMULATION_PLANS_PKG. Visit-level data is managed through AHL_VISITS_B, AHL_VISITS_B_S, AHL_VISITS_VL, and AHL_VISITS_PKG, while visit tasks and their relationships are handled via AHL_VISIT_TASKS_B, AHL_VISIT_TASKS_B_S, AHL_VISIT_TASKS_VL, AHL_VISIT_TASKS_PKG, and AHL_TASK_LINKS/AHL_TASK_LINKS_S. Resource and space planning relies on AHL_SPACE_ASSIGNMENTS, AHL_SPACE_ASSIGNMENTS_S, AHL_UNIT_EFFECTIVITIES_B, and AHL_DEPARTMENT_SHIFTS_V. The visit workflow and stage logic draws on AHL_VWP_STAGES_B, AHL_VWP_STAGES_B_S, AHL_VWP_STAGES_VL, AHL_VWP_STAGES_PKG, AHL_VWP_RULES_PVT, AHL_VWP_TASKS_PVT, AHL_VWP_TIMES_PVT, AHL_VWP_VISITS_PVT, and AHL_VWP_VISITS_STAGES_PVT. Supporting master data includes CSI_ITEM_INSTANCES, CS_INCIDENTS_ALL_B, CS_INCIDENT_TYPES_VL, MTL_SYSTEM_ITEMS_KFV, MTL_SYSTEM_ITEMS_B_KFV, MTL_ITEM_LOCATIONS_KFV, HR_ORGANIZATION_UNITS, ORG_ORGANIZATION_DEFINITIONS, and AHL_MR_HEADERS_VL.

Usage Notes

This package is invoked indirectly through the public API AHL_LTP_SIMUL_PLAN_PUB and is referenced by two other database objects. In practice, it is called from the CMRO Simulation Workbench or equivalent planning forms, and from concurrent programs or custom PL/SQL used to clone, evaluate, or clean up simulation plans. Planners use it when building alternate maintenance schedules, copying real visits into a scenario, or promoting a chosen plan to primary status. Direct calls are not recommended; FND_GLOBAL and MO_GLOBAL context initialization is expected to be in place before invocation.