Search Results per_events_api




Overview
Explore in AI Chat

Overview

The APPS.PER_EVENTS_API package body provides the supported programmatic interface for creating, maintaining, and removing event and interview records within Oracle E-Business Suite Release 12.1.1 and 12.2.2. Events in the Oracle Human Resources (PER) schema represent scheduled activities such as recruitment interviews, meetings, and other personnel-related appointments. The package encapsulates the business rules, validation logic, and table maintenance required to keep the underlying PER_EVENTS entity consistent, shielding callers from direct DML against the base tables. It is classified as an API in the ETRM repository under the APPS schema, indicating that it is a public, supported entry point intended for use by Oracle forms, concurrent programs, and customer extensions.

Key Procedures and Functions

The documented interface exposes three procedures:

  • CREATE_EVENT — Inserts a new event or interview record. The procedure accepts a start date and an event type as required inputs, with a p_validate flag that allows callers to run validation in isolation before committing. Optional parameters cover the business group, location, internal contact person, organization running the event, assignment, contact telephone number, end date, employee-or-applicant indicator, event-or-interview indicator, external contact details, start and end times, and a full set of descriptive flexfield attributes (p_attribute_category and p_attribute1 through p_attribute18). Note that p_business_group_id carries the HR/TCA merge annotation, reflecting multi-organization support.
  • UPDATE_EVENT — Modifies an existing event record, applying the same validation framework and allowing selective updates to scheduling, contact, and descriptive flexfield information.
  • DELETE_EVENT — Removes an event record from the system after confirming that no dependent data prevents its deletion.

Tables Accessed

The package body operates against the core Human Resources event tables exposed through APPS synonyms, principally PER_EVENTS, which stores the event header information populated by CREATE_EVENT and amended by UPDATE_EVENT. Supporting validation draws on reference and lookup data within the PER schema for event types and business group context, and on organization, location, and person/assignment data to resolve the foreign key identifiers passed as parameters. Descriptive flexfield segments are written to the appropriate attribute columns of the event entity. Because the ETRM metadata for this object lists tables only indirectly, the precise table inventory should be confirmed against the package body source in the target instance.

Usage Notes

PER_EVENTS_API is typically invoked from the Oracle HRMS event and interview maintenance forms, from recruitment-related concurrent programs, and from custom PL/SQL extensions that must create or maintain events without direct table manipulation. The package is referenced by eight other packages within the APPS schema, confirming its role as a shared service layer. Callers should always use the API rather than inserting into PER_EVENTS directly, because the procedures enforce mandatory-column, date-range, and flexfield validation. When integrating, set p_validate to TRUE to test inputs before committing, and supply p_business_group_id explicitly in multi-business-group installations to ensure correct data segregation under the HR/TCA model.