Search Results last_project_status_code

Overview

PA_PURGE_PROJECTS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PA (Projects) module. It presents a consolidated, denormalized picture of the project purge process by joining the purge control records held in PA_PURGE_PROJECTS to the project master rows in PA_PROJECTS and to several descriptive lookup and reference objects. Its principal role is to expose the state of each purge-eligible project in a human-readable form, translating internal status codes into meaningful status names and joining in the project number, project name, organization name and project type. This makes it suitable both for ad-hoc reporting by projects administrators and for integration or diagnostic queries used during archiving and purge cycles.

The view is defined with a ROW_ID pseudo-column derived from PA_PURGE_PROJECTS.ROWID, which uniquely identifies the underlying purge record and supports programmatic access. Because the view is a read-only projection over base purge and project data, it is typically referenced by purge and archive concurrent programs, custom reports and reconciliation queries rather than updated directly.

Underlying Base Objects

The documented base objects referenced by PA_PURGE_PROJECTS_V are HR_GENERAL (package), HR_ORGANIZATION_UNITS (view), HR_SECURITY (package), PA_LOOKUPS (view), PA_PROJECTS (synonym), PA_PROJECT_STATUSES (synonym) and PA_PURGE_PROJECTS (synonym). The joins are driven principally by PA_PURGE_PROJECTS joined to PA_PROJECTS on PROJECT_ID, with the carrying-out organization matched to HR_ORGANIZATION_UNITS on ORGANIZATION_ID to resolve the organization name. Three aliased instances of PA_PROJECT_STATUSES (PS1, PS2, PS3) resolve the current project status, the next purge status and the next project status codes into descriptive names. The PURGE_PROJECT_STATUS code is resolved through PA_LOOKUPS with LOOKUP_TYPE = 'PURGE_PROJECT_STATUS'. The HR_SECURITY and HR_GENERAL packages are referenced implicitly by the organization unit view to enforce organization-level security through the ORG_ID column exposed at the end of the select list.

Key Columns

• ROW_ID – Rowid of the underlying PA_PURGE_PROJECTS record; used as a unique identifier.
• PROJECT_NUMBER / PROJECT_NAME – SEGMENT1 and NAME from PA_PROJECTS.
• PURGE_PROJECT_STATUS / PURGE_PROJECT_STATUS_CODE – Purge state, with the code decoded via PA_LOOKUPS.
• PROJECT_ID, ORGANIZATION_NAME, ORGANIZATION_ID, PROJECT_TYPE, PROJECT_CLOSED_DATE – Core project identity and classification attributes.
• PROJECT_STATUS_CODE / PROJECT_STATUS – Current project status and its descriptive name.
• PURGE_BATCH_ID – Batch that owns the purge record, useful for grouping purge runs.
• TXN_TO_DATE – Transaction cutoff date used when purging/archiving.
• PURGE_ACTUALS_FLAG, ARCHIVE_ACTUALS_FLAG, PURGE_BUDGETS_FLAG, ARCHIVE_BUDGETS_FLAG, PURGE_CAPITAL_FLAG, ARCHIVE_CAPITAL_FLAG, PURGE_SUMMARY_FLAG, ARCHIVE_SUMMARY_FLAG – Indicator flags controlling whether actuals, budgets, capital and summary balances are purged or archived.
• NEXT_PP_PROJECT_STATUS(_CODE), NEXT_P_PROJECT_STATUS(_CODE) – Target statuses applied after the purge/project transition.
• PURGED_DATE – Date the project was purged.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, ORG_ID – Standard audit and multi-org columns.

Common Use Cases and Queries

A typical query lists purge candidates for a given batch:

• SELECT project_number, project_name, purge_project_status, txn_to_date, purged_date FROM pa_purge_projects_v WHERE purge_batch_id = :batch_id ORDER BY project_number;
• SELECT project_number, project_name, organization_name, project_status, purge_project_status FROM pa_purge_projects_v WHERE org_id = :org_id AND purge_project_status_code = 'PENDING';
• SELECT project_number, purge_actuals_flag, archive_actuals_flag, purge_budgets_flag, archive_budgets_flag FROM pa_purge_projects_v WHERE project_id = :project_id;

These queries support reconciliation of purge batches, verification of archive-versus-purge flags before a run, and audit reporting on completed purges. Because the view applies HR organization security, results are automatically restricted to the operating units visible to the querying responsibility.