Search Results get_post_purge_status

Overview

PA_PURGE is a core Oracle Projects PL/SQL package owned by the APPS schema. Its business purpose is to permanently remove project-related transactional and master data that is no longer required, thereby reclaiming storage and enforcing the retention policies configured for the Oracle E-Business Suite implementation. The package operates as the central purge engine for the Projects foundation and is classified by Oracle's ETRM repository as an OTHER API rather than a public, supported extension interface. In Oracle EBS 12.1.1 and 12.2.2 the package remains VALID and retains the same procedure surface, so purge behavior is consistent across both releases.

PA_PURGE is the hub of a family of dependent purge programs. It references only SYS.STANDARD directly, but it is referenced by eight sibling packages — PA_PURGE_BILLING, PA_PURGE_CAPITAL, PA_PURGE_COSTING, PA_PURGE_ICIP, PA_PURGE_PJR_TXNS, PA_PURGE_SUMMARY, PA_PURGE_UNASGN_FI, and PA_PAXARPPR_XMLP_PKG — each of which purges a specific transaction class. This architecture lets the parent package orchestrate an end-to-end purge across all Projects subledgers.

Key Procedures and Functions

• PURGE — The main entry point. It validates purge eligibility for the selected project set and drives the deletion of project records and their dependents.
• PURGE_PROJECT — Performs purge processing for a single project, coordinating the work handed off to the subordinate transaction-specific purge packages.
• COMMITPROCESS — Manages commit boundaries during long-running purge executions, allowing work to be committed incrementally rather than in one large transaction.
• GET_POST_PURGE_STATUS — Returns the status resulting from a purge run, enabling the caller (typically a concurrent program or its XML Publisher report) to confirm success or diagnose failure.

The package exposes four documented procedures in total. Their parameter lists are defined in the ETRM metadata and should be read from the database rather than assumed for any custom invocation.

Tables Accessed

PA_PURGE reads and writes the following applications tables through APPS synonyms:

• PA_IMPLEMENTATIONS — Supplies implementation-level settings that determine which purge behaviors are active for the operating unit or business group.
• PA_PROJECTS_ALL — The base project definition table; candidate projects are identified and ultimately deleted here.
• PA_PROJECT_TYPES_ALL — Provides project type attributes that govern whether a given project is eligible for purge.
• PA_PURGE_BATCHES — Records each purge batch, tracking the batch identifier and its processing state.
• PA_PURGE_PRJ_DETAILS — Stores per-project detail rows belonging to a purge batch, capturing the outcome for each project processed.
• PA_PURGE_PROJECTS — Holds the list of projects selected for purging and drives iteration within PURGE_PROJECT.

Usage Notes

PA_PURGE is normally invoked indirectly. In Oracle Projects it is driven by the concurrent program "PRC: Purge Projects" and by related purge concurrent requests for billing, costing, capital, and intercompany transactions, all of which call into this package and its sibling routines. Because it is classified as an OTHER API, it is not part of Oracle's formally supported public interface, and custom code should not call it directly. The recommended approach is to submit the shipped concurrent programs, which handle batch creation, eligibility validation, commit processing, and status reporting. Direct invocation risks leaving the PA_PURGE_* audit tables in an inconsistent state and bypassing the referential checks that keep Projects data internally consistent. Organizations extending purge behavior should use the supported concurrent programs and rely on GET_POST_PURGE_STATUS output for verification.