Search Results page_status_meaning

Overview

APPS.PA_PROGRESS_REPORTS_V is a reporting view in the Oracle E-Business Suite (EBS) Projects (PA) module, available in releases 12.1.1 and 12.2.2. It presents project progress report versions together with their decoded status descriptions, decoupling the raw code columns stored in the underlying version table from the human-readable status names required by reports, concurrent programs, and integration layers. The view filters on PAGE_TYPE_CODE = 'PPR', so it exposes only progress report page-type records from the version table.

The view is significant because it resolves two distinct status concepts that are frequently conflated. REPORT_STATUS_CODE is decoded against PA_PROJECT_STATUSES to yield PAGE_STATUS_MEANING, while PROGRESS_STATUS_CODE is decoded against the same status table to yield PROGRESS_STATUS_MEANING, along with the associated icon indicators. The column name PAGE_STATUS_MEANING is the decoded display value for the report/page status, which is precisely why it appears in metadata searches for "page_status_meaning". Because the progress status join is outer, records with no defined progress status still return a row, with PROGRESS_STATUS_MEANING null. The report type join is also outer, permitting versions whose report type is not defined in PA_REPORT_TYPES to remain visible.

Underlying Base Objects

The view is defined over four documented base objects. PA_PROGRESS_REPORT_VERS is the driving object and supplies the version identity, status codes, dates, narrative text, and descriptive attributes. PA_PROJECT_STATUSES is joined twice under the aliases PPS1 and PPS2: PPS1 decodes REPORT_STATUS_CODE into the page status meaning, and PPS2 decodes PROGRESS_STATUS_CODE into the progress status meaning including the status icon columns. PA_REPORT_TYPES is joined under the alias RTYP on REPORT_TYPE_ID to supply the report type name, using an outer join. PA_RESOURCE_UTILS is a package, not a table, invoked for resource name resolution on REPORTED_BY, on the LAST_UPDATED_BY identity, and on an inner resource ID lookup.

All base table references are to APPS synonyms. The view is owned by APPS and is intended for read access by reporting and integration components rather than direct application transaction processing.

Key Columns

• OBJECT_TYPE, OBJECT_ID, PAGE_TYPE_CODE, PAGE_ID, VERSION_ID — Identity of the owning project object and the specific progress report page version. PAGE_TYPE_CODE is constrained to 'PPR'.
• REPORT_STATUS_CODE — Raw page/report status code stored on the version row.
• PAGE_STATUS_MEANING — Decoded status name from PPS1.PROJECT_STATUS_NAME; the display value associated with REPORT_STATUS_CODE.
• PROGRESS_STATUS_CODE, PROGRESS_STATUS_MEANING — Raw progress status code and its decoded name from PPS2.
• STATUS_ICON_IND, STATUS_ICON_ACTIVE_IND — Icon indicator flags associated with the resolved progress status, used by user interface rendering.
• REPORT_START_DATE, REPORT_END_DATE — Reporting period covered by the progress report version.
• REPORTED_BY — Resource identifier of the reporter, accompanied by a resolved resource name via PA_RESOURCE_UTILS.GET_RESOURCE_NAME.
• OVERVIEW, COMMENTS — Narrative text entered for the progress report.
• PUBLISHED_DATE, CANCELED_DATE — Lifecycle timestamps for publication and cancellation.
• RECORD_VERSION_NUMBER — Optimistic locking version counter.
• REPORT_TYPE_ID, NAME — Report type identifier and the name resolved through the outer join to PA_REPORT_TYPES.
• Resolved last-updated resource name — Derived from LAST_UPDATED_BY through the resource utility package.

Common Use Cases and Queries

Typical uses include status reporting on published and in-progress project progress reports, dashboards that require decoded status labels rather than stored codes, and extracts feeding external reporting tools. A representative query listing report status and progress status per version is:

SELECT page_id, version_id, page_status_meaning,
       progress_status_meaning, report_start_date, report_end_date,
       published_date, canceled_date
  FROM apps.pa_progress_reports_v
 WHERE object_id = :object_id
 ORDER BY version_id;

To isolate only currently published reports, filter on PUBLISHED_DATE and CANCELED_DATE, for example WHERE published_date IS NOT NULL AND canceled_date IS NULL. A second common pattern joins the view back to a project identifier for consolidated status reporting:

SELECT r.page_id, r.page_status_meaning, r.progress_status_meaning,
       r.report_end_date, r.name report_type
  FROM apps.pa_progress_reports_v r
 WHERE r.progress_status_meaning IS NOT NULL
 ORDER BY r.report_end_date DESC;

Because PROGRESS_STATUS_CODE is resolved through an outer join, consumers requiring a definitive progress status should test PROGRESS_STATUS_MEANING for null before using the value. This view should not be treated as a transactional interface; inserts and updates belong on PA_PROGRESS_REPORT_VERS.