Search Results progress_status_name




Overview
Explore in AI Chat

Overview

APPS.PA_PROJ_CURR_STATUS_REP_V is a reporting view in the Oracle E-Business Suite Projects (PA) module that exposes the current progress status report associated with a project. It consolidates project identification, report type, progress status code and name, status indicator flags, report date ranges, and narrative fields into a single queryable structure. The view is registered in the Application Object Library as FND Design Data PA.PA_PROJ_CURR_STATUS_REP_V and carries a VALID status in the ETRM 12.2.2 metadata repository.

The object is documented by Oracle as Internal Use Only. Oracle Corporation does not support direct access to application data through this view except from standard Oracle Applications programs. Consequently, the view should be regarded as an internal reporting and integration artifact rather than a public data interface. It supplies the current status record for each project, which is why it is consumed by higher-level project list views.

Underlying Base Objects

The view is defined over three referenced objects, each of which appears in the dependency list as a synonym owned by APPS:

  • PA_PROGRESS_REPORT_VERS — stores progress report versions, providing report content, dates, and the linkage between a project and its status reports.
  • PA_PROJECT_STATUSES — holds the project status records, including the progress status code and name used for reporting.
  • PA_REPORT_TYPES — defines the report type identifiers and names that classify each report record.

The view aggregates these sources to produce one row per project and report type combination representing the current status report. Its output is in turn referenced by APPS.PA_PLM_PROJECTS_V, APPS.PA_PROJECT_LISTS_USER_V, and APPS.PA_PROJECT_LISTS_V, confirming its role as a supporting view within the project list and project lifecycle management reporting stack.

Key Columns

  • PROJECT_ID (NUMBER) — the project identifier linking the record to the project definition.
  • REPORT_TYPE_ID (NUMBER, length 15) and REPORT_TYPE_NAME (VARCHAR2, 80) — identify and describe the report classification drawn from PA_REPORT_TYPES.
  • PROGRESS_STATUS_CODE (VARCHAR2, 30) and PROGRESS_STATUS_NAME (VARCHAR2, 80) — the coded and descriptive progress status. Because the user searched for "progress_status_name," this column is the principal descriptive attribute returned when querying the view; it supplies the human-readable status text associated with the project's current report.
  • STATUS_ICON_IND and STATUS_ICON_ACTIVE_IND (VARCHAR2, 80) — control the display and activation of status indicators, supporting status-icon rendering in project reporting UIs.
  • REPORT_START_DATE, REPORT_END_DATE, and PUBLISHED_DATE (DATE) — define the reporting period and the publication date of the status report.
  • OVERVIEW and COMMENTS (VARCHAR2, 240) — narrative summary and remark fields accompanying the status report.

Common Use Cases and Queries

The view is typically consumed to retrieve the current progress status name and related report attributes for a project, and to support project list and PLM reporting. A straightforward query filters by project and returns the descriptive status:

  • SELECT project_id, report_type_name, progress_status_code, progress_status_name, report_start_date, report_end_date, published_date FROM apps.pa_proj_curr_status_rep_v WHERE project_id = :project_id;
  • SELECT project_id, progress_status_name FROM apps.pa_proj_curr_status_rep_v WHERE progress_status_name LIKE '%Active%'; — to locate projects by descriptive status text.
  • SELECT project_id, report_type_name, progress_status_code, published_date FROM apps.pa_proj_curr_status_rep_v ORDER BY published_date DESC; — to review published status reports.

Because the object is documented as Internal Use Only, custom integrations should prefer supported PA APIs or supported views. Access for ad hoc reporting should be governed accordingly, and any dependency on PA_PROJ_CURR_STATUS_REP_V should account for the possibility of change across releases, since Oracle does not guarantee this internal view as a stable interface.