Search Results per_prv_bus




Overview
Explore in AI Chat

Overview

APPS.PER_PRV_BUS is a business-layer PL/SQL package within the Oracle EBS Human Resources (Oracle HRMS) product family, responsible for enforcing the validation rules that surround the PER_PERFORMANCE_REVIEWS entity. The package is classified as an "OTHER" API in the ETRM repository, meaning it is intended primarily as an internal table handler rather than as a public, externally supported interface. Its source header (peprvrhi.pkh) confirms this designation, opening with two private global variables reserved exclusively for the return_legislation_code function and documenting each procedure as "Internal table handler use only."

The package encapsulates the row-level business logic that governs performance review records: verifying that the person referenced is a valid employee on the review date, preventing duplicate reviews, ensuring the next review date follows the current review date, and supporting the standard insert, update, and delete validation cycle. Consolidating these checks in a single package ensures consistent behaviour whether records are maintained through Oracle Forms or through programmatic DML. The package references five core HRMS tables via APPS synonyms and is referenced by three other packages in the ETRM repository, indicating its role as a shared validation dependency within the HRMS schema.

Key Procedures and Functions

  • CHK_PERSON_ID_DATE — Verifies that the person identified is an employee on the given date and that the review date is not a duplicate for that person.
  • CHK_NEXT_PERF_REVIEW_DATE — Confirms that the next performance review date falls after the current review date and that the associated person exists as an employee on that date.
  • CHK_GET_NEXT_PERF_REVIEW_DATE — Supports retrieval and validation of the next performance review date. This is the object most frequently associated with the search term chk_get_next_perf_review_date, which is commonly raised when date-derivation logic for performance reviews fails validation.
  • CHK_DELETE_PERFORMANCE_REVIEW — Performs the deletion-time validation checks for a performance review record before the row is removed.
  • INSERT_VALIDATE — Runs the complete validation set applied when a new performance review row is created.
  • UPDATE_VALIDATE — Runs the validation set applied when an existing performance review row is modified.
  • DELETE_VALIDATE — Runs the validation set applied when a performance review row is deleted.
  • RETURN_LEGISLATION_CODE — Returns the legislation code associated with the record, using the package's private global variables for caching. Because of this shared state, the function should be treated with care in concurrent sessions.

Tables Accessed

  • PER_PERFORMANCE_REVIEWS — The primary entity maintained by this package; all validations are anchored to its rows.
  • PER_ALL_PEOPLE_F — Datetracked person records, used to confirm that the person exists as an employee on the applicable review date.
  • PER_ALL_ASSIGNMENTS_F — Assignment records, used to establish that the person holds a valid employee assignment on the given date.
  • PER_EVENTS — Event records referenced in the performance review validation chain.
  • PER_PAY_PROPOSALS — Pay proposal records consulted as part of the broader HRMS validation context.

Usage Notes

PER_PRV_BUS is invoked most commonly from the Oracle HRMS Performance Management forms when users create, modify, or delete performance review records. The INSERT_VALIDATE, UPDATE_VALIDATE, and DELETE_VALIDATE entry points form the standard table-handler contract called by the form's DML triggers, while the individual CHK_ procedures are called internally by those validators.

Because the package is documented as internal table-handler use only, direct invocation from custom code is not recommended. When custom PL/SQL must insert or update performance reviews, the supported approach is to call the appropriate table handler, or to route changes through the DML operations that trigger it, so that the full validation chain executes. Errors raised by this package typically surface as form-level messages during save operations, and the most frequent cause of failure in the chk_get_next_perf_review_date path is a next review date that is earlier than or equal to the current review date, or a person who is not an active employee on the derived date. The three dependent packages that reference PER_PRV_BUS should be reviewed for compatibility before any patching or schema change affecting performance review validation.