Search Results progress_status_active_icon

Overview

The APPS.PA_PROGRESS_REPORTS_MAIN_V view is a Projects (PA) module reporting object in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a consolidated, security-aware list of progress report entries and their associated object/reporting page layout definitions. The view is designed to serve as the primary driving query behind the Progress Reports user interface and related reporting, surfacing both existing report versions and report containers that do not yet have a generated version.

Its role in EBS reporting and integration is to flatten the relationship between progress report versions, report types, object page layouts, and status lookups into a single queryable structure. Because it exposes the security-check function PA_PROGRESS_REPORT_UTILS.CHECK_SECURITY_FOR_PROGREP as a column (REPORT_ACCESS), it can be used to enforce row-level access control within custom reports and extensions that must respect the same authorization rules as the standard Progress Reports page.

Underlying Base Objects

The view is defined in the APPS schema and joins several documented base objects. The primary source is PA_PROGRESS_REPORT_VERS (referenced through a synonym), which supplies the report version records including report type, status, dates, reporter, and version identifiers. It is joined to PA_OBJECT_PAGE_LAYOUTS (synonym) on OBJECT_ID, OBJECT_TYPE, and REPORT_TYPE_ID to obtain page and next-reporting-date information. PA_REPORT_TYPES (synonym) provides the report type name, while PA_PROJECT_STATUSES (synonym) is referenced twice — once for the report status meaning and once (outer-joined) for the progress status meaning and status icon attributes.

Two PL/SQL packages are also referenced: PA_RESOURCE_UTILS.GET_RESOURCE_NAME resolves the reporter's display name, and PA_PROGRESS_REPORT_UTILS.CHECK_SECURITY_FOR_PROGREP computes the REPORT_ACCESS flag. The view is a UNION of two branches: the first returns existing report versions where the generation method is null or 'MANUAL', and the second returns page-layout rows converted to the same shape with null version and status values and a CURRENT_FLAG of 'Y'.

Key Columns

• OBJECT_TYPE / OBJECT_ID / PAGE_TYPE_CODE / PAGE_ID — identify the owning project or object and its reporting page; PAGE_TYPE_CODE is restricted to 'PPR' in the version branch.
• REPORT_TYPE_ID / NAME — the report type and its descriptive name.
• VERSION_ID — the progress report version; null in the page-layout branch where no version exists yet.
• REPORT_STATUS_CODE / PAGE_STATUS_MEANING — report status code and its decoded project status name.
• PROGRESS_STATUS_CODE / PROGRESS_STATUS_MEANING — progress status and meaning from the outer-joined status lookup, along with STATUS_ICON_IND and STATUS_ICON_ACTIVE_IND.
• REPORT_START_DATE / REPORT_END_DATE / NEXT_REPORTING_DATE — reporting period boundaries and the next due date.
• REPORTED_BY and its derived resource name — the reporter identifier and resolved name.
• CURRENT_FLAG / OVERVIEW / COMMENTS / PUBLISHED_DATE / CANCELED_DATE — lifecycle and content attributes.
• REPORT_ACCESS — the per-row security determination returned by CHECK_SECURITY_FOR_PROGREP.
• RECORD_VERSION_NUMBER — used for optimistic locking on the underlying version record.

Common Use Cases and Queries

The view is typically queried to list progress reports for a project, to identify reports still pending a generated version, or to build custom dashboards that must honor progress report security. A common query filters by object and restricts access using the security column:

• Listing current reports for a project: SELECT version_id, report_type_id, name, report_status_code, progress_status_meaning, next_reporting_date FROM pa_progress_reports_main_v WHERE object_id = :project_id AND current_flag = 'Y';
• Enforcing security in a custom report: SELECT object_id, report_type_id, version_id FROM pa_progress_reports_main_v WHERE report_access = 'Y';
• Finding reporting pages without a version yet: SELECT object_id, page_id, report_type_id, next_reporting_date FROM pa_progress_reports_main_v WHERE version_id IS NULL;

Because the view aggregates status decoding, resource name resolution, and security evaluation, it is preferable to query it directly rather than reimplementing these joins in custom code.