Search Results ben_bnft_vrbl_rt_f




Overview
Explore in AI Chat

Overview

BEN_BNFT_VRBL_RT_F is a dated, effective-dated table in the BEN (Advanced Benefits) product of Oracle E-Business Suite, holding the variable rate definitions applied to a benefit. The table is owned by the BEN schema and is documented as VALID in both ETRM 12.1.1 and 12.2.2 references. Its purpose is to store the configuration of variable rates — rates whose value is not a fixed amount but is calculated dynamically according to an assigned variable rate profile and coverage amount calculation method.

The table carries the standard EBS date-tracked structure: the primary key is BEN_BNFT_VRBL_RT_F_PK, defined over (BNFT_VRBL_RT_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE). Every row is therefore versioned across effective periods, and queries must constrain on the effective dates to retrieve the correct version.

The metadata classifies this object as a standalone table under the heuristic Data Vault classification, with no documented foreign-key dependencies. As a modeling suggestion, this treatment would place BEN_BNFT_VRBL_RT_F as a satellite-like structure keyed on the variable rate identifier and effective dating, rather than as a pure hub or link. In practice the table behaves as a configuration master for variable rates, with the many BVR_ATTRIBUTE1 through BVR_ATTRIBUTE30 columns functioning as an open descriptive flexfield for customer-specific rate attributes.

Key Information Stored

The 44 documented columns are dominated by the primary key, the flexfield segment set, and standard WHO/audit columns. The most significant columns are:

  • BNFT_VRBL_RT_ID — surrogate identifier for the variable rate; the leading column of the primary key and the value referenced by dependent benefit definitions.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the remaining primary key columns, defining the effective period of each rate version.
  • VRBL_RT_PRFL_ID — identifies the variable rate profile that supplies the calculation logic for this rate.
  • CVG_AMT_CALC_MTHD_ID — the coverage amount calculation method associated with the rate.
  • BUSINESS_GROUP_ID — the business group that owns the configuration row, enabling multi-tenant separation.
  • ORDR_NUM — ordering value used to sequence rate rows in presentation.
  • BVR_ATTRIBUTE_CATEGORY plus BVR_ATTRIBUTE1 through BVR_ATTRIBUTE30 — descriptive flexfield context and segments.
  • OBJECT_VERSION_NUMBER — optimistic locking column used to detect concurrent updates.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard audit columns.

The unique index BEN_BNFT_VRBL_RT_F_PK is the business-key candidate, combining the identifier with both effective dates.

Common Use Cases and Queries

Typical usage involves resolving the currently effective variable rate configuration for a benefit, or extracting flexfield segments for reporting. A representative query restricts by effective dates:

  • SELECT bnft_vrbl_rt_id, vrbl_rt_prfl_id, cvg_amt_calc_mthd_id FROM ben.ben_bnft_vrbl_rt_f WHERE bnft_vrbl_rt_id = :p_id AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;
  • Flexfield extraction for configuration audits: SELECT bnft_vrbl_rt_id, bvr_attribute_category, bvr_attribute1, bvr_attribute2 FROM ben.ben_bnft_vrbl_rt_f WHERE business_group_id = :p_bg_id;
  • Version history reporting by ordering on effective_start_date for a given rate identifier.

Common scenarios include verifying which calculation method is attached to a variable rate before a payroll or benefits cycle, and generating configuration comparisons between environments during 12.1.1 to 12.2.2 upgrades.

Related Objects

Because the documented Data Vault classification is standalone with no mined foreign keys, the following related objects are inferred from the rate profile and calculation method references and from standard BEN benefit-rate dependencies. Join columns are noted where the identifier naming supports them.

Cross-reference on BNFT_VRBL_RT_ID and effective dates whenever joining to these objects to preserve date-tracked integrity.