Search Results rptg_grp_name




Overview

APPS.BEN_POPL_RPTG_GRP_D is an Oracle E-Business Suite internal database view owned by the APPS schema and registered under the FND Design Data identifier BEN.BEN_POPL_RPTG_GRP_D. It exposes reporting group definitions used by the Oracle Advanced Benefits (BEN) module in release 12.1.1 and 12.2.2. The view is a denormalized presentation layer that joins the base reporting-group entity to its associated program and plan-list names, producing a human-readable projection of the "Post-Open Enrollment Processing" (POPL) reporting group configuration.

The "_D" suffix denotes a denormalized or display-oriented view whose purpose is to resolve foreign-key identifiers into descriptive text. Rather than forcing report authors and concurrent programs to reconstruct the relationship graph themselves, the view exposes RPTG_GRP_NAME, PGM_NAME, and PL_NAME as ready-to-consume columns. This view is classified as Oracle Internal Use Only: Oracle Corporation does not support direct access to applications data through this object except from standard Oracle Applications programs. Consequently, reporting integrations should treat it as a seeded dictionary object rather than a supported extension point. Its status is VALID in the documented environments.

Underlying Base Objects

The view is defined over four BEN base entities plus the standard user table, all resolved through APPS synonyms:

  • BEN_POPL_RPTG_GRP_F — the reporting group header table supplying the primary key POPL_RPTG_GRP_ID, effective dating, and ordering.
  • BEN_RPTG_GRP — the reporting group definition providing the RPTG_GRP_NAME translated label.
  • BEN_PGM_F — the program definition supplying PGM_NAME.
  • BEN_PL_F — the plan definition supplying PL_NAME.
  • FND_USER — referenced by the LAST_UPDATED_BY foreign key to resolve the standard WHO audit column to a user identity.

The view is referenced downstream by a PUBLIC synonym of the same name, confirming that external tooling and Oracle's own concurrent programs query it through the public namespace. The documented dependency graph is therefore a star join centered on the reporting group foreign header.

Key Columns

  • ROW_ID (ROWID) — the physical row identifier for the joined result.
  • POPL_RPTG_GRP_ID (NUMBER 15) — primary key of the reporting group; the join key back to the _F header table.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE (DATE) — date-tracked effective range for the reporting group row, essential for "as of" queries.
  • RPTG_GRP_NAME (VARCHAR2 240) — the descriptive reporting group name, the column most commonly targeted by searches for the string "rptg_grp_name".
  • PGM_NAME (VARCHAR2 240) — the program name associated with the group, denormalized for display.
  • PL_NAME (VARCHAR2 240) — the plan name associated with the group.
  • ORDR_NUM (NUMBER 15) — display sort order for the group.
  • LAST_UPDATE_DATE / LAST_UPDATED_BY — standard WHO audit columns; the latter is a foreign key to FND_USER.USER_ID.

Common Use Cases and Queries

Typical usage centers on validating configuration, driving concurrent processing, and producing ad-hoc extracts. A common pattern is filtering by name, which is precisely the column surfaced in the search term "rptg_grp_name":

  • Locate a reporting group by nameSELECT popl_rptg_grp_id, rptg_grp_name, pgm_name, pl_name FROM apps.ben_popl_rptg_grp_d WHERE rptg_grp_name LIKE :name;
  • Effective-dated lookup — add WHERE TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date to retrieve only currently effective definitions.
  • Program/plan cross-reference — group by pgm_name or pl_name to audit which plans are bundled into each reporting group.
  • Audit extraction — join last_updated_by to fnd_user.user_id to identify the last maintainer of each row.

Because the view is unsupported for external access, these queries are appropriate for diagnostic and reporting use rather than for building custom declarative integrations; supported interfaces should be preferred where Oracle provides them.