Search Results initialize_parent_level

Overview

PA_MAINT_PROJECT_ACCUMS is a core PL/SQL package in the Oracle EBS Project Accounting (PA) module, owned by the APPS schema and shipped in a VALID state in both release 12.1.1 and 12.2.2. Its purpose is to build, maintain, and refresh the project accumulation tables that store summarized actual, budget, and commitment balances at the project, task, and resource level. These accumulation tables — PA_PROJECT_ACCUM_ACTUALS, PA_PROJECT_ACCUM_BUDGETS, and PA_PROJECT_ACCUM_COMMITMENTS — are the repository from which Project Accounting reporting, project status inquiry, and downstream costing and revenue processes draw their summarized figures.

Rather than recalculating balances from raw transaction and distribution detail on every query, Oracle maintains persistent accumulators. PA_MAINT_PROJECT_ACCUMS is the maintenance engine that initializes those accumulator rows, rolls amounts up from the lowest task and resource level to parent tasks and to the project level, and prepares transaction-level accumulation records. In the ETRM 12.2.2 metadata the package is classified as OTHER and exposes 15 documented procedures and functions, indicating it is an internal engine invoked by other PA packages rather than a public application programming interface.

Key Procedures and Functions

The documented entry points divide into three logical groups:

• Transaction accumulation: PROCESS_TXN_ACCUM and CREATE_ACCUM_ACTUALS handle the creation and processing of actual cost accumulation records from source transactions; CREATE_ACCUM_ACTUALS_RES performs the same role at the resource dimension.
• Validation and task resolution: CHECK_ACCUM_RES_TASKS and CHECK_ACCUM_WBS validate whether accumulation is required for a given resource/task or WBS combination; GET_ALL_HIGHER_TASKS returns the full set of ancestor tasks above a given task so amounts can be propagated upward.
• Initialization and rollup: INITIALIZE_ACTUALS, INITIALIZE_BUDGETS, and INITIALIZE_COMMITMENTS prepare accumulator rows for the three balance types; INITIALIZE_TASK_LEVEL, INITIALIZE_PARENT_LEVEL, and INITIALIZE_PROJECT_LEVEL establish row structures at each hierarchy tier; ADD_PARENT_AMOUNTS and ADD_PROJECT_AMOUNTS perform the arithmetic that rolls child balances into parent tasks and the project header respectively. INSERT_HEADERS_TASKS populates accumulation header and task combinations.

Tables Accessed

The package reads and writes the accumulator tables it maintains — PA_PROJECT_ACCUM_ACTUALS, PA_PROJECT_ACCUM_BUDGETS, PA_PROJECT_ACCUM_COMMITMENTS, PA_PROJECT_ACCUM_HEADERS, PA_PROJECT_ACCUM_HEADERS_S, and PA_RESOURCE_ACCUM_DETAILS. PA_TXN_ACCUM holds intermediate transaction accumulation data consumed when building actuals. PA_TASKS supplies the project task hierarchy used by GET_ALL_HIGHER_TASKS and the rollup routines. PA_BUDGET_VERSIONS identifies valid budget versions for budget accumulation. PA_RESOURCES, PA_RESOURCE_LIST_ASSIGNMENTS, and PA_RESOURCE_LIST_MEMBERS resolve resource list membership so amounts can be accumulated at resource level. GL_PERIODS provides accounting period context, and PA_IMPLEMENTATIONS supplies installation-level settings. DUAL supports simple scalar queries.

Usage Notes

PA_MAINT_PROJECT_ACCUMS is referenced by four other packages — PA_MAINT_PROJECT_BUDGETS, PA_PROCESS_ACCUM_COMMITMENTS, PA_PROJ_ACCUM_MAIN, and PA_REFRESH_RES_LISTS — and the package itself appears in its own dependency list for internal calls. In practice it is invoked indirectly through those drivers, which are themselves triggered by Project Accounting concurrent programs such as PRC: Maintain Project Accumulations, and by the accumulation logic that runs when transactions are costed, when budgets are baselined, and when commitment balances are refreshed. Because the routines are not designed as a supported public interface, customizations should call the higher-level accumulation driver programs or the documented PA APIs rather than invoking PA_MAINT_PROJECT_ACCUMS procedures directly. Any custom code that does call it must respect the initialization-before-rollup sequence: accumulator rows must be initialized at task, parent, and project level before parent and project amounts are added.