Search Results process_simulation_visit




Overview

APPS.AHL_LTP_SIMUL_PLAN_PUB is a public PL/SQL API package within the Oracle E-Business Suite Advanced Planning and Scheduling (AHL) application, specifically belonging to the Long Term Planning (LTP) simulation feature set. The package exposes business logic for managing simulation plans and simulation visits, allowing users to model, adjust, and promote planning scenarios without affecting live production data. As a public ("PUB") API classified object, it serves as the supported entry point for external callers, while the underlying implementation is delegated to the private package AHL_LTP_SIMUL_PLAN_PVT. This separation of public and private packages is a standard Oracle EBS design pattern that stabilizes the interface while permitting internal changes.

Key Procedures and Functions

The package exposes five documented procedures/functions:

Specific parameter lists are not documented in the provided metadata and should be confirmed by inspecting the package specification in the database.

Tables Accessed

The documented table access is limited to PLITBLM, referenced through an APPS synonym. In Oracle EBS this table is a generic, multi-purpose temporary/staging structure used by various AHL planning routines. The simulation procedures likely read from and write to this table during plan and visit processing.

Usage Notes

This package is typically invoked from Oracle Forms, concurrent programs, or custom PL/SQL code that implements long term planning simulations. Because it is a public API, all calls should invoke the procedures with proper FND_API initialization and error handling. The dependency metadata shows that AHL_LTP_SIMUL_PLAN_PUB references FND_API (the standard Oracle EBS API utility package), indicating compliance with Oracle's API error-handling conventions. It is referenced by two other packages — AHL_LTP_SIMUL_PLAN_PUB_W and AHL_LTP_SIMUL_PLAN_PVT — confirming it acts as a stable interface layer wrapping the private implementation. When customizations are required, the public package should be called rather than the private one, to preserve upgradeability. As with all APPS-owned packages, direct modification is not supported; any extension should be performed through wrapper packages.