Search Results key_ee_det_name

Overview

APPS.BEN_PL_REGN_D is a validated Oracle E-Business Suite view owned by the APPS schema. It exposes benefit plan and reporting group registration data, joining the plan registration and reporting hierarchy with plan definitions and lookup-derived descriptive attributes. In ETRM the object is classified as an internal view (FND Design Data: BEN.BEN_PL_REGN_D), and Oracle's standard warning applies: the object is designated Oracle Internal Use Only and is not supported for direct customer access except from standard Oracle Applications programs. This means the view is intended as a read-only reporting and integration surface rather than a supported extension point.

The view is primarily relevant to Oracle Advanced Benefits (OAB) reporting. The user search term "regn_name" maps directly to the REGN_NAME column, which carries the registration name (VARCHAR2 240). Because the view flattens several BEN entities into a single row per plan registration, it is convenient for concurrent programs, extracts, and diagnostic queries that need registration, plan, and reporting group context without manually joining the underlying registration tables.

Underlying Base Objects

The documented dependencies for APPS.BEN_PL_REGN_D are:

• BEN_PL_REGN_F — plan registration base table, supplying the registration identifier and its date-tracked attributes.
• BEN_PL_F — plan base table (plan name and plan type context).
• BEN_REGN_F — registration base table.
• BEN_RPTG_GRP — reporting group definitions.
• FF_FORMULAS_F — FastFormula definitions, used for non-discrimination and highly compensated logic.
• FND_USER — resolves the LAST_UPDATED_BY standard who column.
• HR_LOOKUPS — lookup values that populate the *_NAME and MEANING descriptive columns.
• HR_API — HR package used within the view logic for date-tracked or business-group resolution.

All base tables and views are referenced through synonyms in the APPS schema (for example, BEN_PL_REGN_F and BEN_REGN_F), while HR_API is referenced as a package. The view therefore inherits the datetrack behavior of the BEN_F family: it exposes EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, and callers are expected to filter on the effective date range appropriate to their context.

Key Columns

• ROW_ID — ROWID of the underlying registration row; useful for row identification in extracts.
• PL_REGN_ID — primary identifier of the plan registration; the join key back to BEN_PL_REGN_F.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — date-tracked validity window for the row.
• REGN_NAME — registration name (VARCHAR2 240); the attribute most commonly searched for by users.
• PL_NAME — associated plan name (VARCHAR2 240).
• RPTG_GRP_NAME — reporting group name (VARCHAR2 240) from BEN_RPTG_GRP.
• HGHLY_COMPD_DET_NAME — highly compensated individual detail name (VARCHAR2 80), relevant to nondiscrimination testing.
• KEY_EE_DET_NAME — key employee detail name (VARCHAR2 80).
• CNTR_NNDSCRN_NAME / CVG_NNDSCRN_NAME — contract and coverage nondiscrimination names (VARCHAR2 80).
• FIVE_PCT_OWNR_NAME — five-percent owner detail name (VARCHAR2 80).
• REGY_PL_TYP_MEANING — regulatory plan type meaning (VARCHAR2 80), derived from HR_LOOKUPS.
• LAST_UPDATE_DATE / LAST_UPDATED_BY — standard who columns; LAST_UPDATED_BY is a foreign key to FND_USER.USER_ID.

Common Use Cases and Queries

The view is typically used in two ways: as a direct source in reporting SQL and as a reference for diagnosing registration configuration. A basic lookup by registration name is shown below.

SELECT ROW_ID, PL_REGN_ID, REGN_NAME, PL_NAME, RPTG_GRP_NAME, REGY_PL_TYP_MEANING, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE FROM APPS.BEN_PL_REGN_D WHERE REGN_NAME = :regn_name AND SYSDATE BETWEEN EFFECTIVE_START_DATE AND NVL(EFFECTIVE_END_DATE, SYSDATE + 1);

For nondiscrimination and executive-compensation analysis, the detail name columns can be projected alongside the registration:

SELECT PL_REGN_ID, REGN_NAME, HGHLY_COMPD_DET_NAME, KEY_EE_DET_NAME, CNTR_NNDSCRN_NAME, CVG_NNDSCRN_NAME, FIVE_PCT_OWNR_NAME FROM APPS.BEN_PL_REGN_D WHERE EFFECTIVE_START_DATE <= :effective_date AND NVL(EFFECTIVE_END_DATE, :effective_date) >= :effective_date;

Because the object is Oracle Internal Use Only, production integrations should consume the view read-only and tolerate schema changes across releases. Where possible, confirm behavior against the 12.1.1 and 12.2.2 documentation for the underlying BEN tables before relying on any column in a custom interface.