Search Results purge_batch_status

Overview

APPS.PA_PURGE_BATCHES_V is a reporting and inquiry view in Oracle EBS Projects (PA) that presents purge batch definitions alongside their decoded lookup meanings and target project statuses. A purge batch identifies a set of projects whose transactional, budgetary, capital, and summary data is to be purged and/or archived. The view joins PA_PURGE_BATCHES to PA_LOOKUPS and two aliases of PA_PROJECT_STATUSES so that coded values are surfaced as user-readable descriptions. This decoding is significant because the base purge batch table stores only the code BATCH_STATUS_CODE, while the view returns the corresponding MEANING from the PURGE_BATCH_STATUS lookup type. The view is exposed under the APPS schema and is typically consumed by concurrent programs, forms, and custom reports. Users searching for "purge_batch_status" are generally looking for the lookup that qualifies purge batch state; this view is the primary object in which that lookup is resolved for reporting.

Underlying Base Objects

Per the documented view text, the FROM clause references four objects:

• PA_PURGE_BATCHES (SYNONYM) — the driving table aliased PB, holding purge batch header data.
• PA_LOOKUPS (VIEW) — aliased L1, restricted to LOOKUP_TYPE = 'PURGE_BATCH_STATUS' to translate the batch status code.
• PA_PROJECT_STATUSES (SYNONYM) — aliased PS1 and PS2, joined on the next pre-purge and next post-purge project status codes respectively.

The three joins are enforced in the WHERE clause as inner joins, so a purge batch row is returned only when a matching PURGE_BATCH_STATUS lookup exists and both referenced project status codes resolve. The view also exposes PB.ROWID as ROW_ID, enabling row-based updates through the view in the standard Oracle Forms pattern.

Key Columns

• PURGE_BATCH_ID, BATCH_NAME, DESCRIPTION — batch identity.
• BATCH_STATUS_CODE and MEANING — the raw status code plus the decoded status from PA_LOOKUPS; this pairing is the focal point of the "purge_batch_status" search.
• ACTIVE_CLOSED_FLAG, TXN_TO_DATE — batch scope controls, including the transaction cutoff date.
• PURGE_ACTUALS_FLAG, ARCHIVE_ACTUALS_FLAG, PURGE_BUDGETS_FLAG, ARCHIVE_BUDGETS_FLAG, PURGE_CAPITAL_FLAG, ARCHIVE_CAPITAL_FLAG, PURGE_SUMMARY_FLAG, ARCHIVE_SUMMARY_FLAG — per-category purge versus archive switches.
• ADMIN_PROJ_FLAG — indicates administrative project handling.
• NEXT_PP_PROJECT_STATUS_CODE, PS1.PROJECT_STATUS_NAME, NEXT_P_PROJECT_STATUS_CODE, PS2.PROJECT_STATUS_NAME — the pre-purge and post-purge project statuses, decoded to names.
• PURGED_DATE, PURGE_RELEASE — when the batch ran and the release level applied.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent request lineage.
• ORG_ID — operating unit identifier (multi-org).

Common Use Cases and Queries

Typical usage includes monitoring batch progress, auditing purge scope, and feeding downstream extracts. To list batches with decoded status:

SELECT purge_batch_id, batch_name, batch_status_code, meaning,
       purged_date, project_status_name
FROM   apps.pa_purge_batches_v
WHERE  meaning = 'Pending';

To review archive-versus-purge scope for actuals:

SELECT batch_name, purge_actuals_flag, archive_actuals_flag, txn_to_date
FROM   apps.pa_purge_batches_v
WHERE  purged_date IS NULL;

Joining to the underlying synonym for additional columns not exposed by the view is common, as is filtering by ORG_ID in multi-org deployments. Because the view performs inner joins on PA_LOOKUPS and PA_PROJECT_STATUSES, batches with missing lookup or status setup are not returned, which is a frequent cause of "missing row" reports.