Results for “ben_rptg_prps”

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

Overview

APPS.BENBV_RPTG_GRP_V is a reporting view in the Oracle E-Business Suite Benefits (BEN) module. It exposes reporting group definitions together with their translated descriptive attributes and reporting purpose meanings, presenting a denormalized, query-friendly projection of the underlying reporting group tables. The view is owned by the APPS schema and is registered under FND Design Data as BEN.BENBV_RPTG_GRP_V.

The view's principal function is to support business intelligence and reporting consumers who need reporting group metadata without joining the BEN_RPTG_GRP and BEN_RPTG_GRP_TL tables manually. The suffix "_V" denotes a view, and the "BV" prefix is characteristic of Oracle's Business Intelligence/views layer within the Benefits product family. Note that Oracle classifies this object as Internal Use Only: access is supported only from standard Oracle Applications programs, and direct customer queries should be treated as unsupported.

Underlying Base Objects

According to the documented metadata (ETRM 12.2.2), BENBV_RPTG_GRP_V is defined over the following base objects, which appear in the APPS schema as synonyms:

• BEN_RPTG_GRP — the primary reporting group entity, supplying core attributes such as name, description, and foreign keys.
• BEN_RPTG_GRP_TL — the translation (TL) table for reporting groups, supplying language-dependent descriptive text.
• HR_BIS — a package used in the view's construction, typically for business group security or session context evaluation.

The view is exposed publicly as PUBLIC.BENBV_RPTG_GRP_V, meaning it can be referenced without the APPS schema qualifier by authorized sessions. The presence of the _TL table indicates the view honors multi-language installations, resolving descriptive columns according to the session language.

Key Columns

• RPTG_GRP_ID (NUMBER, 15) — System-generated primary key uniquely identifying each reporting group record.
• NAME (VARCHAR2, 240) — Reporting group name, sourced from the translated base table.
• RPG_DESC (VARCHAR2, 240) — Reporting group description.
• RPTG_PRPS_CD (VARCHAR2, 30) — Reporting purpose lookup code, based on lookup type BEN_RPTG_PRPS.
• RPTG_PRPS_CD_M (VARCHAR2, 4000) — Reporting purpose lookup meaning corresponding to RPTG_PRPS_CD. This is the column most commonly sought by users searching on "rptg_prps_cd_m."
• FUNCTION_CODE (VARCHAR2, 30) — Functional classification applied to the reporting group.
• LEGISLATION_CODE (VARCHAR2, 30) — Legislation (country/regulatory) context for the reporting group.
• BUSINESS_GROUP_ID (NUMBER, 15) — Foreign key to HR_ORGANIZATION_UNITS, enforcing business group partitioning.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — Standard WHO audit columns.
• _DF:BNR (CHAR, 24) — Descriptive flexfield context/segment column (BNR context) associated with the reporting group.

Common Use Cases and Queries

The view supports reporting on Benefits reporting group configurations, particularly where a user needs the reporting purpose meaning alongside its coded value. A typical query retrieving the meaningful description for reporting groups in a given business group is:

SELECT r.RPTG_GRP_ID,
       r.NAME,
       r.RPTG_PRPS_CD,
       r.RPTG_PRPS_CD_M,
       r.LEGISLATION_CODE,
       r.FUNCTION_CODE
FROM   APPS.BENBV_RPTG_GRP_V r
WHERE  r.BUSINESS_GROUP_ID = :p_business_group_id
AND    r.RPTG_PRPS_CD_M IS NOT NULL;

Another common pattern is lookup validation, confirming that a stored RPTG_PRPS_CD resolves to an active BEN_RPTG_PRPS meaning via RPTG_PRPS_CD_M. Because RPTG_PRPS_CD_M can be up to 4000 characters, report layouts should allow for wide output columns. Users searching the term "rptg_prps_cd_m" are almost certainly attempting to reference this lookup-meaning column; it should always be correlated with RPTG_PRPS_CD for unambiguous interpretation.

As with all Internal Use Only objects, production integration should route through supported Oracle APIs rather than direct view queries.