Search Results create_ac_ent_rollup

Overview

APPS.PJI_FM_PLAN_CAL_RLPS is a PL/SQL package in Oracle E-Business Suite that supports the Projects Intelligence module, serving as the calendar rollup engine for project financial management data. Its principal business function is to aggregate actuals, commitments, and plan (forecast) amounts into the various time calendars used across Oracle Projects and Oracle General Ledger — specifically the Project Accounting (PA) calendar, the General Ledger (GL) calendar, and the Enterprise (ENT) calendar.

The package operates on two distinct data categories. The "AC" family of procedures handles Actuals and Commitments calendar rollups, while the "FP" family handles Plans calendar rollups for both primary and secondary slices. This primary/secondary slice distinction allows the package to maintain aggregated plan data at different levels of project hierarchy summation, which is essential for reporting and analysis within Projects Intelligence and the Project Management Portal dashboards.

Key Procedures and Functions

The package documents 28 procedures, organized into three functional groupings.

• Actuals and Commitments rollups: CREATE_AC_PA_ROLLUP, CREATE_AC_GL_ROLLUP, and CREATE_AC_ENT_ROLLUP aggregate actual and commitment amounts into the PA, GL, and Enterprise calendars respectively. CREATE_AC_ALL_T_PRI_ROLLUP consolidates these across all calendar types with a default calendar type parameter of 'G'.
• Plans rollups (primary and secondary slices): CREATE_FP_PA_ROLLUP, CREATE_FP_GL_ROLLUP, CREATE_FP_NONTP_ROLLUP, and CREATE_FP_ENT_ROLLUP handle the public plan rollups. The primary-slice procedures — CREATE_FP_PA_PRI_ROLLUP, CREATE_FP_GL_PRI_ROLLUP, and CREATE_FP_ALL_T_PRI_ROLLUP — and their secondary-slice counterparts (CREATE_FP_PA_SEC_ROLLUP, CREATE_FP_GL_SEC_ROLLUP, CREATE_FP_ENT_SEC_ROLLUP) provide slice-specific aggregation. CREATE_FP_ALLT_PRI_AGGREGATE and CREATE_FP_ALLT_SEC_AGGREGATE produce the aggregated plan data for the two slice levels.
• Proration routines: The PRORATE_TO_ENT_* and PRORATE_TO_PAGL_* procedures prorate plan or actual amounts from one calendar to the Enterprise calendar or to the PA/GL calendars based on a defined prorating format. Variants such as PRORATE_TO_ENT_PG_PJP1_D, PRORATE_TO_ENT_PG_FPRL_D, PRORATE_TO_ENT_N_PJP1_D, and the corresponding _SE (single-ended) versions distinguish between different proration source formats and calendar types. Several of these carry a p_prorating_format parameter, added under Bug 4005006.

Tables Accessed

The package reads and writes several foundation and staging tables through APPS synonyms.

• Aggregation tables: PJI_FP_AGGR_PJP1 and PJI_AC_AGGR_PJP1 serve as the primary storage for rolled-up plan and actual/commitment amounts.
• Calendar definition tables: PJI_TIME_CAL_PERIOD, PJI_TIME_CAL_QTR, PJI_TIME_ENT_PERIOD, and PJI_TIME_ENT_QTR define the periods and quarters for the PA/GL and Enterprise calendars, driving how amounts are bucketed.
• Source and reference tables: PJI_FM_EXTR_PLNVER4 supplies extracted plan version data, PJI_ORG_EXTR_INFO provides organizational extraction context, PA_PROJECTS_ALL and PA_FIN_PLAN_TYPES_B supply project and financial plan type definitions, and FND_CURRENCIES supplies currency conversion context.

Usage Notes

PJI_FM_PLAN_CAL_RLPS is an internal Projects Intelligence engine, not a public API classification. It is typically invoked indirectly by concurrent programs and scheduled rollup processes that refresh the aggregated plan and actuals data underlying Projects Intelligence reports and portal dashboards. Because the procedures are referenced by three other packages, custom code should avoid calling rollup procedures directly and instead invoke the standard concurrent program that orchestrates them, ensuring calendar seed data and plan versions are consistent. The default parameter values — calendar type 'G' for the ALL_T rollups — indicate that callers may override the calendar type when targeting specific calendar rollups. All procedures operate against APPS-owned synonyms, so execution must occur in a context with appropriate APPS privileges.