Search Results pa_purge_project_errors_u1

Overview

PA.PA_PURGE_PROJECT_ERRORS is a transactional table in the Oracle E-Business Suite Projects (PA) schema that stores validation and processing errors encountered during a project purge run. It serves as the diagnostic record for the Project Purge concurrent program, capturing the specific reasons a given project could not be purged from a given batch. Each row associates a purge batch, a project, and an error code, forming the granular error log that administrators review when a purge does not complete as expected.

Under the heuristic Data Vault classification supplied in the metadata, this object is characterized as satellite-leaning. In modeling terms, this suggests the table behaves primarily as a descriptive satellite anchored to the purge batch (and secondarily to the project), holding attributes that describe the outcome of a purge attempt rather than acting as an independent hub or as a pure associative link between two hubs.

Key Information Stored

The table contains nine documented columns. The mandatory identifiers are the most important:

• PURGE_BATCH_ID (NUMBER 15, mandatory) — the unique identifier of the purge batch in which the error occurred; a foreign key to PA_PURGE_PROJECTS.
• PROJECT_ID (NUMBER 15, mandatory) — the identifier of the project that failed validation or processing for the batch.
• ERROR_CODE (VARCHAR2 30, mandatory) — the validation error code produced for the failure.
• ERROR_TYPE (VARCHAR2, optional) — the category or type of the validation error, providing classification of the failure.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS who columns recording audit and concurrency context.

The primary key is PA_PURGE_PROJECT_ERRORS_PK, defined on (PURGE_BATCH_ID, PROJECT_ID, ERROR_CODE). The unique index PA_PURGE_PROJECT_ERRORS_U1 carries the same three columns and is the business-key candidate that prevents duplicate error rows for the same batch, project, and error code. The surrogate identity of a row is therefore the (batch, project, error code) combination rather than any single generated column.

Common Use Cases and Queries

The primary use case is diagnosing why a project purge run reported failures. Support and functional teams query this table by batch to list the offending projects and their error codes, then cross-reference the error code against the Project Purge documentation or validation logic to determine corrective action.

• Listing all errors for a specific purge batch:

  SELECT PROJECT_ID, ERROR_CODE, ERROR_TYPE
  FROM   PA.PA_PURGE_PROJECT_ERRORS
  WHERE  PURGE_BATCH_ID = :batch_id
  ORDER BY PROJECT_ID, ERROR_CODE;

• Identifying all projects that failed a purge with a particular error code across batches, using the unique index columns as the driving predicate.
• Aggregate reporting to count error occurrences by ERROR_TYPE per batch, supporting purge health metrics.

Because the table is keyed on PURGE_BATCH_ID, PROJECT_ID, and ERROR_CODE, joining it to the parent batch table on PURGE_BATCH_ID yields a complete batch-to-error report.

Related Objects

The documented foreign key relationship anchors this table to the purge batch header. Significant related objects include:

• PA.PA_PURGE_PROJECTS — the parent batch/project table; PA_PURGE_PROJECT_ERRORS.PURGE_BATCH_ID references it, providing the master purge run context.
• APPS.PA_PURGE_PROJECT_ERRORS — the APPS synonym or view layer through which the table is typically accessed.

Join patterns consistently proceed from the batch header down to this error detail using PURGE_BATCH_ID, and optionally PROJECT_ID when reconciling a specific project across a batch.