Results for “internal_contact_person_id”

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

Overview

PER_EVENTS_V is an APPS-owned view in the Oracle E-Business Suite PER (Human Resources) product module, holding VALID status in both 12.1.1 and 12.2.2. It is documented as being "used to support user interface," meaning it functions as a presentation-layer object rather than a transactional base table. The view surfaces interview records stored in PER_EVENTS, enriched with lookup meanings and location codes, so that forms, list-of-values, and reporting queries can retrieve human-readable interview data without directly joining the underlying lookup and location tables.

The view is particularly relevant to the search term "external_contact" because it explicitly exposes the EXTERNAL_CONTACT column from PER_EVENTS, allowing users to identify interview events involving non-employee participants without querying the base table directly.

Underlying Base Objects

The view definition joins three primary sources. PER_EVENTS (referenced via a synonym in the documented metadata) supplies the core columns of the view. HR_LOOKUPS supplies the MEANING column, resolved through a join on PE.TYPE = HR.LOOKUP_CODE with LOOKUP_TYPE constrained to 'EMP_INTERVIEW_TYPE'. HR_LOCATIONS supplies LOCATION_CODE through an outer join (PE.LOCATION_ID = HL.LOCATION_ID (+)), meaning interviews are still returned even when no matching location exists.

The documented base objects also include HR_API and HR_GENERAL packages, which are standard PER security and utility packages referenced by dependent objects. The metadata lists HR_LOCATIONS as a VIEW, HR_LOOKUPS as a VIEW, and PER_EVENTS as a SYNONYM, reflecting the layered dictionary structure typical of EBS.

Crucially, the WHERE clause restricts results to PE.EVENT_OR_INTERVIEW = 'I', so the view returns interview records only, excluding other event types in PER_EVENTS.

Key Columns

• EVENT_ID — Primary identifier for the interview event, inherited from PER_EVENTS.
• EXTERNAL_CONTACT — The external contact associated with the interview; the column most directly tied to the user's search.
• INTERNAL_CONTACT_PERSON_ID — Identifier of the internal employee contact for the interview.
• CONTACT_TELEPHONE_NUMBER, DATE_START, DATE_END, TIME_START, TIME_END — Scheduling and contact details.
• MEANING — Decoded lookup meaning for the interview type, sourced from HR_LOOKUPS.
• LOCATION_CODE, LOCATION_ID — Location reference, with LOCATION_CODE joined via HR_LOCATIONS.
• ORGANIZATION_RUN_BY_ID, ASSIGNMENT_ID, BUSINESS_GROUP_ID — Organizational and assignment context.
• TYPE — Lookup code value restricted by lookup type 'EMP_INTERVIEW_TYPE'.
• ROW_ID — ROWID of the base PER_EVENTS row, enabling direct reference.
• ATTRIBUTE1–20 and WHO columns — Descriptive flexfield segments and standard audit columns.

Common Use Cases and Queries

Typical uses include interview scheduling reports, HR dashboards listing external interview contacts, and integration extracts feeding third-party recruitment or calendar systems. The view's READ-ONLY nature and absence of DML make it safe for reporting joins.

Sample query for external interview contacts by location:

• SELECT v.event_id, v.meaning, v.external_contact, v.contact_telephone_number, v.location_code, v.date_start, v.time_start FROM apps.per_events_v v WHERE v.external_contact IS NOT NULL AND v.date_start >= SYSDATE - 30 ORDER BY v.date_start DESC;
• SELECT v.meaning, COUNT(*) FROM apps.per_events_v v GROUP BY v.meaning;
• SELECT v.event_id, v.external_contact FROM apps.per_events_v v WHERE v.location_code = 'HQ';

Because the view filters to interview rows and resolves lookup meanings automatically, queries against it are simpler and more readable than constructing equivalent joins across PER_EVENTS, HR_LOOKUPS, and HR_LOCATIONS.