Search Results valid_code




Overview
Explore in AI Chat

Overview

HRI_CL_RSN_SAL_X_V is an Oracle E-Business Suite (EBS) view owned by the APPS schema and registered in the E-Tax/ETRM repository under product HRI (Human Resources Intelligence). It exposes the valid, enabled lookup values belonging to the lookup type PROPOSAL_REASON, together with each value's effective date range and a validity indicator. In release 12.1.1 and 12.2.2 the object is documented as VALID, and its purpose is to provide a stable, date-filtered presentation of proposal reason codes for consumption by Oracle HRMS Intelligence extract programs, Discoverer workbooks, and downstream reporting or integration layers.

Rather than exposing the raw HR_LOOKUPS rows, the view performs the common EBS "code translation" pattern: it maps the lookup code to an ID, the lookup meaning to a VALUE, derives effective start and end dates with infinities substituted for nulls, and returns an enabled flag as VALID_CODE. This makes the view suitable for building value sets, warehouse dimensions, or parameter lists where only currently active proposal reasons must be presented.

Underlying Base Objects

The documented base objects referenced by this view are:

  • HR_LOOKUPS (VIEW) — the primary source. The view selects rows where LOOKUP_TYPE = 'PROPOSAL_REASON' and ENABLED_FLAG = 'Y', and applies a TRUNC(SYSDATE) range check against the lookup's active dates.
  • HR_GENERAL (PACKAGE) — supplies the sentinel constants START_OF_TIME and END_OF_TIME, used to substitute for null START_DATE_ACTIVE and END_DATE_ACTIVE values so that the date range is always bounded.
  • HR_API (PACKAGE) — documented as a referenced base object, reflecting the standard HRMS lookup access conventions used across HR Intelligence objects.
  • DUAL (SYNONYM) — the second branch of the UNION ALL selects a single synthetic row from DUAL.

Structurally the view is a UNION ALL of two queries. The first returns enabled proposal reason lookups whose effective window includes the current date. The second appends a fixed pseudo-row with ID = 'NA_EDW', a null VALUE, and full open date bounds, providing a placeholder member for Extensible Data Warehouse (EDW) style dimensions. The view is defined WITH READ ONLY, so no DML is possible through it.

Key Columns

  • ID — the LOOKUP_CODE from HR_LOOKUPS for real rows, or the literal 'NA_EDW' for the synthetic row. Serves as the surrogate key when the view is used in a value set or dimension.
  • VALUE — the lookup MEANING, the user-facing description of the proposal reason; blank for the synthetic row.
  • DATE_FROM — NVL(START_DATE_ACTIVE, HR_GENERAL.START_OF_TIME), the effective start of the value.
  • DATE_TO — NVL(END_DATE_ACTIVE, HR_GENERAL.END_OF_TIME), the effective end of the value.
  • VALID_CODE — the ENABLED_FLAG; always 'Y' here because the query filters enabled rows and the synthetic row is hard-coded to 'Y'.

Common Use Cases and Queries

Typical uses include populating a report parameter or LOV with current proposal reasons, joining proposal records to a descriptive reason dimension, and seeding a warehouse dimension that requires a dummy NA_EDW member for referential completeness.

  • List all currently valid proposal reasons: SELECT id, value FROM apps.hri_cl_rsn_sal_x_v ORDER BY value;
  • Retrieve the description for a known reason: SELECT value FROM apps.hri_cl_rsn_sal_x_v WHERE id = :p_reason;
  • Resolve the date range for auditing: SELECT id, date_from, date_to, valid_code FROM apps.hri_cl_rsn_sal_x_v WHERE id <> 'NA_EDW';

Because the view is read-only and filters on TRUNC(SYSDATE), results change as lookup start and end dates pass; consumers should not cache the output where date sensitivity matters.