Results for “rpg_desc”

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

Overview

BEN_RPTG_GRP is the reporting group definition table within the Oracle Advanced Benefits (BEN) module. It stores the named groupings that control how participant populations, plan enrollments, and benefit actions are aggregated, filtered, and presented for reporting and processing purposes. In Oracle EBS 12.1.1 and 12.2.2, the table resides in the BEN schema and is flagged VALID in the ETRM repository, confirming it as a supported, documented object in the Applications data model.

From a Data Vault modeling perspective, the heuristic classification for BEN_RPTG_GRP is hub-leaning. This is a modeling suggestion rather than a functional label: the table carries a single-column surrogate primary key (RPTG_GRP_ID) and is referenced by multiple downstream tables as a foreign key target, which is characteristic of a hub entity holding the stable business key of a reporting group. The descriptive columns supplied via the DFF attribute set (BNR_ATTRIBUTE1–30) and the descriptive columns (NAME, RPG_DESC) additionally give it satellite-like characteristics, but the primary structural role is as an anchor referenced by other benefit objects.

Key Information Stored

The table contains 45 documented columns in the 12.2.2 physical schema. The most operationally significant are summarized below.

• RPTG_GRP_ID — the surrogate primary key, constrained by unique index BEN_RPTG_GRP_PK. It is the single documented business-key candidate; no alternate unique index is defined, so RPTG_GRP_ID is the sole reliable identifier for joining.
• NAME — the user-visible name of the reporting group. This is the primary descriptive identifier used in self-service and setup forms.
• BUSINESS_GROUP_ID — the HR business group to which the reporting group belongs, establishing the multi-tenant partitioning boundary across the BEN schema.
• RPTG_PRPS_CD — the reporting purpose code, which determines the business intent of the group (for example, a specific reporting or processing context).
• RPG_DESC — a longer free-text description of the reporting group, typically rendered in lookup and selection lists.
• FUNCTION_CODE — identifies the functional area or processing context with which the group is associated.
• LEGISLATION_CODE — the legislative/regulatory context (for example a country or locale), which drives which benefit regulations apply.
• ORDR_NUM — the display ordering sequence used when reporting groups are presented to users or in reports.
• BNR_ATTRIBUTE_CATEGORY and BNR_ATTRIBUTE1–30 — a thirty-column descriptive flexfield attribute set, allowing customer-specific extensions to be stored alongside the seeded attributes without schema modification.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER — standard Oracle Applications audit columns supporting concurrency control, change tracking, and row-level locking diagnostics.

Common Use Cases and Queries

The table is typically queried to resolve a reporting group ID into its name and description for downstream reports, or to enumerate all groups available for a given business group and legislation. A common pattern joins the group to population-level definitions to build participation-by-group extracts:

• Resolving a group reference captured on a transaction: SELECT name, rpg_desc FROM ben_rptg_grp WHERE rptg_grp_id = :p_group_id.
• Listing active groups for an organization: SELECT rptg_grp_id, name, rptg_prps_cd FROM ben_rptg_grp WHERE business_group_id = :p_bg_id ORDER BY ordr_num.
• Auditing recently changed definitions using LAST_UPDATE_DATE in conjunction with CREATED_BY / LAST_UPDATED_BY.
• Joining to BEN_POPL_RPTG_GRP_F to associate groups with population definitions, and to BEN_BENEFIT_ACTIONS to trace the group referenced during a benefit life event or action.
• Report extracts that filter by LEGISLATION_CODE to produce jurisdiction-specific benefit populations.

Related Objects

BEN_RPTG_GRP is referenced by several benefit and HR transaction tables through the RPTG_GRP_ID foreign key. The most significant dependencies documented in the ETRM relationship data are:

• BEN_BENEFIT_ACTIONS — references BEN_RPTG_GRP.RPTG_GRP_ID; links benefit actions to the reporting group under which they were processed.
• BEN_PL_REGN_F — references RPTG_GRP_ID; associates plan regulations with reporting groups.
• BEN_PL_REGY_BOD_F — references RPTG_GRP_ID; ties plan regulatory body definitions to reporting groups.
• BEN_POPL_RPTG_GRP_F — references RPTG_GRP_ID; the population-to-reporting-group assignment table.
• HR_API_TRANSACTIONS — references RPTG_GRP_ID; records the reporting group on HR API transaction payloads.
• PQH_SS_TRANSACTION_HISTORY — references RPTG_GRP_ID; captures the reporting group in self-service transaction history for audit purposes.

Because all of these tables store the RPTG_GRP_ID value rather than the group name, any report that requires the human-readable group label must join back to BEN_RPTG_GRP on RPTG_GRP_ID.