Search Results pa_purge_projects




Overview
Explore in AI Chat

Overview

PA_PURGE_PROJECTS is a transaction table in the Oracle Projects (PA) schema that records the set of projects queued for processing within a single project purge batch. It acts as the working manifest for the Purge Projects concurrent program, capturing each project selected for purge or archive together with the disposition flags and status transitions applied to that project during the batch run. The table is owned by the PA schema and is classified as VALID in EBS 12.1.1 and 12.2.2.

From a dimensional modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. The composite primary key (PURGE_BATCH_ID, PROJECT_ID) identifies each row as an intersection between a purge batch and a project, while the surrounding columns carry the descriptive and state-transition attributes that change as the batch executes. Modelers using a Data Vault approach would likely treat this as a satellite attached to a link between the purge batch and the project hub, rather than as a standalone hub.

Key Information Stored

The table contains 25 documented columns. The most operationally significant are:

The unique index PA_PURGE_PROJECTS_U1 (PURGE_BATCH_ID, PROJECT_ID) mirrors the primary key and is the natural business-key candidate. The surrogate primary key is PA_PURGE_PROJECTS_PK on the same two columns; when querying, the composite pair, not a single sequence-generated value, is the reliable access path.

Common Use Cases and Queries

Typical reporting requirements include verifying which projects were processed by a given purge batch, confirming whether actuals, budgets, capital, or summary data were archived versus purged, and diagnosing errors raised during processing.

Retrieve all projects in a batch:

  • SELECT project_id, last_project_status_code, purge_project_status_code, purged_date FROM pa_push_projects WHERE purge_batch_id = :batch_id;

Identify archive-versus-purge decisions for cost data:

  • SELECT project_id, purge_actuals_flag, archive_actuals_flag, purge_budgets_flag, archive_budgets_flag, txn_to_date FROM pa_purge_projects WHERE purge_batch_id = :batch_id;

Trace failures for a batch by joining to PA_PURGE_PROJECT_ERRORS on both PURGE_BATCH_ID and PROJECT_ID, or examine row-level progress by joining PA_PURGE_PROJECT_DETAILS on the same pair. Concurrent program troubleshooting commonly inspects REQUEST_ID to correlate rows with the log and output files of the Purge Projects request.

Related Objects

  • PA_PURGE_BATCHES_ALL – Referenced through PURGE_BATCH_ID; holds batch header information.
  • PA_PROJECTS_ALL – Referenced through PROJECT_ID; the master project definition.
  • PA_PROJECT_STATUSES – Referenced by LAST_PROJECT_STATUS_CODE, NEXT_P_PROJECT_STATUS_CODE, and NEXT_PP_PROJECT_STATUS_CODE.
  • PA_PURGE_PROJECT_DETAILS – Child table keyed by PURGE_BATCH_ID and PROJECT_ID; stores detail rows about purged objects.
  • PA_PURGE_PROJECT_ERRORS – Child table keyed by PURGE_BATCH_ID and PROJECT_ID; captures error conditions encountered for a project in the batch.
  • PA_PURGE_PROJECTS_PK / PA_PURGE_PROJECTS_U1 – The primary key constraint and unique index enforcing uniqueness on (PURGE_BATCH_ID, PROJECT_ID).