Search Results pa_purge_project_errors




Overview
Explore in AI Chat

Overview

PA_PURGE_PROJECT_ERRORS is a Projects (PA) module table that stores validation errors encountered for individual projects during a project purge batch. When the Oracle EBS Purge Projects process executes, it evaluates each project in a purge batch against a series of business and referential integrity rules. Projects that fail validation are recorded here by batch and project, with an associated error code classifying the failure. The table therefore acts as the diagnostic audit trail for the purge process, allowing users to diagnose why a specific project could not be purged and to take corrective action before resubmitting the batch.

From a dimensional modeling perspective, the Data Vault classification derived heuristically from the foreign key structure is satellite-leaning. This suggests the table is best modeled as a satellite attached to a purge batch and project hub or link, holding descriptive error attributes that change with each purge execution rather than acting as an independent business entity.

Key Information Stored

The documented physical schema contains nine columns. The most significant are described below.

  • PURGE_BATCH_ID — Identifier of the purge batch run, foreign key to PA_PURGE_PROJECTS. Part of the composite primary key.
  • PROJECT_ID — Identifier of the project that failed validation. Part of the composite primary key.
  • ERROR_CODE — Code identifying the specific validation failure. Part of the composite primary key and the unique index.
  • ERROR_TYPE — Classification of the error, distinguishing categories of validation failure.
  • CREATED_BY — User who created the error record.
  • CREATION_DATE — Date the error record was created.
  • LAST_UPDATED_BY — User who last modified the record.
  • LAST_UPDATE_DATE — Date of the most recent update.
  • LAST_UPDATE_LOGIN — Login session associated with the last update.

The surrogate primary key is PA_PURGE_PROJECT_ERRORS_PK, defined on (PURGE_BATCH_ID, PROJECT_ID, ERROR_CODE). A unique index, PA_PURGE_PROJECT_ERRORS_U1, exists on the same three columns, making this triple the documented business-key candidate that guarantees one row per error per project per batch. The table references PA_PURGE_PROJECTS on PURGE_BATCH_ID.

Common Use Cases and Queries

Primary use cases include diagnosing failed purges, auditing purge history, and reporting on recurring validation issues. A typical query retrieves all errors for a given batch:

  • SELECT purge_batch_id, project_id, error_code, error_type FROM pa.pa_purge_project_errors WHERE purge_batch_id = :batch_id;
  • SELECT project_id, error_code, COUNT(*) FROM pa.pa_purge_project_errors GROUP BY project_id, error_code ORDER BY 3 DESC;
  • SELECT p.project_number, e.error_code FROM pa.pa_purge_project_errors e JOIN pa.pa_projects p ON p.project_id = e.project_id WHERE e.purge_batch_id = :batch_id;

Reporting commonly joins to PA_PURGE_PROJECTS for batch-level context and to PA_PROJECTS for human-readable project identifiers.

Related Objects

The table integrates with the following significant objects:

  • PA_PURGE_PROJECTS — Parent table referenced via PURGE_BATCH_ID; holds the purge batch and project selection records.
  • PA_PROJECTS — Master project definition joined via PROJECT_ID to resolve project numbers and names.
  • PA_PURGE_PROJECT_ERRORS_PK — Composite primary key constraint enforcing uniqueness.
  • PA_PURGE_PROJECT_ERRORS_U1 — Unique index reinforcing the business key.
  • PA Purge Projects concurrent program — Populates this table during validation.

Together these objects support the end-to-end purge validation and remediation workflow within the Projects module.