Search Results ben_vrbl_rt_elig_prfl




Overview
Explore in AI Chat

Overview

BEN_VRBL_RT_ELIG_PRFL is a read-only view owned by the APPS schema in Oracle Advanced Benefits (BEN). It exposes the effective-dated relationship between a variable rate profile and an eligibility profile, answering the functional question of which eligibility profile governs a given variable rate profile during a given period. The view is the runtime-facing counterpart of the underlying date-tracked table, applying a session-based date filter so that only rows effective as of the current FND session date are visible to the calling session.

In Oracle EBS 12.1.1 and 12.2.2, the view is widely used by the benefits calculation and eligibility engines, by concurrent processes that evaluate variable rate eligibility, and by reporting and integration layers that need a point-in-time perspective on the variable rate and eligibility profile association without writing their own date-bracketing predicates. Because it is a view rather than a table, no DML is permitted against it; it should be treated strictly as a query surface.

Underlying Base Objects

The view is defined over two documented base objects:

  • BEN_VRBL_RT_ELIG_PRFL_F (accessed through a synonym) — the date-tracked ( _F ) table that stores the effective-dated rows of the variable rate / eligibility profile relationship.
  • FND_SESSIONS (accessed through a synonym) — the Applications session table, used here to resolve the effective date for the current session.

The defining query joins the two objects and filters on the session effective date:

VEP.EFFECTIVE_START_DATE <= (SELECT SS.EFFECTIVE_DATE FROM FND_SESSIONS SS WHERE SS.SESSION_ID = USERENV('SESSIONID')) and, symmetrically, VEP.EFFECTIVE_END_DATE >= (SELECT SS.EFFECTIVE_DATE ...). This pattern is standard for BEN runtime views: it returns the single row valid as of the session's effective date, automatically handling date-tracked versions without requiring the caller to supply BETWEEN predicates. Since the join against FND_SESSIONS is driven by USERENV('SESSIONID'), the view must be queried from an initialized EBS session (an active Apps connection) for meaningful results.

Key Columns

Common Use Cases and Queries

Typical scenarios include: listing the eligibility profiles linked to a variable rate profile for the current session; auditing DFF context and segment values on the association; and joining to eligibility and variable rate profile views to build benefit configuration reports.

Example — all current associations for a business group:

SELECT ve.VRBL_RT_ELIG_PRFL_ID, ve.VRBL_RT_PRFL_ID, ve.ELIGY_PRFL_ID, ve.MNDTRY_FLAG, ve.EFFECTIVE_START_DATE, ve.EFFECTIVE_END_DATE FROM apps.ben_vrbl_rt_elig_prfl ve WHERE ve.business_group_id = :p_business_group_id ORDER BY ve.VRBL_RT_PRFL_ID;

Example — associations for a specific variable rate profile, joined to the eligibility profile:

SELECT ve.vrbl_rt_prfl_id, ve.eligy_prfl_id, ep.eligy_prfl_nm FROM apps.ben_vrbl_rt_elig_prfl ve, apps.ben_eligy_prfl ep WHERE ve.eligy_prfl_id = ep.eligy_prfl_id AND ve.vrbl_rt_prfl_id = :p_vrbl_rt_prfl_id;

Because the view performs its own effective-date filtering against FND_SESSIONS, callers should not add redundant EFFECTIVE_START_DATE/EFFECTIVE_END_DATE predicates when a current-session perspective is required; historical analysis should query the _F base table directly with explicit date ranges.