Results for “hrfv_reviewers”

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

Overview

HRFV_REVIEWERS is a business view template owned by the APPS schema in Oracle E-Business Suite, classified under the PER (Human Resources) product family. As documented in the ETRM metadata for release 12.2.2, the object is a VIEW with VALID status. Its official description states that it is a "business view template from which the flexfield view is generated," positioning it as the foundation layer from which Oracle's flexfield-driven business views are instantiated rather than as an end-user reporting object in its own right. In practice, HRFV_REVIEWERS consolidates data about employee review meetings and their assigned reviewers — spanning the reviewee, the reviewer, the assignment, the business group, and the review event itself — into a single denormalized projection. It is commonly accessed for HR analytics, integration extracts, and any reporting need that requires mapping reviewers to review events. The view is created WITH READ ONLY, meaning it cannot be used as the target of DML; it serves strictly as a query surface. References to the _DF derived-flex column and to internal packages such as HR_BIS, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY confirm that the view participates in the Oracle HRMS DateTrack and security architecture, applying language and security-profile filters at runtime.

Underlying Base Objects

The view is defined over a set of documented base objects: HR_ALL_ORGANIZATION_UNITS_TL, PER_ALL_PEOPLE_F, PER_PEOPLE_X, PER_ALL_ASSIGNMENTS_F, PER_EVENTS, PER_BOOKINGS, and the HR_BIS package, with additional dependencies on HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY. Most are exposed as synonyms in the APPS schema, while PER_PEOPLE_X is itself a view. The joins are significant: PER_ALL_PEOPLE_F appears twice — once for the reviewee (RER alias) and once for the reviewer (REE alias) — reflecting the fact that a review event links two people. PER_BOOKINGS bridges reviewer to event, and PER_EVENTS carries the review definition, type, and start date. The assignment is filtered so that the event date falls between the assignment's effective start and end dates, while the reviewer record is restricted by TRUNC(SYSDATE) between effective dates, enforcing current-row semantics. Language filtering via USERENV('LANG') and business-group security via HR_BIS.GET_SEC_PROFILE_BG_ID ensure the view respects localization and data security.

Key Columns

The view exposes a set of descriptive and key columns. BUSINESS_GROUP_NAME, REVIEWEE_NAME, REVIEWEE_EMPLOYEE_NUMBER, and REVIEWEE_ASSIGNMENT_NUMBER describe the person being reviewed. REVIEW_TYPE and PLANNED_REVIEW_DATE derive from PER_EVENTS and the EMP_INTERVIEW_TYPE lookup. REVIEWEE_CURRENT_EMPLOYEE_FLAG decodes the YES_NO lookup from the current employee flag. REVIEWER_NAME and REVIEWER_EMPLOYEE_NUMBER identify the reviewer. The identifier columns are the most important for joins and integrations: EMPLOYEE_REVIEW_ID maps to EVT.EVENT_ID, EMPLOYEE_REVIEWER_ID maps to BKG.BOOKING_ID, REVIEWEE_ASSIGNMENT_ID maps to EVT.ASSIGNMENT_ID, REVIEWEE_PERSON_ID maps to the reviewee person record, and the column the user searched for — REVIEWER_PERSON_ID — maps to RER.PERSON_ID, uniquely identifying the reviewer. A "_DF" column supports derived flexfield content, and BUSINESS_GROUP_ID ties the row to its organization.

Common Use Cases and Queries

The most frequent use case is locating reviewers for a given review event, or listing reviews by reviewer. For example, to find all reviews assigned to a specific reviewer:

• SELECT Employee_Review_Id, Reviewee_Name, Reviewer_Name, Planned_Review_Date FROM apps.hrfv_reviewers WHERE Reviewer_Person_Id = :p_reviewer_person_id;
• SELECT Business_Group_Name, Reviewee_Name, Reviewer_Name FROM apps.hrfv_reviewers WHERE Planned_Review_Date BETWEEN :p_start AND :p_end;
• SELECT Employee_Reviewer_Id, Reviewee_Assignment_Id, Review_Type FROM apps.hrfv_reviewers WHERE Reviewee_Person_Id = :p_reviewee_person_id;
• SELECT Reviewer_Person_Id, Reviewer_Name, COUNT(*) reviews FROM apps.hrfv_reviewers GROUP BY Reviewer_Person_Id, Reviewer_Name;

Because the view is READ ONLY and security-filtered, these queries automatically honor the caller's business-group security profile and language. Developers embedding it into concurrent programs or OAF pages should treat it as a stable query surface rather than a data-maintenance interface.