Results for “hrfv_def_benefit_contributions”

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

Overview

The HRFV_DEF_BENEFIT_CONTRIBUTIONS view is a business view template shipped in the APPS schema of Oracle E-Business Suite 12.1.1 and 12.2.2. It is registered under the PER (Human Resources) product family and is generated from Oracle's flexfield view framework, which produces predefined business views over selected base tables for use in Oracle Discoverer, Oracle Business Intelligence, and other reporting or integration layers. The view consolidates benefit plan contribution data with translated element names, benefit classification attributes, and business group identification, presenting a denormalized, read-only projection suitable for ad hoc querying and downstream reporting.

The view exposes a single record per benefit contribution definition, keyed by BENEFIT_CONTRIBUTION_ID. Because it is defined WITH READ ONLY, it cannot be used for DML operations and should be treated strictly as a query surface. Its principal purpose is to render human-readable benefit names (the BENEFIT_NAME column, sourced from the translated element types table) alongside contribution formulas, coverage types, and classification flags, thereby removing the need to join the underlying transactional tables manually.

Underlying Base Objects

The documented base objects referenced by the view are:

• BEN_BENEFIT_CONTRIBUTIONS_F (SYNONYM) — the primary source for contribution amounts, effective dates, coverage type, and keys.
• BEN_BENEFIT_CLASSIFICATIONS (SYNONYM) — supplies the benefit classification name, COBRA flag, and dependents allowed flag.
• PAY_ELEMENT_TYPES_F (SYNONYM) — provides the element type definition and benefit classification linkage.
• PAY_ELEMENT_TYPES_F_TL (SYNONYM) — supplies the translated element (benefit) name and description.
• HR_ALL_ORGANIZATION_UNITS_TL (SYNONYM) — resolves the business group name in the user's language.
• HR_BIS (PACKAGE) — used for BIS_DECODE_LOOKUP calls that translate lookup codes such as coverage type and yes/no flags into display values.
• HR_DISCOVERER (PACKAGE) — used for CHECK_END_DATE to mask or adjust effective end dates for reporting.

The view applies NVL(HR_BIS.GET_SEC_PROFILE_BG_ID, ...) against BUSINESS_GROUP_ID so that results are filtered to the security profile's business group when one is set, and otherwise returns all business groups. Language filtering uses USERENV('LANG') on both translated tables so that only the current session language rows are returned.

Key Columns

• BUSINESS_GROUP_NAME — translated organization unit name identifying the business group.
• BENEFIT_NAME — translated element name for the benefit, the column most commonly used to identify a plan.
• BENEFIT_CLASSIFICATION_NAME — classification (for example medical, dental, life) assigned to the benefit.
• DESCRIPTION — translated description of the element type.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — validity window of the contribution record; end date is passed through CHECK_END_DATE.
• COVERAGE_TYPE — decoded from the US_BENEFIT_COVERAGE lookup (for example employee only, family).
• EMPLOYEE_CONTRIBUTION / EMPLOYER_CONTRIBUTION — numeric contribution amounts.
• TOTAL_CONTRIBUTION — computed sum of the employee and employer amounts.
• COBRA_ELIGIBLE, DEPENDENTS_COVERED_FLAG — decoded YES_NO flags.
• BENEFIT_CONTRIBUTION_ID, BUSINESS_GROUP_ID, ELEMENT_TYPE_ID, FORMULA_ID — surrogate and foreign keys supporting joins to underlying entities.

Common Use Cases and Queries

Typical uses include listing all benefits and their contribution rates for a business group, isolating COBRA-eligible plans, or comparing employee versus employer cost. A representative query is:

SELECT benefit_name, benefit_classification_name, coverage_type, employee_contribution, employer_contribution, total_contribution FROM apps.hrfv_def_benefit_contributions WHERE business_group_id = :p_bg_id AND SYSDATE BETWEEN effective_start_date AND NVL(effective_end_date, SYSDATE);

Because the view honors the security profile business group and current session language, results adapt automatically to the reporting user's context, making it appropriate for embedded Discoverer workbooks and custom reporting extracts.