Results for “pa_ci_comments”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_CI_COMMENTS is a Project Accounting (PA) transactional table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the comments associated with the action log of project control items. A control item (held in PA_CONTROL_ITEMS) represents a tracked issue, deliverable, or commitment against a project; each control item can accumulate one or more actions (held in PA_CI_ACTIONS), and each action can carry comments. The table records requestor comments, closure comments, and progress comments on an action, as well as unsolicited comments attached directly to the control item. The documented business rule is that, for any given action, there is at most one requestor comment and one closure comment, which means the comment role is determined by TYPE_CODE rather than by multiple rows per type. The table is owned by the PA schema, is marked VALID, and in the documented 12.2.2 physical schema exposes 11 columns.

Under a heuristic Data Vault classification mined from its foreign key structure, the table behaves like a link: it connects an action (via CI_ACTION_ID) and a control item (via CI_ID) while also carrying descriptive attributes such as the comment text and comment type. In a dimensional model it is more naturally treated as a child detail or satellite of the action, with control item context inherited through the action.

Key Information Stored

The primary key is the surrogate identifier CI_COMMENT_ID, enforced by the index PA_CI_COMMENTS_PK, and also declared as the unique index PA_CI_COMMENTS_U1. The most significant columns are:

• CI_COMMENT_ID — surrogate primary key; unique identifier for each comment row.
• CI_ID — foreign key to PA_CONTROL_ITEMS; identifies the control item the comment belongs to.
• CI_ACTION_ID — foreign key to PA_CI_ACTIONS; identifies the action the comment relates to.
• TYPE_CODE — classifies the comment as a requestor, closure, or progress comment, or as an unsolicited comment on the control item.
• COMMENT_TEXT — the free-text body of the comment.
• RECORD_VERSION_NUMBER — optimistic locking / concurrency control value maintained by the OA Framework.
• CREATION_DATE, CREATED_BY — audit columns recording when and by whom the comment was entered.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — audit columns recording the most recent modification.

The unique index PA_CI_COMMENTS_U1 on CI_COMMENT_ID is the documented business-key candidate; no separate natural composite key is exposed, so the surrogate key remains the primary join path.

Common Use Cases and Queries

The table is primarily used for reporting on project issue resolution history, audit trails of change requests, and the progression of control items through their lifecycle. Typical queries join to the action and control item parents to resolve project context.

The following pattern returns all comments for a given control item, showing the type and author of each:

• SELECT c.CI_COMMENT_ID, c.TYPE_CODE, c.COMMENT_TEXT, c.CREATED_BY, c.CREATION_DATE
• FROM PA_CI_COMMENTS c
• WHERE c.CI_ID = :control_item_id
• ORDER BY c.CREATION_DATE;

A second pattern resolves action-level requestor and closure comments for status reporting:

• SELECT a.CI_ACTION_ID, c.TYPE_CODE, c.COMMENT_TEXT
• FROM PA_CI_ACTIONS a, PA_CI_COMMENTS c
• WHERE a.CI_ACTION_ID = c.CI_ACTION_ID
• AND a.CI_ACTION_ID = :action_id;

Common reporting scenarios include open issue dashboards for project managers, SLA tracking measuring time between requestor and closure comments, and extract programs feeding data warehouses where PA_CI_COMMENTS is modeled as a detail of the action link.

Related Objects

The FK metadata identifies the following dependencies:

• PA_CI_ACTIONS — parent table via PA_CI_COMMENTS.CI_ACTION_ID; the action to which requestor, closure, and progress comments belong. A comment row may reference an action through this column.
• PA_CONTROL_ITEMS — parent table via PA_CI_COMMENTS.CI_ID; the control item that owns the comment thread and against which unsolicited comments are recorded.

Beyond these documented relationships, PA_CI_COMMENTS depends on the standard EBS audit columns sourced from FND_USER and is accessed through OA Framework-based Project Accounting control item pages. Because it is a child of both PA_CI_ACTIONS and PA_CONTROL_ITEMS, deletes of parent control items or actions cascade the associated comment rows, and any reporting or integration layer must preserve the CI_ID and CI_ACTION_ID pair to maintain correct project context.