Search Results copy_visits_to_plan

Overview

APPS.AHL_LTP_SIMUL_PLAN_PVT is a private PL/SQL API belonging to the Advanced Services (AHL) product family in Oracle E-Business Suite, specifically the Advanced Services Online module that supports field service and depot repair planning. The package is declared with AUTHID CURRENT_USER, meaning that its SQL statements execute with the privileges of the invoking user rather than the package owner, a convention typical of private APIs called from within the APPS schema context.

The package manages Simulation Plan information. Simulation plans in Advanced Services Online allow planners to model hypothetical service scenarios — combinations of visits, tasks, resources, and space assignments — without committing those changes to the live plan. A simulation plan can be designated as a primary plan, and individual simulation visits can likewise be flagged as primary, enabling side-by-side comparison of alternative scheduling or resource strategies before promotion to production.

The header comment documents the object as a Private API, indicating it is not intended for direct customer invocation. Its procedures are surfaced to end users through the Advanced Services Online forms and through other AHL packages; the metadata indicates the package is referenced by two other packages, which act as the public entry points.

Key Procedures and Functions

The documented API surface comprises nine procedures:

• CREATE_SIMULATION_PLAN — Inserts a new simulation plan header, populating the simulation plan record with its name, description, primary plan flag, descriptive flexfield attributes, and audit columns.
• UPDATE_SIMULATION_PLAN — Modifies an existing simulation plan's attributes, including the primary plan flag and DFF segments.
• DELETE_SIMULATION_PLAN — Removes a simulation plan, presumably together with its dependent visit and task data.
• COPY_VISITS_TO_PLAN — Copies visits from a source context into a simulation plan, the core mechanism for seeding a what-if scenario.
• REMOVE_VISITS_FR_PLAN — Removes selected visits from a simulation plan without deleting the underlying visit records.
• TOGGLE_SIMULATION_DELETE — Controls or toggles delete behavior for simulation plan entities, likely an internal flag manipulator supporting cascading or soft-delete semantics.
• SET_PLAN_AS_PRIMARY — Marks a given simulation plan as the primary plan, demoting any previously primary plan.
• SET_VISIT_AS_PRIMARY — Marks a specific simulation visit as primary within its plan, supporting comparison between alternative visit configurations.
• DELETE_SIMUL_VISITS — The procedure matching the user's search term. It deletes simulation visits, and is the targeted routine for removing one or more visits that belong to a simulation plan.

Tables Accessed

The package reads and writes a broad set of AHL and CSI tables through APPS synonyms:

• AHL_SIMULATION_PLANS_B and _S — the base and translation tables holding simulation plan headers.
• AHL_VISITS_B and _S, AHL_VISIT_TASKS_B and _S — visit and visit-task definitions copied into or removed from simulation plans.
• AHL_TASK_LINKS and _S — relationships and sequencing between tasks.
• AHL_SPACE_ASSIGNMENTS and _S — the space (bay, dock, or stall) allocations that simulation plans model.
• AHL_UNIT_EFFECTIVITIES_B — effective dating of units within a plan.
• AHL_VWP_STAGES_B and _S — visit work package stage definitions.
• CSI_ITEM_INSTANCES — the installed base instances serviced by the simulated visits.
• CS_INCIDENTS_ALL_B — service incidents or requests driving the visit work.

Usage Notes

Because this is a PVT (private) API, it should not be called directly from custom code. It is invoked by the Advanced Services Online forms layer and by the two other AHL packages that reference it, which expose supported public entry points. Customizations requiring simulation plan manipulation should call the public wrapper rather than AHL_LTP_SIMUL_PLAN_PVT. When troubleshooting deletion of simulation visits in 12.1.1 or 12.2.2, DELETE_SIMUL_VISITS is the operative routine; failures typically trace to foreign-key dependencies in AHL_VISIT_TASKS_B, AHL_TASK_LINKS, or AHL_SPACE_ASSIGNMENTS that must be cleared first, or to the invoking user lacking privileges on the underlying tables under AUTHID CURRENT_USER semantics.