Search Results reassigned_to

Overview

PA_CI_ACTIONS_CHRO_V is a reporting view within the Oracle E-Business Suite Projects (PA) module that presents the Control Item action log in chronological order. Control Items are used in project collaboration and issue tracking workflows, and each Control Item may accumulate a series of actions — requests, responses, reassignments, and status transitions — over its lifecycle. The view consolidates these actions together with the associated comment text so that a functional user or downstream report can reconstruct the full communication thread.

A defining characteristic of this view is that requests and their corresponding responses are surfaced as separate rows. Because there is no aggregation of the request and its reply into a single record, the chronological ordering produced by the view reflects discrete transaction events rather than conversational pairs. This makes the view well suited to audit trails, dashboards, and integration extracts that need event-level granularity rather than summarized threads.

In Oracle EBS 12.1.1 and 12.2.2, the view is typically consumed by reporting tools, custom concurrent programs, and OBIEE or BI Publisher extracts built over the Projects schema. The ETRM metadata notes that the view is not implemented in the reference database from which the documentation was generated, so availability should be verified against the target environment.

Underlying Base Objects

The view text is defined over a set of base tables and lookup objects. The central table is PA_CI_ACTIONS, which appears twice — once as the primary action alias (A) and once as the reassignment action alias (A2) — via an outer join on SOURCE_CI_ACTION_ID. A.Control item context is supplied by PA_CONTROL_ITEMS (PCI), joined through COMMENTS.CI_ID. Comment text and timestamps are drawn from PA_CI_COMMENTS. Status descriptions come from PA_PROJECT_STATUSES, while action type and sign-off flag meanings are resolved through PA_LOOKUPS and two instances of FND_LOOKUPS. Party names are obtained from HZ_PARTIES, joined four times for the requestor, assignee, reassignee, and commentor roles.

Party identifier resolution is performed by the PL/SQL function PA_CI_ACTIONS_UTIL.GET_PARTY_ID, which converts a CREATED_BY (FND user identifier) into the corresponding HZ_PARTIES party ID. The ETRM metadata lists no documented referenced base objects, so the relationships above are derived from the published view SQL. Note that all party joins are outer joins, ensuring actions and comments without fully resolved party records still appear.

Key Columns

• CI_COMMENT_ID, CI_ID, CI_ACTION_ID — Identifiers linking the row to the Control Item, action, and comment/response record.
• UPDATE_DATE, UPDATE_TIME — The comment's last update date and a 12-hour formatted time, used for chronological placement.
• COMMENT_CREATED_BY_NAME, REQUESTOR_NAME, ASSIGNEE_NAME, REASSIGNEE_NAME — Party names sourced from HZ_PARTIES for each role.
• ASSIGNED_TO — The party ID of the individual currently assigned to the action; this column is the target of the common "assigned_to" search and joins to ASSIGNEE.PARTY_ID.
• REASSIGNED_TO, REASSIGN_CI_ACTION_ID, REASSIGN_CI_ACTION_NUMBER — Populated when a reassignment action precedes the current action.
• COMMENT_TEXT, MESSAGE_TYPE_CODE — The literal message content and its classification (request versus response).
• ACTION_TYPE_CODE, ACTION_TYPE, STATUS_CODE, STATUS_CODE_MEANING — Decoded action and status values from PA_LOOKUPS and PA_PROJECT_STATUSES.
• SIGN_OFF_REQUIRED_FLAG, SIGN_OFF_FLAG and their MEANING columns — Sign-off requirement and completion indicators from FND_LOOKUPS.
• DATE_REQUIRED, DATE_CLOSED, CI_ACTION_NUMBER, PROJECT_ID — Due date, closure date, human-readable action number, and owning project.

Common Use Cases and Queries

Typical uses include building a Control Item audit trail, generating an assignee workload report, and extracting sign-off compliance data. A frequent query pattern filters by ASSIGNED_TO to see what a given individual is responsible for:

• SELECT CI_ACTION_NUMBER, REQUESTOR_NAME, ASSIGNEE_NAME, ACTION_TYPE, STATUS_CODE_MEANING, COMMENT_TEXT FROM PA_CI_ACTIONS_CHRO_V WHERE ASSIGNED_TO = :party_id ORDER BY LAST_UPDATE_DATE;
• Chronological thread for one Control Item: SELECT UPDATE_DATE, UPDATE_TIME, COMMENT_CREATED_BY_NAME, MESSAGE_TYPE_CODE, COMMENT_TEXT FROM PA_CI_ACTIONS_CHRO_V WHERE CI_ID = :ci_id ORDER BY LAST_UPDATE_DATE;
• Outstanding sign-offs: SELECT CI_ACTION_NUMBER, ASSIGNEE_NAME, SIGN_OFF_REQUIRED_FLAG, SIGN_OFF_FLAG FROM PA_CI_ACTIONS_CHRO_V WHERE SIGN_OFF_REQUIRED_FLAG = 'Y' AND SIGN_OFF_FLAG = 'N' AND DATE_CLOSED IS NULL;

Because requests and responses are separate rows, aggregations such as the latest comment per action typically require a correlated subquery or analytic ranking on LAST_UPDATE_DATE.