Search Results chk_performance_review_id

Overview

APPS.PER_PRV_BUS is the business-layer package body in Oracle E-Business Suite that supports the Performance Reviews entity within Oracle Human Resources (Oracle HRMS). Its naming convention follows the Oracle Designer / HRMS generator standard: the _BUS suffix identifies the business-level API that sits above the view (_V), shared (_SHD), and row-handler (_RHI) tiers of the same object. The package encapsulates the validation and maintenance logic for the PER_PERFORMANCE_REVIEWS table, shielding callers from the physical table structure while enforcing business rules such as primary-key integrity, date consistency, and legislative applicability.

As reflected in the ETRM metadata, the package is classified as API classification OTHER and is referenced by three other packages, indicating that it is an internal, dependent business layer rather than a top-level public API. The header revision identifier peprvrhi.pkb 120.1 confirms that the object is seeded as part of the standard HRMS library and should not be modified without an Oracle patch or an approved customisation strategy.

Key Procedures and Functions

The 12.2.2 metadata documents eight procedures and functions:

• CHK_PERSON_ID_DATE — Validates the relationship between the person identifier and the associated review dates, ensuring that a performance review is anchored to a valid person and a sensible date range.
• CHK_NEXT_PERF_REVIEW_DATE — Checks the next performance review date on the record for logical consistency against the current review period.
• CHK_GET_NEXT_PERF_REVIEW_DATE — A validation variant that derives or confirms the next review date during insert or update processing.
• CHK_DELETE_PERFORMANCE_REVIEW — Applies the rules that determine whether a performance review row may be deleted (for example, preventing deletion of rows referenced by downstream business processes).
• INSERT_VALIDATE — Row-level validation invoked before a new performance review record is written.
• UPDATE_VALIDATE — Row-level validation invoked before an existing performance review record is modified.
• DELETE_VALIDATE — Row-level validation invoked before a performance review record is removed.
• RETURN_LEGISLATION_CODE — Returns the legislation code that governs the record, used to apply legislation-specific (localisation) rules during processing.

The package body also declares chk_performance_review_id, shown in the source excerpt, which verifies that the primary key is null on insert and is not updated afterwards, consistent with the standard HRMS generated row-handler pattern.

Tables Accessed

The package touches the following tables through APPS synonyms:

• PER_PERFORMANCE_REVIEWS — the primary entity table holding the review records that this API validates and maintains.
• PER_ALL_PEOPLE_F — the person master, used to confirm the person for whom the review is created and to resolve person-level attributes.
• PER_ALL_ASSIGNMENTS_F — the assignment records, used to relate reviews to the correct employee assignment and its effective dates.
• PER_PAY_PROPOSALS — used where a performance review feeds into a pay or salary proposal workflow.
• PER_EVENTS — the HRMS event/date-tracked table, used to record or query dated events associated with the review.

Usage Notes

PER_PRV_BUS is normally invoked indirectly. Oracle HRMS forms and the generated _API wrapper layer call into the business package when a user creates, updates, or deletes a performance review. Concurrent programs and Oracle HRMS date-track and event routines also rely on it for validation. Because the user search term was get_frequency, it is worth noting that the documented procedure list does not include any frequency accessor; frequency or periodicity data for performance reviews is not exposed through this business package in the documented 12.2.2 metadata, and callers seeking periodicity should inspect related configuration or lookup tables.

Custom code should treat this package as internal. Direct calls bypass supported entry points and may break when Oracle applies patches. Where customisations are required, integration should target the public API layer rather than PER_PRV_BUS itself.