Search Results per_performance_reviews_pk




Overview
Explore in AI Chat

Overview

The HR.PER_PERFORMANCE_REVIEWS table is the core transactional store for employee performance evaluation data in the Oracle E-Business Suite PER (Human Resources) module. Each row captures a single performance review event for a person, linking the review outcome to an HR event record and to downstream compensation proposals. In releases 12.1.1 and 12.2.2 the object is owner-qualified as HR.PER_PERFORMANCE_REVIEWS, reported with VALID status and a documented physical schema of 43 columns.

From a Data Vault modeling perspective, the FK topology mined from the dictionary suggests a satellite-leaning classification. The table describes attributes of a review occurrence rather than acting as an independent hub of business entities, and it hangs off PER_EVENTS through EVENT_ID. This classification is a heuristic modeling suggestion rather than a physical constraint; the table remains a conventional third-normal-form EBS entity.

Key Information Stored

The surrogate primary key is PERFORMANCE_REVIEW_ID, enforced by the unique index PER_PERFORMANCE_REVIEWS_PK. This index is the only documented unique constraint and therefore the sole business-key candidate at the physical level, although the natural business identity of a review is normally the combination of person and event context.

The most operationally significant columns are:

Common Use Cases and Queries

Typical reporting retrieves the latest rating per employee, the review history for a person, or reviews due within a period. A representative query joining the review to its event is:

  • SELECT pr.performance_review_id, pr.person_id, pr.review_date, pr.performance_rating, pr.next_perf_review_date FROM per_performance_reviews pr WHERE pr.person_id = :person_id ORDER BY pr.review_date DESC;
  • Identifying overdue reviews: filter on NEXT_PERF_REVIEW_DATE < SYSDATE for active employees.
  • Compensation analysis: join PER_PAY_PROPOSALS on PERFORMANCE_REVIEW_ID to correlate ratings with proposed salary changes.
  • Event reconciliation: join PER_EVENTS on EVENT_ID to obtain event type and status context.

Because the flexfield columns are client-configured, queries on ATTRIBUTE* should be validated against the customer's descriptive flexfield definition before use in production reports.

Related Objects

Relationship metadata shows the following significant dependencies:

  • PER_PERFORMANCE_REVIEWS.EVENT_ID → PER_EVENTS — the parent event driving the review.
  • PER_PAY_PROPOSALS.PERFORMANCE_REVIEW_ID → PER_PERFORMANCE_REVIEWS — downstream compensation proposals referencing the review.
  • PER_PERFORMANCE_REVIEWS_PK — the primary key index on PERFORMANCE_REVIEW_ID.

The person reference via PERSON_ID logically joins to the PER_ALL_PEOPLE_F person/assignment model, and the standard WHO columns integrate with the common audit framework. Together these objects form the performance management chain from event through evaluation to pay proposal.