Results for “per_events_v3”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PER_EVENTS_V3 is an APPS-owned database view within the Oracle E-Business Suite Human Resources (PER) product family. Its documented purpose is to support the user interface, serving as a presentation-layer construct rather than a standalone transactional entity. The view consolidates interview-related event data with assignment, status, location, and lookup information so that a single query can return a fully described interview record. Because the object resides in the APPS schema and is marked VALID in ETRM, it is intended to be referenced directly by forms, concurrent programs, or custom reporting. In Oracle EBS 12.1.1 and 12.2.2 environments, such interface-supporting views are frequently used by Oracle Forms blocks and by customers building custom reports or integrations against the Human Resources module.

Underlying Base Objects

The ETRM metadata documents the referenced base objects as HR_API (PACKAGE), HR_GENERAL (PACKAGE), HR_LOCATIONS (VIEW), HR_LOOKUPS (VIEW), PER_ALL_ASSIGNMENTS_F (SYNONYM), PER_ASSIGNMENT_STATUS_TYPES (SYNONYM), PER_ASSIGNMENT_STATUS_TYPES_TL (SYNONYM), and PER_EVENTS (SYNONYM). The view text joins PER_EVENTS to PER_ALL_ASSIGNMENTS_F on ASSIGNMENT_ID, and further requires that the event's DATE_START fall between the assignment's effective start and end dates, ensuring only date-effective-valid assignment context is returned. PER_ASSIGNMENT_STATUS_TYPES and its translation table PER_ASSIGNMENT_STATUS_TYPES_TL supply the assignment status type identifier and the user-facing status value. HR_LOCATIONS provides location codes via an outer join on LOCATION_ID, while HR_LOOKUPS resolves the interview type through LOOKUP_TYPE = 'APL_INTERVIEW_TYPE'. The view is filtered to interview records only through the predicate EVENT.EVENT_OR_INTERVIEW = 'I'.

Key Columns

The view exposes identity and descriptive columns including EVENT_ID, BUSINESS_GROUP_ID, ROW_ID, ASSIGNMENT_ID, and LOCATION_ID. INTERVIEW_TYPE and LOCATION present decoded meanings rather than raw codes. For the search term "time_start," the relevant column is TIME_START, produced by converting EVENT.TIME_START with TO_DATE(EVENT.TIME_START, 'HH24:MI'), with a parallel TIME_END column following the same conversion. Scheduling context is provided by DATE_START and DATE_END. Contact information appears in CONTACT_TELEPHONE_NUMBER, INTERNAL_CONTACT_PERSON_ID, and EXTERNAL_CONTACT. Employee or applicant context is captured by EMP_OR_APL, while ORGANIZATION_RUN_BY_ID identifies the conducting organization. STATUS_AFTER_INTERVIEW is derived from STATUSTL.USER_STATUS, and ASSIGNMENT_STATUS_TYPE_ID is included as well. Audit and extensibility fields include REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, the ATTRIBUTE1 through ATTRIBUTE20 descriptive flexfield columns, and the standard WHO columns LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE.

Common Use Cases and Queries

A typical use is retrieving interview events for an assignment within a date range, illustrating the TIME_START conversion. For example:

• SELECT event_id, assignment_id, date_start, TO_CHAR(time_start,'HH24:MI') time_start, interview_type, location FROM per_events_v3 WHERE assignment_id = :p_assignment_id AND date_start BETWEEN :p_from AND :p_to;
• Joining to PER_ALL_PEOPLE_F through ASSIGNMENT_ID or PERSON_ID to obtain candidate names for interview scheduling reports.
• Filtering by interview_type or status_after_interview to build pipeline and outcome dashboards.
• Combining date_start with time_start to construct full appointment timestamps for notifications.

Because TIME_START is stored in the base table as a character string and converted on the fly, comparisons and sorting on that column should account for day boundaries and be combined with DATE_START where necessary. The outer join to HR_LOCATIONS means location may be null, so queries should handle that condition. Given its interface-support orientation, PER_EVENTS_V3 remains a convenient, denormalized access path for interview event reporting in both 12.1.1 and 12.2.2.