Results for “hrfv_reviews”

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

Overview

APPS.HRFV_REVIEWS is a business view template shipped with the Oracle E-Business Suite Human Resources (PER) product. It is a flexfield view generated from a template, designed to expose employee review and performance data in a flattened, report-friendly structure. The view resides in the APPS schema and holds VALID status in both EBS 12.1.1 and 12.2.2. Its primary role is to surface employee review events (interviews and performance reviews) joined across the business group, person, assignment, location, and performance review tables, presenting decoded lookups rather than raw codes so that it can be consumed directly by Oracle Business Intelligence (BIS) reporting, custom reports, and integration extracts.

The view is defined with a WITH READ ONLY clause, confirming it is strictly a reporting artifact; no DML is permitted. Because it lives in APPS and is built on top of secured objects, it participates in the standard EBS security model through HR_BIS.GET_SEC_PROFILE_BG_ID, meaning results are automatically filtered by the caller's business group security profile.

Underlying Base Objects

The view is documented as being defined over a set of synonyms, views, and packages owned or referenced within APPS. The core data originates from PER_EVENTS (aliased EVT), which supplies the review event, and PER_PERFORMANCE_REVIEWS (aliased PRV), which supplies the performance review details. These are joined to PER_PEOPLE_X (PEO), PER_ALL_ASSIGNMENTS_F (ASG), HR_LOCATIONS_ALL_TL (LOCT), and HR_ALL_ORGANIZATION_UNITS_TL (BGRT) to enrich each row with person, assignment, location, and business group descriptions.

Several packages are referenced during evaluation: HR_BIS for the BIS_DECODE_LOOKUP and security profile functions, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY. The join to PER_PERFORMANCE_REVIEWS is an outer join (EVT.EVENT_ID = PRV.EVENT_ID (+)), so interview events without an associated performance review are still returned. Location and business group translations are restricted to the session language via USERENV('LANG'), and assignments are date-effectively bounded by the event date start.

Key Columns

• BUSINESS_GROUP_NAME — the business group under which the review event was recorded.
• PERSON_NAME, EMPLOYEE_NUMBER — the reviewed employee's full name and employee number.
• ASSIGNMENT_NUMBER — the assignment the review event is tied to.
• REVIEW_TYPE — decoded value from the EMP_INTERVIEW_TYPE lookup.
• REVIEW_DATE — the start date of the review event (from PER_EVENTS.DATE_START).
• PERFORMANCE_REVIEW_DATE, NEXT_PERFORMANCE_REVIEW_DATE — dates from the performance review record.
• PERFORMANCE_RATING — decoded value from the PERFORMANCE_RATING lookup; this is the column most directly relevant to a "performance_rating" search.
• CURRENT_EMPLOYEE_FLAG — decoded YES/NO flag indicating current employment status.
• REVIEW_LOCATION — the location code of the review.
• IDENTIFIERS — ASSIGNMENT_ID, BUSINESS_GROUP_ID, EMPLOYEE_REVIEW_ID, LOCATION_ID, PERFORMANCE_REVIEW_ID, PERSON_ID provide the keys needed to join back to base tables or drive drill-down reports.

Common Use Cases and Queries

Typical scenarios include performance rating distribution reports, review scheduling dashboards, and integration extracts feeding a data warehouse. A standard query filtering on rating counts is shown below:

• SELECT person_name, employee_number, performance_rating, performance_review_date FROM apps.hrfv_reviews WHERE performance_rating IS NOT NULL;
• SELECT performance_rating, COUNT(*) FROM apps.hrfv_reviews GROUP BY performance_rating;
• SELECT person_name, review_type, review_date FROM apps.hrfv_reviews WHERE review_date BETWEEN :start_date AND :end_date;

Because the view enforces business group security automatically, no additional predicate is normally required, though a report can filter on business_group_name for a specific operating unit perspective.