Results for “benbv_rptg_grp_v”

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

Overview

The BENBV_RPTG_GRP_V view is a business-facing, read-only reporting object within the Oracle Advanced Benefits (BEN) module of Oracle E-Business Suite. It is owned by the APPS schema and is validated in both release 12.1.1 and 12.2.2. The view presents reporting group definitions — the mechanisms by which plans and programs are grouped for reporting and administration purposes. Reporting groups allow benefit administrators to organize plans under common headers so that eligibility, enrollment, and cost data can be analyzed or administered by category rather than by individual plan.

The view is one of a family of "BV" (business view) objects that expose base tables in a denormalized, user-friendly form. It resolves the base table's internal codes — notably RPTG_PRPS_CD — into descriptive values, and it enforces multi-tenant security by restricting rows to the business group returned by the security profile. It also supplies a descriptive flexfield reference token so that the consuming form or report can render the DFF segment associated with the BEN_RPTG_GRP entity. The view is defined WITH READ ONLY, so it is intended strictly for query and reporting, never for DML.

Underlying Base Objects

The view is defined over three documented base objects:

• BEN_RPTG_GRP (SYNONYM) — the base reporting group table. It supplies the reporting purpose code, function code, legislation code, description, identifier, business group, and the standard WHO audit columns.
• BEN_RPTG_GRP_TL (SYNONYM) — the translation (TL) table for reporting groups, supplying the language-dependent NAME value. The join to this table is filtered by TL.LANGUAGE = USERENV('LANG'), returning the name in the session's current language.
• HR_BIS (PACKAGE) — the HR business intelligence/security package. Its BIS_DECODE_LOOKUP function decodes the lookup type BEN_RPTG_PRPS, and GET_SEC_PROFILE_BG_ID provides the business group used for row-level security filtering.

The security predicate compares the row's business group against HR_BIS.GET_SEC_PROFILE_BG_ID, using nested NVL expressions so that rows matching the session's secured business group are returned.

Key Columns

• NAME — the reporting group name from the translated table, shown in the session language.
• RPG_DESC — the free-text description of the reporting group.
• FUNCTION_CODE — the function classification of the reporting group.
• LEGISLATION_CODE — the legislation (country/regulatory) context for the group.
• RPTG_PRPS_CD — the reporting purpose code. This is the column most often searched by users investigating reporting group behavior; it stores the short lookup value identifying the group's purpose.
• RPTG_PRPS_CD_M — the decoded, meaning-value form of RPTG_PRPS_CD, produced by HR_BIS.BIS_DECODE_LOOKUP('BEN_RPTG_PRPS', BNR.RPTG_PRPS_CD). Use this column when a readable label is required.
• "_DF:BNR" — a descriptive flexfield reference token identifying the DFF context for BEN_RPTG_GRP.
• RPTG_GRP_ID — the primary key of the reporting group.
• BUSINESS_GROUP_ID — the owning business group; also drives the security filter.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — standard WHO audit columns.

Common Use Cases and Queries

The view is commonly used in benefit administration reports, plan/program setup listings, and diagnostic queries that explain how plans are grouped. A typical listing that resolves the reporting purpose to a readable meaning is:

• SELECT rptg_grp_id, name, rptg_prps_cd, rptg_prps_cd_m, legislation_code, business_group_id FROM apps.benbv_rptg_grp_v ORDER BY name;
• Filtering by purpose: SELECT name, rptg_prps_cd_m FROM apps.benbv_rptg_grp_v WHERE rptg_prps_cd = :purpose;
• Joining to plan-level data by RPTG_GRP_ID to attribute plans to their reporting group for enrollment or cost analysis.

Because the view is read-only and enforces business group security automatically, it is a safe source for ad hoc queries and custom reports without additional row-level filtering. Note that RPTG_PRPS_CD_M depends on the BEN_RPTG_PRPS lookup, so decoded values reflect the current lookup configuration.