Search Results check_ver3_not_empty

Overview

The APPS.PJI_FM_PLAN_MAINT package is a PL/SQL maintenance package within the Oracle E-Business Suite Project Intelligence (PJI) module. Its primary business function is to manage and maintain project financial plan data used by the Project Intelligence reporting and extraction infrastructure. The package is responsible for creating, updating, and deleting "primary" and "secondary" plan records that feed the financial aggregation and extraction tables (such as PJI_FM_AGGR_FIN7 and PJI_FM_AGGR_FIN8) used by the PJI analytics engine.

In Oracle EBS 12.1.1 and 12.2.2, this package is classified as OTHER (rather than a public API) and is a supporting internal utility. It is owned by the APPS schema and is documented in ETRM as VALID. The package is referenced by several other PJI packages, including PJI_FM_PLAN_MAINT_T_PVT, PJI_FM_XBS_ACCUM_MAINT, PJI_PJP_EXTRACTION_UTILS, and PJI_PJP_SUM_ROLLUP, indicating that it acts as a foundational layer in the PJI financial plan maintenance and extraction pipeline.

Key Procedures and Functions

ETRM documents a total of 12 procedures and functions within PJI_FM_PLAN_MAINT. The principal entries are:

• MAP_RESOURCE_LIST — Maps resource lists used in the planning process, establishing the association between resources and their corresponding plan structures.
• CREATE_PRIMARY_PVT and CREATE_PRIMARY_UPGRD_PVT — Create primary plan records; the upgraded variant supports migration or upgrade scenarios where existing plan data is converted to the current structure.
• CREATE_SECONDARY_PVT and CREATE_SECONDARY_T_PVT — Create secondary plan records, with the _T_ variant likely operating against a temporary or translated staging table.
• DELETE_ALL_PVT — Removes all plan records maintained by this package, typically invoked before a full rebuild.
• UPDATE_PRIMARY_PVT and UPDATE_PRIMARY_PVT_ACT_ETC — Update primary plan records; the second variant updates actual and estimated-to-complete (ETC) amounts.
• POPULATE_FIN8 — Populates the PJI_FM_AGGR_FIN8 aggregation table, a key step in the PJI summarization process.
• PULL_PLANS_FOR_PR — Pulls plan data for a given project (or project range) into the maintenance structures.
• GET_ACTUALS_SUMM — Retrieves summarized actual amounts for use in plan maintenance calculations.
• CHECK_VER3_NOT_EMPTY — Validates that the Version 3 extraction table (PJI_FM_EXTR_PLNVER3_T) contains data before proceeding with dependent processing.

Tables Accessed

The package operates against a wide set of project planning and financial tables accessed via APPS synonyms. Core transactional and setup tables include PA_BUDGET_VERSIONS and PA_FIN_PLAN_TYPES_B, which define the plan versions and financial plan types this package maintains. Structural definitions are read from PA_PROJ_ELEM_VER_STRUCTURE, PA_RBS_PRJ_ASSIGNMENTS, and PA_PROJ_FP_OPTIONS. The denormalized PA_XBS_DENORM and accumulating tables PJI_FP_TXN_ACCUM and PJI_FP_XBS_ACCUM_F supply transactional and cross-business-summary amounts.

Aggregation and extraction outputs are written to PJI_FM_AGGR_FIN7, PJI_FM_AGGR_FIN8, PJI_FM_EXTR_PLNVER3_T, and PJI_FM_EXTR_PLNVER4. Batch and staging control is handled through PJI_PJP_PROJ_BATCH_MAP, PJI_PJP_RBS_HEADER, and the event log PA_PJI_PROJ_EVENTS_LOG.

Usage Notes

This package is invoked internally by higher-level PJI packages rather than directly by end users. It is typically triggered during PJI financial plan maintenance cycles, when plan versions are populated, updated, or regenerated for Project Intelligence reporting. POPULATE_FIN8 and the extraction-related procedures are commonly invoked from concurrent programs that rebuild the PJI aggregation tables. Because it is classified as non-public (OTHER) and is referenced by PJI_PJP_EXTRACTION_UTILS and PJI_PJP_SUM_ROLLUP, customizations should avoid calling it directly; instead, invoke the supported PJI concurrent processes that drive it. Developers requiring custom plan maintenance should first verify the signature against the actual 12.1.1 / 12.2.2 database, since ETRM does not publish parameter lists for this package.