Search Results pa_perf_comments_u1

Overview

PA.PA_PERF_COMMENTS is a transaction-detail table in the Oracle E-Business Suite Project Accounting (PA) schema that stores free-form performance comments recorded against performance transactions. In Oracle EBS 12.1.1 and 12.2.2 the table is documented as VALID, owned by the PA schema, with FND Design Data registered as PA.PA_PERF_COMMENTS. It resides in the APPS_TS_TX_DATA tablespace with PCT FREE 10, while its unique index is created in APPS_TS_TX_IDX, the standard configuration for high-volume transactional data.

The table is narrow in scope: it captures a comment identifier, a link to the originating performance transaction, the comment text, the identity of the person who entered the comment and the date it was entered, plus the standard Oracle WHO audit columns. Because it stores descriptive attributes attached to a parent transaction rather than defining entities or relationships of its own, the mined Data Vault classification is satellite-leaning. In modeling terms, PA_PERF_COMMENTS can be treated as a satellite hanging off the PA_PERF_TRANSACTIONS hub, with PERF_TXN_ID acting as the foreign key to the parent hub. This classification is a heuristic suggestion derived from the foreign-key structure rather than a documented Oracle design statement.

Key Information Stored

The documented physical schema contains ten columns. The most important are:

• COMMENT_ID (NUMBER(15)) — the surrogate primary key, enforced by PA_PERF_COMMENTS_PK and also carrying the unique index PA_PERF_COMMENTS_U1. It is the only unique business-key candidate in the documented structure and the identifier returned by the standard query text.
• PERF_TXN_ID (NUMBER(15)) — the foreign key to PA.PA_PERF_TRANSACTIONS, anchoring each comment to its parent performance transaction. This is the principal join column in any query that retrieves comments in a transactional context.
• COMMENT_TEXT (VARCHAR2(4000)) — the message text of the comment; the substantive payload of the row.
• COMMENTED_BY (NUMBER(15)) — the identifier of the user who authored the comment.
• COMMENT_DATE (DATE) — the date the comment was recorded, distinct from the standard creation timestamp.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the Oracle WHO audit columns, supporting change tracking and audit reporting.

There are no descriptive or denormalized attributes beyond these; the table is purely transactional and audit-oriented.

Common Use Cases and Queries

Typical usage includes retrieving all comments for a given performance transaction, auditing who entered commentary and when, and producing detail or exception reports for project performance review. A representative query filters on the parent transaction:

• SELECT c.COMMENT_ID, c.COMMENT_TEXT, c.COMMENTED_BY, c.COMMENT_DATE FROM PA.PA_PERF_COMMENTS c WHERE c.PERF_TXN_ID = :perf_txn_id ORDER BY c.COMMENT_DATE;
• SELECT c.COMMENT_ID, c.COMMENT_TEXT, c.COMMENT_DATE FROM PA.PA_PERF_COMMENTS c WHERE c.COMMENT_DATE BETWEEN :start_date AND :end_date;

Because COMMENT_ID is unique, single-row lookups by primary key are efficient through PA_PERF_COMMENTS_U1. COMMENT_TEXT is capped at 4000 characters, so reporting layers should be sized accordingly.

Related Objects

The most significant related object is the parent performance transaction table. The documented foreign key is:

• PA.PA_PERF_TRANSACTIONS — joined on PA_PERF_COMMENTS.PERF_TXN_ID = PA_PERF_TRANSACTIONS.PERF_TXN_ID; the parent hub for the satellite. This is the primary join in nearly all reporting use cases.
• APPS.PA_PERF_COMMENTS — the APPS-layer synonym/view that reference the PA base table and is referenced by dependent objects in the APPS schema. Most custom reports and concurrent programs should query through this APPS object rather than the PA base table directly.

The ETRM metadata records no additional referencing objects for PA.PA_PERF_COMMENTS beyond the APPS entry. As a result, the table should be treated strictly as a dependent detail of PA_PERF_TRANSACTIONS for integration and reporting purposes.