Results for “per_events_lov_v”

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

Overview

PER_EVENTS_LOV_V is an Oracle E-Business Suite view owned by the APPS schema within the PER (Human Resources) product module. It is classified as a "Used to support user interface" object, meaning it is designed to populate a List of Values (LOV) region in a forms-based or OAF user interface rather than to serve as a reporting or integration interface. In the Oracle EBS 12.1.1 and 12.2.2 releases, the view is documented as VALID in the ETRM repository.

The view returns interview events associated with assignments, presenting a formatted date, a lookup meaning for the event type, and a location code. Because the review date is rendered through the FND_PROFILE package, the output is session-dependent: the date appears in the format defined by the ICX_DATE_FORMAT_MASK profile option for the current user. This is the reason a search for icx_date_format_mask resolves to this object.

Underlying Base Objects

The view text joins three objects and relies on the FND_PROFILE package for formatting:

• PER_EVENTS (SYNONYM) — the driving table, aliased EVT, supplying ASSIGNMENT_ID, EVENT_ID, the event date, type, and location identifier. The predicate EVENT_OR_INTERVIEW = 'I' restricts rows to interview events.
• HR_LOCATIONS (VIEW) — aliased LOC, providing LOCATION_CODE. The join is outer (LOCATION_ID(+) = LOC.LOCATION_ID).
• HR_LOOKUPS (VIEW) — aliased HLU, supplying MEANING for the interview type. The join is outer and constrained to LOOKUP_TYPE = 'EMP_INTERVIEW_TYPE'.
• FND_PROFILE (PACKAGE) — invoked as FND_PROFILE.VALUE('ICX_DATE_FORMAT_MASK') to convert DATE_START into a display string.
• HR_API and HR_GENERAL (PACKAGE) — documented dependencies used by the HR location and lookup views.

Because the two joins to HR_LOCATIONS and HR_LOOKUPS are outer joins, an interview event still appears when its type is not defined in EMP_INTERVIEW_TYPE or when no location is recorded; MEANING and LOCATION_CODE then return NULL.

Key Columns

• ASSIGNMENT_ID — identifier of the assignment to which the interview event belongs; the primary linkage to the employee or applicant record.
• EVENT_ID — unique identifier of the row in PER_EVENTS; used as the LOV return value.
• REVIEW_DATE — the column alias applied to the TO_CHAR expression over EVT.DATE_START, rendered using the ICX_DATE_FORMAT_MASK date format mask for the current session.
• EVENT_TYPE — the decoded MEANING of the event type lookup (EMP_INTERVIEW_TYPE) rather than the raw lookup code.
• EVENT_LOCATION — the LOCATION_CODE from HR_LOCATIONS, or NULL when no location is associated.

Common Use Cases and Queries

The view supports interview-selection LOVs in HR forms. Practical queries constrain by assignment and rely on the pre-formatted date column.

Retrieve all interview events for a given assignment:

• SELECT EVENT_ID, REVIEW_DATE, EVENT_TYPE, EVENT_LOCATION FROM APPS.PER_EVENTS_LOV_V WHERE ASSIGNMENT_ID = :assignment_id;

Search by formatted date range, noting that the filter must be applied to the underlying date and not to the string column:

• SELECT EVENT_ID, REVIEW_DATE, EVENT_TYPE FROM APPS.PER_EVENTS_LOV_V WHERE ASSIGNMENT_ID = :assignment_id AND EVENT_TYPE = :meaning;

Validate that the session date format is being applied as expected:

• SELECT REVIEW_DATE FROM APPS.PER_EVENTS_LOV_V WHERE ROWNUM <= 10;

When the mask yields an unexpected pattern, confirm the ICX_DATE_FORMAT_MASK value at the site, application, responsibility, or user level, since FND_PROFILE.VALUE resolves the effective setting for the connected session. Direct SQL access to this view outside the supported interface should be treated with caution, as it is documented as a user-interface support object.