Search Results progress_report_id

Overview

The APPS.PA_PROJ_PROGRESS_REPORTS_V view is a reporting and integration object within the Oracle E-Business Suite Projects (PA) module. It presents a denormalized, read-only projection of project progress report data, combining the transactional rows stored in the underlying progress report base object with the descriptive meaning of the progress status lookup. This design allows reporting tools, concurrent programs, and external integrations to retrieve both the coded value (PROGRESS_STATUS_CODE) and its human-readable meaning (PROGRESS_STATUS_MEANING) in a single query without performing an explicit join to the lookup view.

The view is owned by the APPS schema and holds VALID status, which confirms it is a supported and active database object in both Oracle EBS 12.1.1 and 12.2.2. Because it exposes progress status, percent complete, estimate-to-complete, and scheduling attributes, it is particularly useful for project performance analysis, status reporting, and dashboard-style queries. Its presence in the ETRM catalog under the PA - Projects product reinforces its role as a documented reference object rather than an internal, undocumented structure.

Underlying Base Objects

The view is defined over two documented base objects. The primary source is PA_PROJ_PROGRESS_REPORTS, referenced as a synonym, which stores the actual progress report records keyed by PROGRESS_REPORT_ID. The second object is PA_LOOKUPS, referenced as a view, which supplies the lookup meaning for the progress status.

The join condition links PPR.PROGRESS_STATUS_CODE to PAL.LOOKUP_CODE, constrained by PAL.LOOKUP_TYPE = 'PA_XC_PROGRESS_STATUS'. Only rows whose progress status code matches an active lookup of this type are returned, effectively making the lookup an inner join filter. The view aliases the lookup meaning column as PROGRESS_STATUS_MEANING. Columns such as CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN are inherited directly from the base progress report object, preserving standard EBS audit and concurrency columns.

Key Columns

The view exposes the following primary columns:

• PROGRESS_REPORT_ID — Primary identifier for the progress report record.
• PROJECT_ID / TASK_ID — Foreign keys identifying the project and, where applicable, the task.
• PROGRESS_STATUS_CODE / PROGRESS_STATUS_MEANING — The coded status and its lookup-derived description.
• SHORT_DESCRIPTION / LONG_DESCRIPTION / ISSUES — Narrative fields describing the report and any outstanding issues.
• PROGRESS_ASOF_DATE — The effective date of the reported progress.
• ESTIMATED_START_DATE / ESTIMATED_END_DATE / ACTUAL_START_DATE / ACTUAL_END_DATE — Planning versus actual schedule dates.
• PERCENT_COMPLETE / ESTIMATE_TO_COMPLETE — Quantitative progress measures.
• UNIT_TYPE / PLANNED_ACTIVITIES — Unit of measure and planned activities detail.
• REPORT_STATUS — Status of the report record itself (the column matching the search term "report_status").
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns.
• RECORD_VERSION_NUMBER — Optimistic locking / versioning column.

Common Use Cases and Queries

Typical uses include progress reporting extracts, project status dashboards, and integration feeds that publish percent complete and schedule data to external systems. A common query retrieves all reports for a project:

• SELECT project_id, task_id, progress_status_meaning, report_status, percent_complete, progress_asof_date FROM pa_proj_progress_reports_v WHERE project_id = :p_project_id;
• SELECT report_status, COUNT(*) FROM pa_proj_progress_reports_v GROUP BY report_status; — reports distribution by report status.
• SELECT progress_status_meaning, AVG(percent_complete) FROM pa_proj_progress_reports_v GROUP BY progress_status_meaning; — average completion by status.

Because the join to PA_LOOKUPS is inner, records with an invalid or unmapped progress status code will not appear; consumers requiring every base row should query PA_PROJ_PROGRESS_REPORTS directly and outer-join the lookup.