Search Results pa_perf_comments_pk

Overview

PA_PERF_COMMENTS is a transactional table in the Oracle Projects (PA) schema that stores free-text performance comments recorded against project performance transactions. Within Oracle EBS 12.1.1 and 12.2.2, it functions as a detail-level repository for narrative observations captured during project performance reporting cycles, typically referenced through the Project Status Inquiry and performance reporting workflows. Each row represents a single comment authored by a user and attached to a specific performance transaction.

From a dimensional modeling perspective, the mined metadata classifies PA_PERF_COMMENTS as satellite-leaning. This classification reflects its structure: the table carries a surrogate primary key and a narrow set of descriptive attributes that change over time, all anchored to a parent transaction rather than acting as an independent hub or resolving many-to-many relationships. Practically, this means the table should be treated as context-bearing detail attached to PA_PERF_TRANSACTIONS, not as a standalone entity.

Key Information Stored

The table contains 10 documented columns. The most important are:

• COMMENT_ID — The surrogate primary key, enforced by the PA_PERF_COMMENTS_PK constraint and also supported by the unique index PA_PERF_COMMENTS_U1. This is the column referenced in the user's search term, "pa_perf_comments_pk".
• PERF_TXN_ID — Foreign key to PA_PERF_TRANSACTIONS. This is the sole documented foreign key and the primary linkage that positions each comment against its parent performance transaction.
• COMMENT_TEXT — The narrative content of the performance comment itself.
• COMMENTED_BY — The user who authored the comment.
• COMMENT_DATE — The date the comment was recorded, distinct from the row's audit timestamps.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN follow the standard Oracle EBS WHO-column convention, supporting traceability and change auditing.

Note that COMMENT_ID serves as both the primary key and a documented unique-index business-key candidate, so it is the single reliable identifier for joining and deduplication. There is no separate natural business key beyond this surrogate.

Common Use Cases and Queries

Typical scenarios include retrieving comment histories for a performance transaction, reporting comment activity by author, and surfacing commentary alongside project status data. A common join pattern follows the foreign key to the parent table:

• Joining PA_PERF_COMMENTS to PA_PERF_TRANSACTIONS on PERF_TXN_ID = PERF_TXN_ID to retrieve comments for a given transaction.
• Filtering by COMMENTED_BY and COMMENT_DATE to build activity or audit reports on who commented and when.
• Aggregating comment counts per transaction for performance tracking dashboards.

A representative query pattern selects COMMENT_ID, PERF_TXN_ID, COMMENT_TEXT, COMMENTED_BY, and COMMENT_DATE from PA_PERF_COMMENTS, filtered by a specific PERF_TXN_ID or a COMMENT_DATE range, ordered by COMMENT_DATE. Because COMMENT_TEXT is free-form, text searches are best performed with explicit predicates on that column.

Related Objects

The most significant related objects are:

• PA_PERF_TRANSACTIONS — The parent table, joined via PA_PERF_COMMENTS.PERF_TXN_ID = PA_PERF_TRANSACTIONS.PERF_TXN_ID. This is the only documented foreign key relationship and the principal dependency.
• PA_PERF_COMMENTS_PK and PA_PERF_COMMENTS_U1 — The primary key constraint and unique index on COMMENT_ID, which govern row identity and enforce uniqueness.
• Standard Oracle Projects performance reporting views and concurrent programs that consume performance transaction data and surface associated comments through Project Status Inquiry.

Given the limited documented relationships, PA_PERF_COMMENTS should be treated as a satellite object reachable almost exclusively through its PERF_TXN_ID linkage to PA_PERF_TRANSACTIONS.