Search Results per_bookings




Overview
Explore in AI Chat

Overview

The PER_BOOKINGS table is a core data object within the Oracle E-Business Suite (EBS) Human Resources (HR) module, specifically under the PER (Personnel) product family. It serves as the primary transactional repository for recording and managing event booking details. In the context of Oracle EBS 12.1.1 and 12.2.2, this table is fundamental to functionalities related to training, development, and other scheduled organizational events. Its role is to maintain a detailed record of each booking instance, linking participants (employees or other persons) to specific scheduled events and capturing the associated administrative and logistical details of that registration.

Key Information Stored

The table's structure is designed to capture the essential elements of an event booking. The primary key, BOOKING_ID, uniquely identifies each booking record. As indicated by the foreign key relationships, two critical foreign keys anchor the booking within the HR data model: EVENT_ID links to the PER_EVENTS table to define the specific event being booked, and BUSINESS_GROUP_ID links to HR_ALL_ORGANIZATION_UNITS to enforce data security and partitioning at the business group level. While the provided metadata does not list all columns, typical data stored in such a table would include the PERSON_ID (the attendee), booking status (e.g., Confirmed, Waitlisted, Cancelled), booking date, internal chargeback information, attendance confirmation flags, and potentially cost and payment details associated with the booking.

Common Use Cases and Queries

This table is central to reporting and operational processes surrounding event management. Common use cases include generating participant rosters for trainers, managing waitlists for oversubscribed events, tracking attendance records for compliance or certification purposes, and analyzing training participation rates across departments. A typical reporting query might join PER_BOOKINGS with PER_EVENTS and PER_ALL_PEOPLE_F to list all bookings for a specific event.

SELECT pb.booking_id,
       ppf.full_name attendee,
       pe.event_name,
       pb.booking_status,
       pb.booking_date
  FROM hr.per_bookings pb,
       hr.per_events pe,
       hr.per_all_people_f ppf
 WHERE pb.event_id = pe.event_id
   AND pb.person_id = ppf.person_id
   AND pe.event_id = :p_event_id
   AND SYSDATE BETWEEN ppf.effective_start_date AND ppf.effective_end_date;

Another common operational query would identify all upcoming event bookings for a given employee to facilitate calendar management and planning.

Related Objects

  • PER_EVENTS: This is the primary parent table, as defined by the foreign key PER_BOOKINGS.EVENT_ID. It holds the master definition of the event (title, date, location, capacity) for which bookings are created.
  • HR_ALL_ORGANIZATION_UNITS: The foreign key on BUSINESS_GROUP_ID links to this table, securing the booking data within the correct business group as per the Oracle HRMS security model.
  • PER_ALL_PEOPLE_F: Although not listed in the provided foreign keys, a functional foreign key relationship almost certainly exists from a PERSON_ID column in PER_BOOKINGS to this table to identify the attendee.
  • APIs and Views: Standard Oracle HRMS APIs for event management (potentially within the PER_TSH_API package or similar) will internally create, update, and delete records in the PER_BOOKINGS table. Reporting is often done through predefined HRMS views that join this table to its related entities.