Results for “drvbl_fctr_apls_meaning”

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

Overview

BEN_VRBL_RT_RL_D is an APPS-owned database view within the Oracle Advanced Benefits (BEN) module. It is a denormalized, presentation-oriented view built over the BEN_VRBL_RT_RL_F entity and its associated lookups, formulas, and activity base rates. The "_D" naming convention in Oracle EBS typically indicates a descriptive or denormalized view that joins a base (or "_F") table to HR_LOOKUPS and other reference objects to translate coded columns into user-readable meanings. In this case the object is documented as "Retrofitted," meaning it was created or regenerated as part of ETRM retrofitting to ensure the metadata and dependency definitions remain compliant with the documented schema.

Functionally, the view exposes configuration rows that govern how variable rate calculations are performed within Benefits. Each row describes a variable rate rule, including the rate treatment, the driving factor to which it applies, an application order, the formula that computes it, and the activity base rate used as input. Its role is primarily read-only reporting and integration — it provides a stable, human-readable projection of variable-rate rule setup that report writers, extracts, and downstream interfaces can query without re-implementing the lookup joins themselves.

Underlying Base Objects

The view is defined over several documented base objects. The primary driving object is BEN_VRBL_RT_RL_F (referenced through a synonym), the base table holding variable rate rule definitions. Supporting objects include:

• BEN_VRBL_RT_RL_F — the base variable rate rule table supplying VRBL_RT_RL_ID, effective dates, order of application, and the foreign keys to treatment, factor, formula, and activity base rate.
• HR_LOOKUPS — joined twice to decode RT_TRTMT_CD against lookup type 'BEN_RT_TRTMT' (RT_TRTMT.MEANING) and DRVBL_FCTR_APLS_FLAG against lookup type 'YES_NO' (DRVBL_FCTR_APLS.MEANING). This explains the user search term ben_rt_trtmt.
• FF_FORMULAS_F — supplies FORMULA_NAME for the formula used to compute the variable rate.
• BEN_ACTY_BASE_RT_F — supplies ACTY_BASE_RT_NAME, the activity base rate that underpins the calculation.
• FND_USER — provides the identity of the last user to update the row.
• HR_API — the HR package referenced in the documented dependency chain, used for date-tracked and security-related access logic.

All joins are outer joins (the "(+)" operator), so a rule row is returned even if its lookup, formula, activity base rate, or user reference is missing, which is important for auditing incomplete setup.

Key Columns

• ROW_ID — the ROWID of the underlying BEN_VRBL_RT_RL_F row; stable physical address used for direct-row access.
• VRBL_RT_RL_ID — primary key of the variable rate rule.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-tracked validity window for the rule.
• DRVBL_FCTR_APLS_MEANING — decoded 'YES/NO' meaning indicating whether the driving factor applies.
• RT_TRTMT_MEANING — decoded meaning of the rate treatment from lookup type BEN_RT_TRTMT.
• ORDR_TO_APLY_NUM — sequence in which the rule is applied relative to others.
• FORMULA_NAME — the formula that computes the variable rate.
• ACTY_BASE_RT_NAME — the activity base rate feeding the calculation.
• LAST_UPDATE_DATE / LAST_UPDATED_BY — audit columns; the latter is exposed as a user ID.

Common Use Cases and Queries

The view is most often used to audit or report variable rate rule configuration, to verify that lookups decode correctly, and to feed integration extracts. A typical query retrieves all active rules with decoded meanings:

• Configuration audit: SELECT vrbl_rt_rl_id, rt_trtmt_meaning, drvbl_fctr_apls_meaning, ordr_to_aply_num, formula_name, acty_base_rt_name FROM ben_vrbl_rt_rl_d WHERE TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date ORDER BY ordr_to_aply_num;
• Reconciliation: SELECT vrbl_rt_rl_id, rt_trtmt_meaning FROM ben_vrbl_rt_rl_d WHERE rt_trtmt_meaning IS NULL; to find rules whose rate treatment lookup is missing or invalid.
• Change tracking: filter on last_update_date >= :since_date and join LAST_UPDATED_BY to FND_USER for the user name.

Because the view hides the underlying lookup joins, it is well suited to ad hoc reporting and to interfaces that require the decoded rate treatment (ben_rt_trtmt) text rather than the raw lookup code. Queries should be date-filtered to honor the effective-dating of the base table.