Search Results ben_lvg_rsn_rt_d




Overview
Explore in AI Chat

Overview

BEN_LVG_RSN_RT_D is a VALID database view owned by the APPS schema within the BEN (Advanced Benefits) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a denormalized, reporting-friendly representation of leave reason rate records. The physical data is stored in the BEN_LVG_RSN_RT_F base table (a date-tracked/date-effective table), while the view enriches each row with descriptive attributes pulled from lookup values, variable rate profiles, and user information. Rather than exposing raw foreign key identifiers alone, BEN_LVG_RSN_RT_D resolves those identifiers into human-readable names, which makes it suitable for custom reports, extracts, and integrations that must present leave-of-absence reason rate configuration in an understandable form. Because it is a view rather than a table, it carries no storage of its own and always reflects the current state of its underlying base objects at query time.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over the following referenced objects:

  • BEN_LVG_RSN_RT_F (SYNONYM) — the primary driving table holding leave reason rate definitions, including effective dates, order number, and the exclusion flag. It is joined as the alias LRN.
  • BEN_VRBL_RT_PRFL_F (SYNONYM) — the variable rate profile table, joined on VRBL_RT_PRFL_ID to supply the profile name. Joined as alias VPR.
  • HR_LOOKUPS (VIEW) — the lookups view, used to translate the LVG_RSN_CD lookup code into the descriptive meaning. The join restricts LOOKUP_TYPE to 'LEAV_REAS'.
  • FND_USER_VIEW (VIEW) — the application user view, joined on USER_ID to resolve the last-updated-by identifier into a user name. The join is outer (+), so rows without a matching user are still returned.
  • HR_API (PACKAGE) — a referenced package associated with the base benefit objects, typically used by the underlying date-tracked table logic.

The join condition to the variable rate profile is an inner join, while the user join is an outer join. Consequently, a leave reason rate row will not appear unless a matching variable rate profile exists, but it will appear even if no matching FND user is found.

Key Columns

The view exposes the following columns:

  • ROW_ID — the ROWID of the underlying BEN_LVG_RSN_RT_F row, useful for uniquely identifying a physical record.
  • LVG_RSN_RT_ID — the primary key of the leave reason rate definition.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-effective range during which the row is valid.
  • EXCLD_FLAG — indicates whether the record is excluded from processing.
  • VRBL_RT_PRFL_NAME — the variable rate profile name resolved from BEN_VRBL_RT_PRFL_F.
  • LVG_RSN_CD / LVG_RSN — the leave reason lookup code and its corresponding meaning from HR_LOOKUPS ('LEAV_REAS').
  • ORDR_NUM — the display or processing order number.
  • LAST_UPDATE_DATE — the timestamp of the last modification.
  • LAST_UPDATED_BY — the user identifier resolved through FND_USER_VIEW to a user name.

Common Use Cases and Queries

Typical uses include validation of leave reason rate configuration, auditing changes by user, and reporting on effective-date ranges. A representative query follows:

  • SELECT LVG_RSN_RT_ID, LVG_RSN, VRBL_RT_PRFL_NAME, EXCLD_FLAG, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE FROM BEN_LVG_RSN_RT_D WHERE SYSDATE BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE;
  • SELECT LVG_RSN, ORDR_NUM, LAST_UPDATE_DATE, LAST_UPDATED_BY FROM BEN_LVG_RSN_RT_D ORDER BY ORDR_NUM;

Because it is a view, all queries inherit the base tables' effective-dating and security characteristics; report authors should apply appropriate date filters to obtain only currently active configurations.