Search Results validate_set_pr_params




Overview

APPS.PJI_FM_PLAN_MAINT_PVT is a private (PVT) PL/SQL package in the Oracle EBS Projects (PA/PJI) schema that supports the maintenance and staging of financial plan data used by Project Resource Management and Project Financial Management. Its core responsibility is the extraction and preparation of plan amounts, effort, and version data from source planning structures into the fact tables and denormalized structures that drive financial plan rollups, RBS-based reporting, and slicing. The package is part of the extract-and-rollup infrastructure that moves plan information from RBS (Resource Breakdown Structure) planning constructs into the financial plan fact and resource map tables.

The package is classified as PVT, meaning it is an internal API not intended for direct customer invocation. It is referenced by four other packages within the EBS codebase, indicating that it functions as a shared implementation layer for higher-level public APIs and concurrent programs that manage financial plan versions and plan amounts. The header identifies the file as PJIPP02S.pls and carries a version stamp from the 12.0.0 development line, consistent with its presence in both 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

Tables Accessed

The package reads and writes through APPS synonyms across planning, RBS, and parallel-processing tables. Planning and version data is sourced from PA_BUDGET_LINES, PA_BUDGET_VERSIONS, and PA_PROJ_ELEMENT_VERSIONS. RBS structures are held in PA_RBS_DENORM, PA_RBS_PRJ_ASSIGNMENTS, PA_RBS_TXN_ACCUM_MAP, and PA_RBS_VERSIONS_B. Project and resource context comes from PA_PROJECTS_ALL, PA_RESOURCE_ASSIGNMENTS, PA_PROJ_ELEM_VER_STRUCTURE, PA_PROJ_FP_OPTIONS, and PA_FIN_PLAN_TYPES_B. Parallel processing is coordinated through AD_PARALLEL_UPDATES, AD_PARALLEL_UPDATE_UNITS, and AD_PARALLEL_WORKERS, enabling large plan extractions to be distributed across workers.

Usage Notes

As a PVT package, PJI_FM_PLAN_MAINT_PVT is not exposed to end users or directly callable from standard forms. It is invoked by the EBS financial plan extraction and rollup framework, including the concurrent programs that generate and refresh financial plan versions and their associated amounts. The GLC12 extraction procedures are typically reached through the plan version generation process, where the pull-dangling flag defaults to 'Y' so that reversal amounts are computed during extraction. Custom development should avoid direct use of this package; supported integration points are the public PA APIs. DBAs troubleshooting plan extraction issues may trace into this package's procedures to follow the flow from version extraction through amount staging, fact-table merge, and RBS rollup.