Search Results delete_version_helper

Overview

APPS.PA_FIN_PLAN_PUB is the public PL/SQL API for Oracle Project Management's financial planning functionality in Oracle E-Business Suite 12.1.1 and 12.2.2. Financial plans define planned, budgeted, and forecasted amounts at the project, task, and resource level. The package encapsulates the creation, maintenance, versioning, baselining, and deletion of plan versions and their associated plan lines, providing a stable interface that shields callers from the underlying data structures and internal packages.

The package is classified as a PUB API, indicating it is intended for external invocation by forms, concurrent programs, workflow, and custom extensions. It is a central node in the financial planning dependency graph: it references base planning tables and constants packages, and is itself referenced by seventeen other packages, including PA_BUDGET_PUB, PA_BUDGET_WF, PA_FIN_PLAN_PVT, PA_FP_ROLLUP_PKG, PA_FP_COPY_FROM_PKG, and PA_PROJECT_CORE.

Key Procedures and Functions

The documented interface exposes eighteen procedures and functions that cover the full lifecycle of a financial plan version and its planning content:

• Version creation and setup: CREATE_VERSION, CREATE_VERSION_ORGFCST, CREATE_FRESH_PERIOD_PROFILE, and CREATE_DEFAULT_PLAN_TXN_REC establish new plan versions, org forecast versions, period profiles, and default planning transaction records.
• Plan content generation: CREATE_ORG_FCST_ELEMENTS, REGENERATE, and CALL_MAINTAIN_PLAN_MATRIX build or rebuild plan element and matrix structures for a version.
• Plan line loading: INSERT_PLAN_LINES_TMP_BULK and REFRESH_RES_LIST_ASSIGNMENT support bulk staging of plan lines and refresh of resource list assignments.
• Version state management: SUBMIT_CURRENT_WORKING, SET_CURRENT_WORKING, REWORK_SUBMITTED, MARK_AS_ORIGINAL, UPDATE_VERSION, and BASELINE manage the status transitions of a plan version, including baselining the current working version.
• Version removal: DELETE_VERSION and DELETE_VERSION_HELPER perform the removal of plan versions and associated data.

The precise parameter lists for these procedures are defined in the package specification and should be reviewed in the ETRM documentation before invocation; this summary intentionally omits them.

Tables Accessed

The package reads and writes core financial planning tables through APPS synonyms. PA_BUDGET_VERSIONS and PA_BUDGET_VERSIONS_S store version headers and status. PA_BUDGET_LINES holds the budget and plan line amounts. PA_FIN_PLAN_LINES_TMP is the temporary staging table used during bulk insert and generation. PA_PROJ_ELEMENT_VERSIONS and PA_PROJ_PERIODS_DENORM hold element and period rollup data used during regeneration and matrix maintenance. PA_PROJECTS_ALL, PA_TASKS, PA_PROJ_FP_OPTIONS, and PA_AGREEMENTS_ALL supply project, task, option, and agreement context. PA_CONTROL_ITEMS and PA_FIN_PLAN_ADJ_LINES (with its _S date-tracked synonym) hold control items and adjustment lines. GL_PERIODS and GL_PERIOD_STATUSES provide the accounting period calendar used in period profile and period-denormalized processing.

Usage Notes

PA_FIN_PLAN_PUB is invoked primarily from the Oracle Project Management financial planning forms, from concurrent programs that create, copy, roll up, or baseline plan versions, and from the financial plan WebADI integration. Budget and forecast generation, workflow-driven baselining, and plan copy utilities such as PA_FP_COPY_FROM_PKG and PA_FP_ROLLUP_PKG call this API rather than manipulating the underlying tables directly. Custom extensions should follow the same practice: use the PUB procedures for version lifecycle operations, respect version status transitions, and stage plan lines through the documented temporary table before bulk insert. Because of the number of dependent packages, changes to plan version state performed through this API can trigger downstream workflow and budget processes and should be executed in the appropriate operating unit and period context.