Search Results next_p_project_status_code

Overview

The APPS.PA_PURGE_BATCHES_V view is a reporting and inquiry object within the Oracle E-Business Suite Projects (PA) module. It presents a denormalized, human-readable representation of purge batch definitions maintained in the PA_PURGE_BATCHES base table. Purge batches in Oracle Projects define the criteria and target dispositions used when archiving or purging project transaction and summary data. The view enriches the underlying batch records by resolving code columns to their descriptive meanings through joins to the PA_LOOKUPS and PA_PROJECT_STATUSES objects. This makes the view well suited to support Oracle Reports, Oracle Forms LOVs, OBIEE/BI Publisher extracts, and custom SQL-based integrations where users require the batch status meaning and the descriptive project status names rather than raw codes. Because the view is owned by APPS and is documented as VALID in ETRM 12.2.2, it is available for direct query by applications and reporting tools in both 12.1.1 and 12.2.2 environments.

Underlying Base Objects

The view is defined over three referenced base objects. PA_PURGE_BATCHES (a synonym in the ETRM metadata) is the primary driver table, supplying all batch-level attributes and the primary key PURGE_BATCH_ID. PA_LOOKUPS (a view) joins on LOOKUP_TYPE = 'PURGE_BATCH_STATUS' and LOOKUP_CODE = BATCH_STATUS_CODE to supply the lookup MEANING that is exposed as BATCH_STATUS. PA_PROJECT_STATUSES (a synonym) is joined twice: once as PS1 on PS1.PROJECT_STATUS_CODE = PB.NEXT_PP_PROJECT_STATUS_CODE and once as PS2 on PS2.PROJECT_STATUS_CODE = PB.NEXT_P_PROJECT_STATUS_CODE. These joins resolve the post-purge project status codes for two distinct target contexts — the "PP" (project-to-project or pre-processing) status and the "P" status — into their PROJECT_STATUS_NAME values, exposed as NEXT_PP_PROJECT_STATUS and NEXT_P_PROJECT_STATUS respectively. The query is filtered only by the lookup type condition, so all purge batch rows (for the organization scope stored on the row, ORG_ID) are returned.

Key Columns

• ROW_ID — the ROWID of the base PA_PURGE_BATCHES row, used for duplicate detection in self-service/Forms integrations.
• PURGE_BATCH_ID — primary key of the purge batch.
• BATCH_NAME / DESCRIPTION — user-defined identifier and free-text description of the batch.
• BATCH_STATUS_CODE / BATCH_STATUS — the raw status code and its decoded meaning (from PA_LOOKUPS, lookup type PURGE_BATCH_STATUS).
• ACTIVE_CLOSED_FLAG — indicates whether the batch is active or closed.
• TXN_TO_DATE — the transaction cutoff date governing which transactions are eligible for the batch.
• PURGE_/ARCHIVE_ (ACTUALS, BUDGETS, CAPITAL, SUMMARY) FLAGS — discrete Yes/No indicators controlling which data classes are purged versus archived.
• ADMIN_PROJ_FLAG — indicates whether administrative project records are included.
• NEXT_PP_PROJECT_STATUS_CODE / NEXT_PP_PROJECT_STATUS — the code and name of the project status to be applied in the PP context after purge.
• NEXT_P_PROJECT_STATUS_CODE / NEXT_P_PROJECT_STATUS — the code and name of the project status to be applied in the P context after purge.
• PURGED_DATE, PURGE_RELEASE — when the batch was purged and the release level applied.
• Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and concurrent request columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE).
• ORG_ID — the operating unit / organization identifier for multi-org filtering.

Common Use Cases and Queries

Typical use cases include listing all purge batches with their decoded statuses, identifying batches associated with a specific target project status, and feeding reporting layouts with descriptive columns. A frequent query pattern is to search on the requested column NEXT_PP_PROJECT_STATUS_CODE:

• SELECT purge_batch_id, batch_name, batch_status, next_pp_project_status_code, next_pp_project_status FROM pa_purge_batches_v WHERE next_pp_project_status_code = :status_code;
• SELECT purge_batch_id, batch_name, batch_status, active_closed_flag, txn_to_date FROM pa_purge_batches_v WHERE org_id = :org_id ORDER BY creation_date DESC;
• SELECT purge_batch_id, batch_name, next_p_project_status FROM pa_purge_batches_v WHERE batch_status_code = 'COMPLETE';

Because the view already performs the lookup and status-name resolution, reports and integrations should query PA_PURGE_BATCHES_V rather than the base table when descriptive values are required, and should apply ORG_ID predicates to satisfy multi-org security.