Results for “hrilv_seprsn_x”

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

Overview

The HRILV_SEPRSN_X view is a Human Resources Intelligence (HRI) reporting object shipped within Oracle E-Business Suite, documented in the ETRM reference for both 12.1.1 and 12.2.2. It is a "list of values" (LOV) presentation view whose function is to expose the set of currently enabled separation, or leave, reasons that the application may present to a user or consume in a reporting query. Its membership is governed entirely by reference data rather than by transactional employee records: the rows are sourced from the HR_LOOKUPS lookup table filtered to a single lookup type. Although the object carries a "SEPRSN" naming element, the view text targets the leave reason lookup type (LEAV_REAS), so it is commonly used wherever a valid, date-effective absence or separation reason list is required.

The documented metadata records the view as "Not implemented in this database," and no base objects are documented in ETRM. The function and structure below are derived from the view text reproduced in the source documentation.

Underlying Base Objects

The view is defined over a single documented base table, HR_LOOKUPS. No other base objects are documented in the ETRM metadata. HR_LOOKUPS stores all Oracle HRMS lookup codes by lookup type; HRILV_SEPRSN_X restricts its SELECT to the rows where LOOKUP_TYPE equals 'LEAV_REAS'.

The definition is a UNION ALL of two branches. The first branch returns every enabled HR_LOOKUPS row of that type whose active date range includes the current system date. The second branch fabricates a single synthetic placeholder row using the literal identifier '__NULL__' selected from DUAL, so that a blank or "no selection" entry is always available to the LOV. Both branches carry the standard HRIVIEW.LDT header, indicating the object was generated from the HRMS view template. HR_GENERAL supplies the unbounded date constants START_OF_TIME and END_OF_TIME used to pad the effective-dating columns.

Key Columns

• ID — The code returned from the lookup row (HRL.LOOKUP_CODE). It is the internal value passed back by the LOV; the synthetic row supplies the literal '__NULL__'.
• VALUE — The user-facing description (HRL.MEANING). This is the text displayed in the LOV list; the synthetic row returns a single space.
• DATE_FROM — The effective start of the lookup. It is HRL.START_DATE_ACTIVE, defaulted to START_OF_TIME when the lookup is unbounded.
• DATE_TO — The effective end of the lookup. It is HRL.END_DATE_ACTIVE, defaulted to END_OF_TIME when open-ended.
• VALID_CODE — The enabled flag (HRL.ENABLED_FLAG), returned as 'Y' for every qualifying row including the placeholder. Combined with the date predicate, it guarantees that only currently valid values appear.

Common Use Cases and Queries

The view is typically consumed to populate a concurrent program parameter LOV, a forms item LOV, or a report filter so that users select only active leave or separation reasons. Filtering is already applied by the view, so calling code does not need to repeat the enabled-flag or date logic. A simple retrieval follows:

• SELECT id, value FROM hriv_seprsn_x ORDER BY value;
• SELECT id, value FROM hriv_seprsn_x WHERE id <> '__NULL__' ORDER BY value; — excludes the synthetic empty entry when a mandatory selection is required.
• SELECT id, value, date_from, date_to FROM hriv_seprsn_x WHERE TRUNC(SYSDATE) BETWEEN date_from AND date_to; — demonstrates the effective-date window already enforced internally.

Because the view is read-only (WITH READ ONLY), it should be used strictly for query and LOV purposes. It is not intended as a base for DML, and any reporting requirement that must include disabled or future-dated lookup values should query HR_LOOKUPS directly rather than this view.