Search Results check_validity

Overview

APPS.PER_EVENTS_PKG is the table handler package for the PER_EVENTS entity within Oracle EBS Human Resources (PER). It encapsulates the business logic required to validate, insert, lock, update, and delete records in the PER_EVENTS and PER_EVENTS_S tables, which store event and interview scheduling data associated with people, assignments, and organizations. Because the package is declared AUTHID CURRENT_USER, it executes with the privileges of the calling schema rather than the definer, meaning callers must hold the appropriate grants on the underlying tables and dependent objects. The package header itself carries the identifier peevt01t.pkh, confirming its role as a public specification (the t suffix denotes the type/header file) shipped with the standard APPLDEV code line.

Functionally, the package addresses two intertwined domains. First, it provides generic table-handler operations so that forms and APIs maintain PER_EVENTS rows consistently. Second, it enforces HR-specific business rules around interviews and letters, including validity checking of an interviewer's contact details, detection of double bookings, and management of interview-related correspondence such as offer or rejection letters.

Key Procedures and Functions

Ten documented procedures and functions make up the package interface:

• CHECK_VALIDITY — Validates an interview event by accepting the internal contact person, start date, organization run-by, business group, end-of-time global, location, and event identifier. It confirms that the combination of interviewer, timing, and organizational context is permissible before the event is recorded.
• INTERVIEWERS_ARE_BOOKED — A Boolean function returning whether interviewers are booked for a given event. An optional flag allows the caller to raise an error when the condition is true.
• CHECK_CURRENT_INTERVIEWERS — Re-evaluates the interviewers attached to an event when the interview start date changes, ensuring no conflicts arise from the reschedule.
• REQUEST_LETTER — Initiates a letter request for a person/assignment, accepting business group, session date, user and login identifiers, assignment status type, person, and assignment. It drives the letter-generation workflow for HR correspondence.
• EVENT_CAUSES_ASSIGNMENT_CHANGE — Determines whether a dated event triggers an assignment change, returning a Boolean used to gate further processing.
• INTERVIEW_DOUBLE_BOOKED — Returns TRUE if the applicant already has an interview at the requested time, using person, interview start date, and start/end time strings (the latter added for bug 3270091).
• INSERT_ROW, LOCK_ROW, UPDATE_ROW, DELETE_ROW — Standard table-handler DML operations that create, lock, modify, and remove PER_EVENTS records while enforcing the package's validation rules.

Tables Accessed

The package reads and writes through APPS synonyms. It directly owns PER_EVENTS and PER_EVENTS_S. It consults PER_ALL_ASSIGNMENTS_F and PER_ALL_PEOPLE_F for assignment and person context, PER_BOOKINGS for booking records, and PER_PAY_PROPOSALS where pay implications arise. Letter handling touches PER_LETTER_REQUESTS, PER_LETTER_REQUESTS_S, PER_LETTER_REQUEST_LINES, PER_LETTER_REQUEST_LINES_S, and PER_LETTER_GEN_STATUSES to track request status and generated output.

Usage Notes

PER_EVENTS_PKG is invoked principally from the Oracle HR forms that create and manage events and interviews, and from the letter-request workflow. It is referenced by one other package, indicating a modest dependency footprint. Custom code should call the documented procedures rather than issuing direct DML, because the validity checks — in particular CHECK_VALIDITY and INTERVIEW_DOUBLE_BOOKED — enforce constraints that a raw insert or update would bypass. The table-handler entry points (INSERT_ROW, LOCK_ROW, UPDATE_ROW, DELETE_ROW) supply the supported path for programmatic maintenance of PER_EVENTS data in both 12.1.1 and 12.2.2.