Results for “drvbl_fctr_apls_flag”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BEN_VRBL_RT_PRFL_RL_D is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the BEN — Advanced Benefits product. In ETRM 12.1.1 and 12.2.2 it is registered as a VALID view over the Advanced Benefits variable rate profile rule configuration. It presents one row per variable rate profile rule line, denormalized with the parent profile name, the formula name, and the user who last updated the record, so that integrators and report developers can resolve descriptive context without joining the underlying flexfield and formula tables themselves.

Its principal role is reporting and integration support: it exposes the driving-factor applicability indicator (DRVBL_FCTR_APLS_FLAG) — the attribute users most frequently search for — alongside the rule ordering sequence and formula binding, making it suitable for auditing how variable rates are calculated and applied within a benefit plan.

Underlying Base Objects

The view is defined over four referenced base objects, all resolved through APPS synonyms:

• BEN_VRBL_RT_PRFL_RL_F — the primary base table (alias VPR) holding the variable rate profile rule lines, including the rule ID, dates, ordering, formula reference, and the driving-factor flag.
• BEN_VRBL_RT_PRFL_F — the parent variable rate profile table (alias VAPRO), supplying the profile name joined on VRBL_RT_PRFL_ID.
• FF_FORMULAS_F — the Oracle Fast Formula repository (alias FFF), supplying FORMULA_NAME joined on FORMULA_ID.
• FND_USER — the application user table, joined with an outer join (+) on LAST_UPDATED_BY to return the updating user name.

All joins are effective-date aware only to the extent that the underlying _F tables carry EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, which the view projects directly.

Key Columns

• VRBL_RT_PRFL_RL_ID — primary key of the rule line; use for point lookups and joins back to the base table.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — date-tracked validity range of the rule line.
• VRBL_RT_PRFL_NAME — the parent variable rate profile name, sourced from BEN_VRBL_RT_PRFL_F.NAME.
• FORMULA_NAME — the Fast Formula that computes the rate, resolved from FF_FORMULAS_F.
• ORDR_NUM — the application order of the rule within the profile (documented as ORDR_TO_APLY_NUM in the view text), governing evaluation precedence.
• DRVBL_FCTR_APLS_FLAG — indicates whether a driving factor applies to the rule; central to rate-determination logic.
• LAST_UPDATE_DATE and LAST_UPDATED_BY — audit columns; the latter resolves to FND_USER.USER_NAME for the updating user.

Common Use Cases and Queries

Typical scenarios include auditing which rules carry a driving factor, reviewing formula bindings per profile, and validating rule ordering. A representative query is:

• List driving-factor rules for a profile:
  SELECT vrbl_rt_prfl_name, formula_name, ordr_num, effective_start_date, effective_end_date FROM apps.ben_vrbl_rt_prfl_rl_d WHERE drvbl_fctr_apls_flag = 'Y' ORDER BY vrbl_rt_prfl_name, ordr_num;
• Trace formula usage: filter by FORMULA_NAME to identify every profile rule referencing a given Fast Formula.
• As-of-date reporting: apply SYSDATE BETWEEN effective_start_date AND effective_end_date to return only currently effective rules.
• Change auditing: group by LAST_UPDATED_BY and LAST_UPDATE_DATE to review recent configuration changes.

Because the view is not date-tracked in its own right, callers should always constrain the effective dates when precise point-in-time results are required.