Results for “elig_per_opt_id”

50+ results




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

Overview

BEN_ELIG_PER_OPT_D is an APPS-owned reporting view within the Oracle Advanced Benefits (BEN) module of Oracle E-Business Suite, valid in releases 12.1.1 and 12.2.2. It presents a denormalized, user-readable representation of eligibility and participation option rules defined in the Benefits configuration layer. Whereas the underlying base table BEN_ELIG_PER_OPT_F stores raw foreign-key identifiers and lookup codes, the view resolves those codes into meaningful descriptions by joining to HR_LOOKUPS, and it exposes the option name from BEN_OPT_F and the updating user name from FND_USER. As a "_D" (description) view, it is intended primarily for reporting, data extraction, and integration scenarios in which functional users or downstream systems require readable eligibility rule definitions rather than numeric identifiers. The view carries the standard Oracle EBS date-tracked columns EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, reflecting the datetracked nature of the base table.

Underlying Base Objects

The view is defined over several documented objects. BEN_ELIG_PER_OPT_F is the primary base object and contributes all eligibility/participation option rule data, including the ROWID projected as ROW_ID. BEN_OPT_F is joined on OPT_ID to supply the eligibility option name and is a non-mandatory (outer) join in the view text. FND_USER is joined on LAST_UPDATED_BY to resolve the user name. Three HR_LOOKUPS aliases—ELIG, OVRIDN, and NO_MX_PRTN_OVRID_THRU—are joined on the YES_NO lookup type to translate the eligibility flag, the participation override flag, and the "no maximum participation override through" flag respectively. Two additional HR_LOOKUPS aliases, PRTN_OVRIDN_RSN and ONCE_R_CNTNG, provide outer-joined descriptions for the override reason code (BEN_OVRID_RSN) and the "once reaching counting" code (BEN_ONCE_R_CNTNG). The documented base object list also references the HR_API package and the HR_LOOKUPS view.

Key Columns

Common Use Cases and Queries

Typical uses include auditing eligibility rule configurations, reconciling participation start and end dates against plan enrollments, and feeding downstream extracts. A representative query filtering on the participation start date is:

SELECT elig_per_opt_id, opt_name, elig_meaning, prtn_strt_dt, prtn_end_dt, effective_start_date, effective_end_date FROM apps.ben_elig_per_opt_d WHERE prtn_strt_dt BETWEEN :p_start AND :p_end ORDER BY prtn_strt_dt;

To locate rules updated by a specific user: SELECT elig_per_opt_id, opt_name, last_updated_by, last_update_date FROM apps.ben_elig_per_opt_d WHERE last_updated_by = 'SYSADMIN';

Because the view joins to datetracked base objects, queries may return multiple rows per rule across effective periods; reporting logic should generally constrain EFFECTIVE_START_DATE and EFFECTIVE_END_DATE to the desired as-of date.