Search Results ben_lvg_rsn_rt




Overview
Explore in AI Chat

Overview

BEN_LVG_RSN_RT is a reporting view in the APPS schema belonging to the Oracle Advanced Benefits (BEN) module. Its name follows the standard EBS convention in which the _RT suffix identifies a row-level runtime (or "row type") view that resolves the current effective-dated version of a base table record. In this case the view surfaces leave-of-absence reason records, as reflected by the LVG_RSN token (Leave Reason). The view is marked VALID in the ETRM repository and is documented for both Oracle EBS 12.1.1 and 12.2.2.

Unlike a physical table, this view presents no data of its own. Its role is to expose a filtered, session-aware slice of the leave reason data so that forms, concurrent programs, and integration queries receive only records that are effective as of the current application session date. This date-sensitive filtering is central to the behaviour of Advanced Benefits, where eligibility, rates, and reason codes are all maintained with effective start and end dates.

Underlying Base Objects

The view is defined exclusively over one base object, BEN_LVG_RSN_RT_F (aliased internally as LRN), with a second reference to the FND_SESSIONS synonym used to resolve the effective date. No joins to other business tables are performed; the view is a straightforward projection with an effective-date predicate.

  • BEN_LVG_RSN_RT_F — the "_F" table holds the full effective-dated history of leave reason rows. All descriptive and descriptive-flex columns originate here.
  • FND_SESSIONS — the Oracle Applications session table, queried for EFFECTIVE_DATE using USERENV('SESSIONID'). This supplies the "as of" date that drives the view's temporal filter.

The defining predicate is:

LRN.EFFECTIVE_START_DATE <= (session effective date) AND LRN.EFFECTIVE_END_DATE >= (session effective date)

Because the comparison is made against the live session effective date rather than SYSDATE, the view automatically honours any date a user has set in the application session (for example, a past or future effective date entered on the navigator), which is the expected behaviour for effective-dated HRMS and Benefits objects.

Key Columns

Common Use Cases and Queries

The view is typically used to report or validate leave reason configuration for a given business group as of a chosen effective date. Because the effective date is taken from FND_SESSIONS, the value returned depends on the session in which the query executes; standalone SQL*Plus sessions may require setting the session context first.

A representative query returning the currently effective leave reasons for a business group is:

  1. SELECT lvg_rsn_rt_id, lvg_rsn_cd, vrbl_rt_prfl_id, ordr_num, effective_start_date, effective_end_date
  2. FROM apps.ben_lvg_rsn_rt
  3. WHERE business_group_id = :p_business_group_id
  4. ORDER BY ordr_num;

To review the complete history of a single leave reason, developers query the base table BEN_LVG_RSN_RT_F directly, since the view intentionally suppresses non-current rows. The view is also useful during data migration or interface validation, where an integration must confirm that a leave reason code is active before loading dependent benefit eligibility or rate records.

In summary, BEN_LVG_RSN_RT is a read-only, session-aware runtime view over the leave reason rate table. It is safe for reporting and integration reads but must not be used for DML; updates belong to the underlying BEN_LVG_RSN_RT_F table through the standard Benefits APIs.