Search Results ben_vrbl_rt_prfl




Overview

BEN_VRBL_RT_PRFL is an Oracle E-Business Suite Advanced Benefits (BEN) view owned by the APPS schema. It presents variable rate profile records, which are the configuration objects that drive how Oracle Advanced Benefits calculates variable earnings, imputed income, and other rate-based benefit values. A variable rate profile defines the treatment, rounding rules, limits, and eligibility factors applied when the benefits engine derives an amount for a participant, dependent, or coverage. The view carries a STATUS of VALID and is exposed in both EBS 12.1.1 and 12.2.2, providing a stable, read-only projection of the underlying rate profile table for reporting, integration, and diagnostic purposes.

Because it is a view rather than a base table, BEN_VRBL_RT_PRFL is intended for querying rather than direct DML. Report writers and integration developers use it to extract the parameters that determine benefit rate processing without needing to understand the denormalized storage of the underlying table.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the view as being defined over two referenced objects:

  • BEN_VRBL_RT_PRFL_F (accessed via a synonym) — the base table that physically stores variable rate profile definitions. The "_F" suffix follows the standard EBS date-tracked table convention, meaning it holds effective-dated (date-tracked) rows keyed by EFFECTIVE_START_DATE and EFFECTIVE_END_DATE.
  • FND_SESSIONS (accessed via a synonym) — the Oracle Application Object Library sessions table, typically used for session or language context resolution.

The view text selects directly from BEN_VRBL_RT_PRFL_F (aliased VPF), projecting every significant column of the base table and adding ROWID as ROW_ID for row identification. There is no join or aggregation in the view text itself; the projection is essentially the date-tracked base table exposed under the BEN_VRBL_RT_PRFL name. FND_SESSIONS supports the runtime context in which the view is resolved.

Key Columns

The view exposes the complete set of rate profile attributes. The most significant include:

Common Use Cases and Queries

Typical usage includes auditing rate profile configuration, reconciling calculation setup before a payroll or benefits run, and feeding downstream reporting or interfaces. The date-tracked nature means queries should normally filter to the effective date of interest.

A representative query retrieving currently effective profiles for a plan:

  • SELECT vrbl_rt_prfl_id, pl_id, name, rt_typ_cd, vrbl_rt_trtmt_cd, val, val_calc_rl, effective_start_date, effective_end_date FROM apps.ben_vrbl_rt_prfl WHERE TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date AND pl_id = :p_plan_id ORDER BY name;

To inspect rounding and limit behavior for a specific profile:

  • SELECT vrbl_rt_prfl_id, rndg_cd, rndg_rl, lwr_lmt_val, lwr_lmt_calc_rl, upr_lmt_val, upr_lmt_calc_rl FROM apps.ben_vrbl_rt_prfl WHERE vrbl_rt_prfl_id = :p_profile_id AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;

To review which rate input factors are enabled, query the RT_*_FLAG columns for the profile of interest. Because the view is read-only and reflects the date-tracked base table, all queries should constrain on effective dates and, where relevant, on BUSINESS_GROUP_ID to respect multi-organization data segmentation.