Search Results check_accum_res_tasks




Overview

PA_MAINT_PROJECT_ACCUMS is an Oracle EBS Projects (PA) maintenance package responsible for building and refreshing the project accumulation tables. These tables (PA_PROJECT_ACCUM_ACTUALS, PA_PROJECT_ACCUM_BUDGETS, and PA_PROJECT_ACCUM_COMMITMENTS) store summarized project, task, and resource-level amounts used by Project Status Inquiry, project reporting, and period-close summarization.

The package operates against the accumulation model rather than the transaction model, reading raw summarized transaction data from PA_TXN_ACCUM and rolling it up into the hierarchical accumulation structures. Its header history shows a lineage of fixes spanning rollup logic, performance tuning, WBS level inclusion (bug 1265148), GL/PA period coordination, and comparative period processing (bug 2753251), reflecting its central role in period processing.

The user-searched procedure CHECK_ACCUM_RES_TASKS is one of the package's validation routines, supporting the decision of whether resource/task accumulation work is required before the heavier rollup procedures execute.

Key Procedures and Functions

The documented 15 procedures and functions form a clear processing pipeline:

Tables Accessed

The package reads transaction accumulation and configuration data and writes the accumulation result tables:

Usage Notes

PA_MAINT_PROJECT_ACCUMS is invoked as part of the Projects period processing and summarization flow, typically from concurrent programs that maintain project accumulations rather than from a directly exposed form. It is referenced by four other packages in the APPS schema, indicating it is called programmatically by higher-level period process or summarization drivers such as period process/close programs.

Because the package coordinates PA and GL periods and supports comparative period processing, custom code invoking it must ensure the correct implementation option and application context are set. Oracle's recorded fixes emphasize that the PA vs. GL period distinction and WBS level ordering are critical to correct PTD/ITD results, so integrators should avoid bypassing the package's validatating checks such as CHECK_ACCUM_RES_TASKS and CHECK_ACCUM_WBS when triggering accumulation manually.