Search Results pa_progress_reports_v




Overview

PA_PROGRESS_REPORTS_V is a read-only consolidated view owned by the APPS schema in Oracle E-Business Suite, belonging to the Projects (PA) product family. It exposes progress report version data maintained for project and task objects within Oracle Projects, presenting status, reporting period, narrative content, and publishing lifecycle information. The view is documented in ETRM for releases 12.1.1 and 12.2.2 with a VALID status.

The view is designed to present progress reports at the page level, restricted by the literal predicate PAGE_TYPE_CODE = 'PPR', meaning only progress report pages are returned. Its principal role is to support reporting, inquiry, and integration requirements where progress report content must be retrieved together with human-readable status and resource names, rather than raw code values. As a view, it stores no data of its own; all content is derived at query time from its underlying base objects.

Underlying Base Objects

The documented base objects referenced by this view are PA_PROGRESS_REPORT_VERS, PA_PROJECT_STATUSES (referenced twice), PA_REPORT_TYPES, and the PA_RESOURCE_UTILS package. PA_PROGRESS_REPORT_VERS is the primary driver table, supplying version identifiers, report dates, reported-by values, overview and comment text, publishing and cancellation dates, and record version numbers. PA_PROJECT_STATUSES is joined twice: once on REPORT_STATUS_CODE to resolve the report status meaning and once on PROGRESS_STATUS_CODE to resolve the progress status meaning, icon indicator, and active icon indicator. PA_REPORT_TYPES is outer-joined on REPORT_TYPE_ID to resolve the report type name. PA_RESOURCE_UTILS is invoked through the GET_RESOURCE_NAME function to derive the reporter name and the name of the last updating user, and internally through GET_RESOURCE_ID to convert the LAST_UPDATED_BY column into a resource identifier.

Key Columns

Common Use Cases and Queries

Typical uses include reporting on progress report activity by project and period, building status dashboards, and extracting narrative content for integration with external repositories.

SELECT object_id,
       report_type_name,
       report_status_meaning,
       report_start_date,
       report_end_date,
       reported_by_name
FROM   pa_progress_reports_v
WHERE  report_end_date >= :p_from_date
AND    report_end_date <= :p_to_date;
SELECT object_type,
       page_id,
       version_id,
       progress_status_meaning,
       published_date
FROM   pa_progress_reports_v
WHERE  report_status_meaning = 'Submitted'
AND    canceled_date IS NULL;

Because the view performs function calls to PA_RESOURCE_UTILS for name resolution, queries should be filtered as tightly as possible on object, date, or status columns to limit the volume of rows processed.