Search Results per_events




Overview
Explore in AI Chat

Overview

PER_EVENTS is a core Human Resources (PER) transaction table in Oracle E-Business Suite 12.1.1 and 12.2.2, owned by the HR schema. As documented, it provides a "record of events such as interviews and appraisals for applicants and employees." The table therefore sits at the intersection of recruitment and HR performance management, capturing the scheduling, participants, and outcomes metadata associated with discrete events tied to either an employee or an applicant. Each row represents a single event instance — for example an interview, an appraisal meeting, or a related activity — identified by a unique EVENT_ID.

From a data modeling perspective, the metadata's heuristic Data Vault classification is satellite-leaning. PER_EVENTS carries descriptive and contextual attributes (dates, times, contacts, comments, and DFF columns) and holds foreign keys to reference entities such as BUSINESS_GROUP_ID and LOCATION_ID, but it does not by itself act as a pure hub or link. The classification should be treated as a modeling suggestion: the table behaves primarily as a descriptive satellite attached to the employee/applicant and organizational context, while downstream tables (PER_BOOKINGS, PER_PAY_PROPOSALS, PER_PERFORMANCE_REVIEWS) reference it, effectively making it a parent anchor for those child records.

Key Information Stored

The table contains 48 documented columns in the 12.2.2 physical schema. The most operationally significant columns are:

Common Use Cases and Queries

Recruitment and HR reporting frequently join PER_EVENTS to personnel and organizational tables. A typical interview-scheduling report joins to the assignment and location to resolve names:

  • Listing upcoming interviews by business group: filter on TYPE, EVENT_OR_INTERVIEW, and DATE_START, restricted by BUSINESS_GROUP_ID.
  • Auditing appraisal events for an employee: join PER_EVENTS to PER_PERFORMANCE_REVIEWS on EVENT_ID to find each review's underlying event.
  • Pay proposal traceability: join PER_PAY_PROPOSALS to PER_EVENTS on EVENT_ID to link pay changes to the originating HR event.
  • Booking/resource analysis: join PER_BOOKINGS on EVENT_ID to reconcile scheduled resources against each event.
  • Data extraction for analytics: select EVENT_ID, PARTY_ID, ASSIGNMENT_ID, DATE_START, and TYPE for a period, applying the DFF columns (ATTRIBUTE_CATEGORY, ATTRIBUTE1..20) for site-specific extensions.

A representative query pattern is: SELECT e.EVENT_ID, e.TYPE, e.DATE_START, e.DATE_END, e.LOCATION_ID FROM PER_EVENTS e WHERE e.BUSINESS_GROUP_ID = :bg AND e.DATE_START >= :from_date ORDER BY e.DATE_START;.

Related Objects

PER_EVENTS is both a referencing child and a referenced parent, creating a cohesive event picture:

  • HR_ALL_ORGANIZATION_UNITS — joined via BUSINESS_GROUP_ID and ORGANIZATION_RUN_BY_ID; supplies business group and running-organization context.
  • HR_LOCATIONS_ALL — joined via LOCATION_ID; supplies event location details.
  • PER_BOOKINGS — references PER_EVENTS via PER_BOOKINGS.EVENT_ID; records resource bookings for the event.
  • PER_PAY_PROPOSALS — references PER_EVENTS via PER_PAY_PROPOSALS.EVENT_ID; links pay proposals to their source event.
  • PER_PERFORMANCE_REVIEWS — references PER_EVENTS via PER_PERFORMANCE_REVIEWS.EVENT_ID; ties performance appraisals to the event record.

Together, these relationships confirm PER_EVENTS as a central HR event anchor supporting recruitment, appraisal, and compensation workflows across the PER module in Oracle EBS.