Results for “per_performance_reviews_v”

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

Overview

PER_PERFORMANCE_REVIEWS_V is an Oracle E-Business Suite view owned by the APPS schema within the PER (Human Resources) product module. It is a user-interface support view, meaning it exists primarily to present performance review data in a form convenient for Oracle Forms-based or OAF-based application screens rather than to serve as a general-purpose reporting entity. The view consolidates the core performance review record with translated lookups and location descriptions so that a single query returns decoded, display-ready values instead of raw codes.

Because the view exposes the ROWID of the underlying base table and includes the OBJECT_VERSION_NUMBER and standard WHO audit columns, it supports both query-only presentation and the update-through-view pattern used by Oracle Forms. In release 12.1.1 and 12.2.2, the view remains VALID, and its definition is consistent across the documented metadata.

Underlying Base Objects

The documented base objects referenced by the view are PER_PERFORMANCE_REVIEWS (synonym), PER_EVENTS (synonym), HR_LOCATIONS_NO_JOIN (view), HR_LOCATIONS_ALL_TL (synonym), HR_LOOKUPS (view), HR_GENERAL (package), and HR_API (package). The packages provide the business logic and validation layers that back the view's DML behavior when accessed through the application.

The FROM clause joins PER_PERFORMANCE_REVIEWS (aliased PRV) as the driving table to PER_EVENTS (EVT) via EVENT_ID, and to HR_LOCATIONS_ALL_TL (LOCTL) through the HR_LOCATIONS_NO_JOIN (LOC) view for translated location details. Two instances of HR_LOOKUPS supply decoded meanings: HL1 resolves the interview/event type from EMP_INTERVIEW_TYPE, and HL2 resolves PERFORMANCE_RATING. All joins to the event, location, and lookup tables are outer joins (indicated by the (+) operator), so performance review rows survive even when the related event, location, or lookup value is missing. The language restriction uses DECODE and USERENV('LANG') to return translated location descriptions matching the session language.

Key Columns

• ROW_ID — the ROWID of the underlying PER_PERFORMANCE_REVIEWS row, used to identify and lock the base record.
• PERFORMANCE_REVIEW_ID — primary key of the performance review.
• PERSON_ID — the person whose review is recorded.
• EVENT_ID / EVENT_TYPE / EVENT_LOCATION — the associated PER_EVENTS record, its decoded interview type from HR_LOOKUPS, and the location code from HR_LOCATIONS.
• REVIEW_DATE — date of the review.
• PERFORMANCE_RATING / RATING_MEANING — the rating code and its decoded meaning from HR_LOOKUPS.
• NEXT_PERF_REVIEW_DATE — scheduled date of the subsequent review.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 — descriptive flexfield segments.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — concurrency and audit columns.

Common Use Cases and Queries

Typical use cases include performance review inquiries, employee review history screens, and ad hoc reporting joins to per_all_people_f for employee names. A basic query is:

SELECT performance_review_id,
       person_id,
       event_type,
       review_date,
       rating_meaning,
       next_perf_review_date
FROM   apps.per_performance_reviews_v
WHERE  person_id = :p_person_id
ORDER  BY review_date DESC;

To report ratings by location, join the view to per_all_people_f and filter by rating_meaning. Analysts should note the outer joins and language-dependent location column, and should treat this view as UI-support rather than a canonical integration interface.