Search Results assignee_name

Overview

PA_CI_COMMENTS_V is an APPS-owned database view in the Oracle EBS Projects (PA) module that exposes comment records stored in the PA_CI_COMMENTS table, enriched with attribute values drawn from control item actions and party definitions. Its primary role is to present a flattened, reporting-friendly representation of collaboration and issue-tracking comments associated with control items, so that forms, concurrent programs, and custom reports can retrieve comment text together with the identities of the individuals involved. The view is validated and available in both Oracle EBS 12.1.1 and 12.2.2. It is particularly relevant to clients searching for the column reassignee_name, since that attribute is exposed directly by this view rather than being available in the base comment table.

Underlying Base Objects

The documented base objects referenced by PA_CI_COMMENTS_V are HZ_PARTIES, PA_CI_ACTIONS, PA_CI_ACTIONS_UTIL, PA_CI_COMMENTS, PA_CONTROL_ITEMS, PA_LOOKUPS, and PA_UTILS. The central driving table is PA_CI_COMMENTS, which supplies the comment identifier, comment text, type code, and audit columns. PA_CONTROL_ITEMS provides the associated project identifier (PROJECT_ID) by joining on CI_ID. PA_CI_ACTIONS supplies action-level detail including action type, status, and action number, and is aliased twice: once as the primary action and once as A2 to resolve a source or reassignment action. HZ_PARTIES is referenced three times, aliased as COMMENTOR, ASSIGNEE, and REASSIGNEE, to translate party identifiers into person names. PA_LOOKUPS supplies the decoded action type meaning via the PA_CI_ACTION_TYPES lookup type, while PA_CI_ACTIONS_UTIL and PA_UTILS supply PL/SQL functions used in the SELECT list and join predicates.

Key Columns

The view returns the following significant columns:

• CI_COMMENT_ID, CI_ID, CI_ACTION_ID — Identifiers linking the comment to its control item and originating action.
• COMMENT_TEXT, MESSAGE_TYPE_CODE — The body of the comment and its classification code.
• COMMENT_CREATED_BY_NAME, REQUESTOR_NAME — Party names of the comment author and requestor.
• ASSIGNEE_NAME — Name of the person to whom the action is currently assigned.
• REASSIGNEE_NAME — Name of the party to whom the action was reassigned, derived from the secondary PA_CI_ACTIONS alias and the REASSIGNEE instance of HZ_PARTIES.
• ACTION_TYPE_CODE, ACTION_TYPE, STATUS_CODE, CI_ACTION_NUMBER — Decoded action attributes for the associated control item action.
• REASSIGN_CI_ACTION_ID, SOURCE_CI_ACTION_ID — References to the reassignment and originating actions.
• PROJECT_ID — The project context of the control item.
• CHILD_EXISTS — A computed flag indicating whether a reply exists for a requestor comment on an open action.

Common Use Cases and Queries

Typical usage includes collaboration dashboards, issue aging reports, and audit extracts that require reassignment history. To list comments with reassignee information:

SELECT ci_comment_id,
       comment_text,
       comment_created_by_name,
       assignee_name,
       reassignee_name,
       action_type,
       status_code
FROM   apps.pa_ci_comments_v
WHERE  project_id = :p_project_id
AND    reassignee_name IS NOT NULL;

To trace open requestor comments lacking replies:

SELECT ci_id, comment_text, requestor_name
FROM   apps.pa_ci_comments_v
WHERE  child_exists = 'N'
AND    message_type_code = 'REQUESTOR';

Queries should filter by PROJECT_ID or CI_ID to constrain the UNION ALL structure and avoid full scans across the joined action and party data.