Results for “ben_elig_per_opt”

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

Overview

BEN_ELIG_PER_OPT is a VALID view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the BEN (Advanced Benefits) product family. It is available in both EBS 12.1.1 and 12.2.2. The view exposes eligibility and participation option records that link a person's eligibility determination to the specific benefit options and plan-in-life-event combinations for which they qualify. In functional terms, it represents the intersection of eligibility processing (ELIG_PER) with the option-level (OPT) and plan-in-life-event (PER_IN_LER) setup used by the Oracle Advanced Benefits engine to drive enrollment flexibility.

Because BEN_ELIG_PER_OPT is a reporting-facing view rather than a base table, it is most commonly consumed by benefit extract processes, payroll integration, custom reports, and ad hoc queries that need to reconcile which options a participant is entitled to at a given point in time. It is not intended for direct DML; all maintenance should be performed through the underlying Advanced Benefits forms and concurrent programs, which write to the base table BEN_ELIG_PER_OPT_F.

Underlying Base Objects

Per the ETRM metadata, the view is defined over the following documented referenced objects:

• BEN_ELIG_PER_OPT_F (accessed via a synonym) — the primary base table storing eligibility-to-option records, including effective-dated rows, override flags, waiting-period dates, and the extensive EPO_ATTRIBUTE1 through EPO_ATTRIBUTE30 descriptive flexfield columns.
• BEN_PER_IN_LER (accessed via a synonym) — the plan-in-life-event table that qualifies a person's eligibility within a specific life event.
• FND_SESSIONS (accessed via a synonym) — a standard Oracle Application Object Library reference used in the view text, typically to support session- or context-sensitive filtering.

The view text is a straightforward projection of the EPO alias (BEN_ELIG_PER_OPT_F), selecting key columns such as ELIG_PER_OPT_ID, ELIG_PER_ID, OPT_ID, PER_IN_LER_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE, alongside the audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) and the WHO-DONE-IT concurrency columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE).

Key Columns

• ELIG_PER_OPT_ID — Primary key for the eligibility-per-option record.
• ELIG_PER_ID — Foreign key to the parent eligibility record for the person.
• OPT_ID — The benefit option the person is eligible for.
• PER_IN_LER_ID — The plan-in-life-event identifier linking eligibility to a specific life event.
• ELIG_FLAG — Indicates whether the person is eligible (Y/N).
• PRTN_OVRIDN_FLAG / PRTN_OVRIDN_THRU_DT — Participation override indicator and its effective-through date.
• WAIT_PERD_CMPLTN_DT / WAIT_PERD_CMPLTN_DATE — Waiting period completion dates, used to determine when eligibility becomes effective.
• RT_* columns (e.g., RT_AGE_VAL, RT_LOS_VAL, RT_HRS_WKD_VAL, RT_COMP_REF_AMT) — "RT" prefixed columns hold the resolved/run-time values used in eligibility rule evaluation.
• FND_SESSIONS — supports session-context joins used elsewhere in the view definition.
• EPO_ATTRIBUTE1..30 — Descriptive flexfield segments for customer-specific extensions.

Common Use Cases and Queries

Typical uses include auditing which options a participant is eligible for, troubleshooting enrollment failures, and building extracts for downstream systems. Example query:

• List eligible options for a person:
  SELECT elig_per_opt_id, elig_per_id, opt_id, elig_flag, effective_start_date, effective_end_date FROM apps.ben_elig_per_opt WHERE elig_flag = 'Y' AND SYSDATE BETWEEN effective_start_date AND effective_end_date;
• Waiting-period and participation overrides:
  SELECT elig_per_opt_id, wait_perd_cmpltn_dt, prtn_ovridn_flag, prtn_ovridn_thru_dt FROM apps.ben_elig_per_opt;
• Join to plan-in-life-event for reporting:
  SELECT e.elig_per_opt_id, e.opt_id, e.per_in_ler_id FROM apps.ben_elig_per_opt e WHERE e.per_in_ler_id IS NOT NULL;

Given that the view is a direct projection of BEN_ELIG_PER_OPT_F, no aggregation is applied, so row counts and performance characteristics mirror the base table. Join conditions and where clauses targeting ELIG_PER_ID, OPT_ID, or PER_IN_LER_ID should be indexed appropriately on the base table to avoid full scans in high-volume benefit extracts.