Search Results priority_sort




Overview
Explore in AI Chat

Overview

PA_CI_CRPRJ_LIST_V is an APPS-owned reporting view within the Oracle Projects (PA) module that consolidates change issue (CI) records — sometimes called control items or change requests — alongside their associated project, type, status, priority, classification, and resolution attributes. The view is a denormalized projection designed to feed the "Control Items" and change management list pages rendered by Oracle's Project Management and Project Intelligence HTML clients, and it is the principal source for the change request list region in the Projects workbench. Because it exposes the full set of descriptive, status, ownership, and financial-amount columns in a single flattened row, it is widely used in custom reports, Oracle BI Publisher templates, and integration extracts that need a portrait of project change activity without joining half a dozen base tables manually. The view is documented as VALID and is delivered under the APPS schema in both Oracle EBS 12.1.1 and 12.2.2. Note that the view is not itself secured per user; row-level access is layered on top of it by the Oracle Projects security model, so deployments that require responsibility-based filtering should join or wrap it with the security views.

Underlying Base Objects

The documented referenced objects span both core tables and supporting views and packages:

Key Columns

Important columns include: PROJECT_ID, SEGMENT1, NAME, and LONG_NAME (project identification); CI_ID, CI_NUMBER, SUMMARY, DESCRIPTION, and STATUS_CODE (issue identification); PROJECT_STATUS_NAME and PROJECT_SYSTEM_STATUS_CODE (project status text and code); STATUS.PROJECT_STATUS_NAME as the change-issue status name; OWNER_ID and PARTY_NAME (issue owner); DATE_REQUIRED, DATE_CLOSED, OPEN_ACTION_NUM, PROGRESS_STATUS_CODE, PROGRESS_AS_OF_DATE, EFFORT_LEVEL_CODE, and RECORD_VERSION_NUMBER; PRIORITY_CODE and PRIORITY_LKP.MEANING (priority label); CLASS_CODE, CLASS_CATEGORY, and RESOLUTION; and PRICE plus PRICE_CURRENCY_CODE. Two computed expressions return aging values — days until DATE_REQUIRED and days since LAST_UPDATE_DATE — each suppressed with NULL when the issue is closed or canceled. Element name and number columns are derived through the utility package, and forecast quantity columns (EST_QUANTITY, LABOR_QUANTITY, ESTIMATED amounts) come from PA_FP_CI_AMOUNTS_V.

Common Use Cases and Queries

Typical scenarios include listing open change requests by project, aging reports for outstanding approvals, and extracts joined to budgets for quote-to-project change control. A representative query for open items sorted by the priority attribute a user might search as "priority_sort" is:

  • SELECT ci_number, summary, project_status_name, priority_code, priority_meaning FROM apps.pa_ci_crprj_list_v WHERE status_code NOT IN ('CI_CLOSED','CI_CANCELED') ORDER BY priority_code, date_required;
  • Aggregate aging: SELECT project_id, COUNT(*) open_issues, AVG(days_to_required) FROM apps.pa_ci_crprj_list_v GROUP BY project_id;
  • Owner workload: SELECT party_name, COUNT(*) FROM apps.pa_ci_crprj_list_v WHERE status_code = 'CI_OPEN' GROUP BY party_name ORDER BY 2 DESC;

Because the view performs inline PL/SQL calls per row, filter by PROJECT_ID or CI_ID wherever feasible and avoid functions on indexed columns in the WHERE clause to preserve performance.