Search Results g_progress_commit_size




Overview

APPS.PJI_PJP_SUM_ROLLUP is a PL/SQL package within the Oracle EBS Project and Portfolio Management (PJI) module that supports the Project Performance and Progress reporting infrastructure. Its principal responsibility is to manage snapshot generation, event processing, denormalization of reporting structures, and aggregation and rollup of financial plan and actual cost slices used by project summarization and reporting engines.

The package is heavily oriented toward the maintenance of the Reporting Business Structure (RBS) and the associated denormalized tables that support efficient retrieval of project performance data. It operates closely with project events logging, financial plan versioning, and slice aggregation mechanisms. Objects in this package are invoked primarily during refresh, rollup, and summarization cycles that occur when underlying project structures, financial plan versions, or RBS assignments change. The extract_fin_plan_vers_bulk query that surfaced this package relates to extracting financial plan versions in bulk, which is consistent with the package's slice aggregation and MARK_EXTRACTED_PROJECTS behavior.

Key Procedures and Functions

Tables Accessed

The package reads and writes a broad set of PA foundation tables. PA_BUDGET_VERSIONS and PA_FIN_PLAN_TYPES_B provide plan version and plan type context. Project and structure definitions come from PA_PROJECTS_ALL, PA_PROJ_ELEMENTS, PA_PROJ_ELEMENT_VERSIONS, PA_PROJ_ELEM_VER_STRUCTURE, PA_PROJ_STRUCTURE_TYPES, and PA_PROJ_WORKPLAN_ATTR. Event tracking uses PA_PJI_PROJ_EVENTS_LOG and its sequence PA_PJI_PROJ_EVENTS_LOG_S. Reporting structures are maintained through PA_RBS_DENORM, PA_RBS_PRJ_ASSIGNMENTS, and PA_RBS_TXN_ACCUM_MAP. Commitment data comes from PA_COMMITMENT_TXNS, and options are read from PA_PROJ_FP_OPTIONS.

Usage Notes

PJI_PJP_SUM_ROLLUP is an internal package invoked by concurrent programs and by other PA packages. It is referenced by seven other packages and expects a p_worker_id parameter to coordinate parallel processing. It is not intended for direct customer invocation; customizations should integrate via supported APIs rather than calling its procedures directly. The G_PROGRESS_COMMIT_SIZE constant of 10 indicates commit frequency management during long-running rollups.