Results for “pa_purge_summary”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_PURGE_SUMMARY is an Oracle EBS Projects (PA) schema package owned by APPS that supports the purge of project summary and accumulation data. In the Oracle Projects architecture, transactional detail is periodically rolled up into summarized accumulation tables to support reporting, burdening, and period-close processing. Over time these accumulated balances inflate the size of the PA schema, particularly after projects are closed or archived. PA_PURGE_SUMMARY provides the internal purge logic used by the higher-level PA_PURGE package to remove obsolete rows from these summary structures. It is classified as an OTHER API, meaning it is an internal worker package rather than a public, supported extension interface. Its principal entry point, PA_SUMMARY_MAIN_PURGE, orchestrates deletion against both the live accumulation tables and their associated archive (suffix _AR) counterparts, ensuring that accumulated actuals, budgets, commitments, headers, resource detail, and transaction accumulations are cleaned consistently. The package is registered as VALID in the ETRM registry and depends on the SYS.STANDARD package supplied by the PL/SQL runtime. It is referenced directly by PA_PURGE and is also referenced by one other package, confirming its role as a subordinate utility rather than a top-level driver.

Key Procedures and Functions

The documented interface consists of a single program unit:

• PA_SUMMARY_MAIN_PURGE — The main purge routine for project summary data. This procedure encapsulates the deletion logic applied to accumulated project totals. Because the package is invoked as part of the larger purge operation, this routine typically accepts a project identifier or purge run context and processes the related accumulation records as a set. Parameter lists are not published in the ETRM metadata and should not be assumed; callers should treat this as an internal routine rather than a documented programmatic API.

Tables Accessed

The package operates against the principal Oracle Projects accumulation tables and their archive mirrors. These include:

• PA_PROJECT_ACCUM_ACTUALS and PA_PRJ_ACCUM_ACTUALS_AR — accumulated actual cost and quantity balances.
• PA_PROJECT_ACCUM_BUDGETS and PA_PRJ_ACCUM_BUDGETS_AR — accumulated budgetary balances.
• PA_PROJECT_ACCUM_COMMITMENTS and PA_PRJ_ACCUM_COMMIT_AR — accumulated commitment balances.
• PA_PROJECT_ACCUM_HEADERS and PA_PRJ_ACCUM_HEADERS_AR — header rows that key the accumulation sets.
• PA_RESOURCE_ACCUM_DETAILS and PA_RES_ACCUM_DETAILS_AR — resource-level accumulated detail.
• PA_TXN_ACCUM, PA_TXN_ACCUM_AR, and PA_TXN_ACCUM_DETAILS, PA_TXN_ACCUM_DETAILS_AR — transaction accumulation and its detail, in both live and archived form.

The consistent pairing of live and _AR tables indicates that the package purges both current summary balances and previously archived copies in a single logical operation, which prevents orphaned accumulation rows from remaining after a project or period is retired.

Usage Notes

PA_PURGE_SUMMARY is not designed to be called directly from forms, concurrent programs, or custom extensions. It is invoked indirectly through the PA_PURGE package, which is the user-facing purge driver associated with Oracle Projects housekeeping and archive-and-purge concurrent processes (such as the Projects Purge and related maintenance programs). Administrators should schedule purges through the standard Oracle Projects concurrent program interface rather than attempting to execute PA_SUMMARY_MAIN_PURGE or PA_PURGE manually. Because the routine performs physical deletes on high-volume accumulation and archive tables, it should only be run after projects are closed and after confirming that required reporting and reconciliation data have been archived. The operation is resource-intensive and should be scheduled in low-activity windows, with adequate undo tablespace and redo capacity. Custom code referencing these tables for reporting should account for the fact that accumulation data may be purged once a project is retired.