Results for “ben_actl_prem_vrbl_rt_rl_x”

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

Overview

BEN_ACTL_PREM_VRBL_RT_RL_X is a public synonym-backed view in the APPS schema belonging to the BEN (Advanced Benefits) product family within Oracle E-Business Suite. It is documented as a "Retrofitted" object, indicating that it was introduced or re-created to maintain backward compatibility with earlier releases of the benefits data model. The view exposes the actual premium variable rate rule records used by Oracle Advanced Benefits when calculating the cost of benefit plans whose premiums are driven by a variable rate formula rather than a fixed amount. In this context, "actual premium" refers to the derived cost of coverage for a participant, and "variable rate rule" refers to the ordered set of formulas that determine that cost based on configurable criteria. The view presents the current effective rows of this rule configuration and is therefore suited for point-in-time reporting, extraction to downstream systems, and integration scenarios where benefit rate configuration must be reconciled across environments or releases.

Underlying Base Objects

The view is defined over a single documented base object: BEN_ACTL_PREM_VRBL_RT_RL_F, a synonym that resolves to the underlying AD_OBJECTS-style key flexfield table holding the effective-dated rate rule definitions. The definition applies a date filter, selecting rows where the system date falls between the EFFECTIVE_START_DATE and EFFECTIVE_END_DATE of the base record. This means the view returns only the currently active version of each rule, suppressing historical and future-dated rows that remain in the base table for audit and dating purposes. Because the view is read-only and driven entirely by that filter and a direct column projection, no joins or aggregations are performed; each row in the view corresponds one-to-one with an active row in the underlying table. The "Retrofitted" designation in the ETRM metadata signals that the view preserves a legacy interface, so existing reports and customizations referencing it continue to function in 12.1.1 and 12.2.2 without modification.

Key Columns

The view exposes the primary key column ACTL_PREM_VRBL_RT_RL_ID along with the surrogate date range columns EFFECTIVE_START_DATE and EFFECTIVE_END_DATE. ACTL_PREM_ID links each rule to the actual premium definition it qualifies, while FORMULA_ID identifies the formula executed to derive the variable rate. ORDR_TO_APLY_NUM establishes the sequence in which multiple rules are evaluated, and RT_TRTMT_CD indicates the rate treatment or rounding behavior applied to the result. BUSINESS_GROUP_ID scopes the configuration to a specific business group. The flexible attribute columns AVA_ATTRIBUTE_CATEGORY through AVA_ATTRIBUTE30 provide the descriptive flexfield extension segment used to capture customer-specific configuration; AVA_ATTRIBUTE1 is the first such segment and is frequently used to store an internal reference or classification for the rate rule. Standard audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER) complete the projection and support change tracking and optimistic locking.

Common Use Cases and Queries

Typical uses include verifying that variable rate rules are correctly sequenced within a plan, auditing formula assignments after a configuration migration, and extracting attribute data to an external rate engine. A representative query filtering on the first descriptive attribute is shown below:

• SELECT ACTL_PREM_VRBL_RT_RL_ID, ACTL_PREM_ID, FORMULA_ID, ORDR_TO_APLY_NUM, RT_TRTMT_CD, AVA_ATTRIBUTE1 FROM BEN_ACTL_PREM_VRBL_RT_RL_X WHERE AVA_ATTRIBUTE1 = :p_attribute;
• SELECT ACTL_PREM_ID, COUNT(*) FROM BEN_ACTL_PREM_VRBL_RT_RL_X GROUP BY ACTL_PREM_ID ORDER BY 1;
• SELECT r.ACTL_PREM_VRBL_RT_RL_ID, r.FORMULA_ID, r.ORDR_TO_APLY_NUM FROM BEN_ACTL_PREM_VRBL_RT_RL_X r WHERE r.BUSINESS_GROUP_ID = :p_bg_id ORDER BY r.ACTL_PREM_ID, r.ORDR_TO_APLY_NUM;

Because the view filters on TRUNC(SYSDATE) against the effective dates, queries automatically return the configuration valid on the date of execution, making it suitable for as-of reporting without additional date predicates.