Results for “ben_elig_per_opt_x”

20 results




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

Overview

The BEN_ELIG_PER_OPT_X view is a denormalized reporting and integration object within the Oracle E-Business Suite Advanced Benefits (BEN) module. It is owned by the APPS schema and holds a VALID status in both Oracle EBS 12.1.1 and 12.2.2 environments. The view exposes the configuration of eligibility criteria that link a person's eligibility record to specific plan options — in other words, it answers the question of which options a participant is eligible to elect given a particular eligibility profile and option setup.

In the EBS benefits data model, eligibility rules for life events, plan options, and compensation are stored across numerous normalized base tables. The _X suffix convention indicates that this object is an extension or extract view rather than an operational base entity. It presents a flattened, query-friendly projection of the underlying eligibility-per-option records, including the many descriptive (attribute) columns and the runtime (RT_) calculation columns used to evaluate eligibility at processing time.

Because it joins eligibility attributes with option identity and runtime values, this view is commonly used by benefits administrators, technical consultants, and developers when building custom reports, extracts, or diagnostic queries against the Advanced Benefits configuration.

Underlying Base Objects

Per the documented ETRM metadata, BEN_ELIG_PER_OPT_X is defined over two referenced base objects:

  • BEN_ELIG_PER_OPT_F (exposed via a SYNONYM) — the core eligibility-per-option table holding the canonical eligibility assignment records. The alias EPO in the view text corresponds to this object, and nearly every projected column is prefixed EPO.
  • BEN_PER_IN_LER (exposed via a SYNONYM) — the persons-in-life-event-reason table that associates a person with a life-event reason record (represented by the PER_IN_LER_ID column).

The view therefore acts as a structured read layer atop the normalized eligibility tables, surfacing both the "seed" eligibility values (the non-RT_ columns such as LOS_VAL, AGE_VAL, COMP_REF_AMT) and their runtime-evaluated counterparts (RT_LOS_VAL, RT_AGE_VAL, RT_COMP_REF_AMT). This dual representation is important: administrative setup values are held in the base columns, while the RT_ columns reflect the computed values actually applied when the eligibility engine evaluates a participant.

Key Columns

Common Use Cases and Queries

A frequent use case is troubleshooting why a participant is or is not eligible for a given option, which is precisely the scenario in which the rt_los_val column is examined. The query below returns runtime length-of-service values alongside the base LOS values for analysis:

  • Eligibility diagnostics — Compare RT_LOS_VAL against LOS_VAL to verify that the runtime evaluation matches configured setup.
  • Configuration reporting — Extract all options tied to a given ELIG_PER_ID or OPT_ID for audit or migration.
  • Integration extracts — Feed flattened eligibility-option data to downstream benefits portals or third-party carriers.
  • Life-event analysis — Join on PER_IN_LER_ID to trace eligibility outcomes back to the triggering life event.

Sample SQL:

SELECT epo.elig_per_opt_id,
       epo.elig_per_id,
       epo.opt_id,
       epo.per_in_ler_id,
       epo.los_val,
       epo.rt_los_val,
       epo.rt_los_uom,
       epo.rt_frz_los_flag,
       epo.elig_flag
  FROM apps.ben_elig_per_opt_x epo
 WHERE epo.effective_start_date <= SYSDATE
   AND NVL(epo.effective_end_date, SYSDATE) >= SYSDATE;