Search Results sys_il0000043565c00035

Overview

HR.PER_BOOKINGS is a transactional table in the Oracle E-Business Suite Human Resources (HR) schema that stores booking records associated with persons and HR events. In Oracle EBS 12.1.1 and 12.2.2, this object participates in the Oracle Human Resources Management System (HRMS) functional area and is registered under the FND Design Data application as PER.PER_BOOKINGS. The object is documented as a table with status VALID and is owned by the HR schema.

From a data-modeling perspective, the ETRM metadata heuristic classifies PER_BOOKINGS as a link entity within a Data Vault-style interpretation. This classification is suggested by the foreign key structure, which connects a person, a business group, and an HR event, thereby resolving many-to-many or associative relationships between core business entities. It should be treated as a modeling suggestion rather than an authoritative Data Vault designation.

Physically, the table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. It includes a unique primary key index (PER_BOOKINGS_PK) and a LOB index named SYS_IL0000043565C00035$$, which is the object identifier matching the user's search string. That identifier is a system-generated LOB segment name rather than a business attribute, and it confirms the presence of a Large Object column in the physical schema despite the column list not enumerating it in the excerpt.

Key Information Stored

The table contains 36 documented columns. The most significant include:

• BOOKING_ID (NUMBER 15) — the system-generated surrogate primary key, uniquely identifying each booking record via PER_BOOKINGS_PK. This is the sole documented unique index and therefore the only business-key candidate in the metadata.
• BUSINESS_GROUP_ID (NUMBER 15, mandatory) — foreign key to HR_ALL_ORGANIZATION_UNITS, partitioning data by operating business group.
• PERSON_ID (NUMBER 10) — foreign key to PER_PEOPLE, identifying the person for whom the booking is recorded.
• EVENT_ID (NUMBER 15) — foreign key to PER_EVENTS, linking the booking to a specific HR event such as a training or interview event.
• PRIMARY_INTERVIEWER_FLAG — indicates whether the associated person acts as the primary interviewer for the event.
• COMMENTS — free-text annotations attached to the booking.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Standard Who columns capturing the concurrent request and program context that last touched the row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE20 — descriptive flexfield columns supporting extensible descriptive data.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard Who audit columns.

Common Use Cases and Queries

Typical reporting scenarios include listing all bookings for a person, retrieving all bookings tied to a specific HR event, and identifying primary interviewers. Example SQL patterns:

• Bookings by person: SELECT * FROM HR.PER_BOOKINGS WHERE PERSON_ID = :person_id;
• Bookings for an event: SELECT * FROM HR.PER_BOOKINGS WHERE EVENT_ID = :event_id;
• Primary interviewer lookup: SELECT PERSON_ID FROM HR.PER_BOOKINGS WHERE EVENT_ID = :event_id AND PRIMARY_INTERVIEWER_FLAG = 'Y';
• Join to people for names: SELECT p.full_name, b.booking_id FROM HR.PER_BOOKINGS b JOIN PER_PEOPLE_F p ON p.person_id = b.person_id WHERE b.event_id = :event_id;

Because Oracle designates this object for internal use only, direct SQL should be confined to query and reporting scenarios, with all data manipulation performed through standard Oracle Applications programs or supported APIs.

Related Objects

• HR_ALL_ORGANIZATION_UNITS — joined via BUSINESS_GROUP_ID; defines the business group context.
• PER_EVENTS — joined via EVENT_ID; the parent event definition.
• PER_PEOPLE_F / PER_PEOPLE — referenced via PERSON_ID; the person associated with the booking.
• PER_BOOKINGS_PK — the unique primary key index on BOOKING_ID.
• PER_BOOKINGS_FK1 / PER_BOOKINGS_FK3 / PER_BOOKINGS_N2 — supporting indexes on BUSINESS_GROUP_ID, EVENT_ID, and PERSON_ID respectively, which are the primary access paths for the join patterns above.