Search Results per_bookings_pk

Overview

PER_BOOKINGS is a Human Resources (PER) module table in the HR schema of Oracle E-Business Suite, holding event booking details. It records the association between a person, an event defined in PER_EVENTS, and the business group that owns the record, and is typically populated when an employee or applicant enrolls in a training, recruitment, or career-management event managed through Oracle HRMS event functionality.

The table carries 36 documented columns in release 12.2.2 and is owned by the HR schema. Its structure is characteristic of a transactional association table: it captures a unique booking transaction, links to two principal parents (business group and event), and carries a large attribute flexfield block (ATTRIBUTE_CATEGORY plus ATTRIBUTE1 through ATTRIBUTE20) plus standard WHO audit columns. Based on the foreign-key structure mined from the ETRM metadata, the heuristic Data Vault classification is link — it resolves the many-to-many relationship between a person/booking and the event it references, rather than functioning as a hub (unique business entity) or a satellite (descriptive history).

Key Information Stored

The surrogate primary key is BOOKING_ID, enforced through the unique index PER_BOOKINGS_PK. The remaining documented columns fall into functional groups:

• BOOKING_ID — system-generated surrogate identifier; the primary key.
• BUSINESS_GROUP_ID — foreign key to HR_ALL_ORGANIZATION_UNITS; identifies the business group (legislative/operating unit) context of the booking.
• EVENT_ID — foreign key to PER_EVENTS; identifies the event being booked.
• PERSON_ID — the person (employee or applicant) for whom the booking is made.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID — identify the concurrent request and program that created or last processed the row, supporting reconciliation and concurrent-manager diagnostics.
• PROGRAM_UPDATE_DATE — timestamp of the last programmatic update.
• PRIMARY_INTERVIEWER_FLAG — indicates whether the booked person is the primary interviewer for the associated event.
• COMMENTS — free-text remarks attached to the booking.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — the descriptive flexfield (DFF) segment block for customer-specific extensions.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard WHO audit columns.

No alternate business-key unique index is documented beyond PER_BOOKINGS_PK; the only other index listed, SYS_IL0000043565C00035$$, is a system-generated LOB index and is not a business-key candidate.

Common Use Cases and Queries

Typical uses include reporting event attendance and interviewer assignments, validating participant loads per event, and auditing concurrent-program outcomes. A representative join retrieves bookings with their event and person context:

• SELECT b.booking_id, b.person_id, e.event_id, e.name, b.primary_interviewer_flag FROM per_bookings b, per_events e WHERE b.event_id = e.event_id;
• Count bookings per event: SELECT event_id, COUNT(*) FROM per_bookings GROUP BY event_id;
• Filter by DFF segment: SELECT * FROM per_bookings WHERE attribute_category = :category AND attribute1 = :value;
• Trace creation origin: SELECT booking_id, request_id, program_application_id, program_id FROM per_bookings WHERE creation_date >= :from_date;

Because DFF columns are customer-defined, reporting on ATTRIBUTE1–ATTRIBUTE20 requires knowledge of the value set and descriptive flexfield context in use at the deployment.

Related Objects

The following objects are significant given the FK and PK relationships documented for PER_BOOKINGS:

• PER_EVENTS — parent of EVENT_ID; supplies the event definition that each booking references. This is the primary join target.
• HR_ALL_ORGANIZATION_UNITS — parent of BUSINESS_GROUP_ID; supplies the business-group context and supports security-group filtering.
• PER_BOOKINGS_PK — the unique index enforcing the surrogate primary key on BOOKING_ID.
• PER_ALL_PEOPLE_F — the underlying person entity corresponding to PERSON_ID; used to resolve names and person attributes.
• FND_CONCURRENT_REQUESTS — resolves REQUEST_ID to the concurrent request that created or updated the booking.
• FND_APPLICATION / FND_PROGRAM — resolve PROGRAM_APPLICATION_ID and PROGRAM_ID to the concurrent program definition.

Together these objects place PER_BOOKINGS at the intersection of event definition, person identity, and business-group security within Oracle HRMS.