Search Results priority_description




Overview
Explore in AI Chat

Overview

PA_CI_ACTIONS_V is a Projects (PA) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to provide the attribute values for Action Lists associated with control items. In the Projects architecture, a control item (CI) represents a tracked issue, change, or deliverable, while an action is a discrete task assigned against that control item. This view denormalizes those relationships into a single reporting surface, resolving internal codes into user-facing meanings.

The column PRIORITY_DESCRIPTION, which is the term the user searched for, is one of the resolved attributes exposed by this view. It is derived from the PA_LOOKUPS table aliased as PRIORITY_LKP, joining on the priority lookup code stored on the control item. Rather than returning a raw lookup code, the view returns the translated MEANING value, allowing reports and integrations to present priority in business-readable form without additional lookups.

Underlying Base Objects

The view is defined over a substantial join across Projects, Trading Community, and common lookup objects. Documented base objects include PA_CI_ACTIONS (action records), PA_CONTROL_ITEMS (the parent control items), PA_CI_COMMENTS (comments attached to control items), PA_CI_TYPES_VL (control item type definitions), PA_PROJECTS_ALL (project master data), PA_LOOKUPS (Projects lookup meanings and codes), and the FND_LOOKUPS view (used for Yes/No and related common lookups). Party identity is resolved through HZ_PARTIES, and several self-joins against PA_CI_ACTIONS supply related action and source-action context.

Two PL/SQL packages are referenced. PA_CONTROL_ITEMS_UTILS.GET_OBJECT_NAME resolves the referenced object for a control item, and FND_GLOBAL and PA_UTILS are used for session and utility context. The joins enforce consistency: control items link to their type, actions link to their assigned party and control item, and comment rows are attached to both the action and its source. Category codes such as control item type, action type, and status are translated through the respective lookup views.

Key Columns

Common Use Cases and Queries

Typical usage includes action list reporting, aging analysis of open actions, and integration extracts feeding external workflow or notification systems. The view is especially useful when priority must be reported as a description rather than a code.

Retrieve actions with their priority description for a given project:

  • SELECT control_item, subject, priority_description, status_code, date_required
  • FROM apps.pa_ci_actions_v
  • WHERE project_id = :p_project_id
  • ORDER BY priority_description, date_required;

Filter open actions by priority meaning and assigned party:

  • SELECT ci_action_number, subject, priority_description, assign_name
  • FROM apps.pa_ci_actions_v
  • WHERE priority_description = 'High'
  • AND status_code = 'CI_ACTION_OPEN';

Because the view resolves lookups and party names inline, it reduces join complexity for report developers and provides a consistent source for both 12.1.1 and 12.2.2 environments.