Results for “wait_perd_dt_to_use_rl”

50+ results




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

Overview

BEN_PRTN_ELIG_V is an Oracle E-Business Suite Advanced Benefits (BEN) view owned by the APPS schema. The ETRM metadata describes it simply as "Retrofitted," indicating that the view was introduced or regenerated during an upgrade or patch cycle to preserve backward compatibility for external references while the underlying data model evolved. Functionally, the view presents partition eligibility rule definitions associated with program, plan, and option-in-plan combinations. In Oracle Advanced Benefits, participation eligibility determines the population of employees who qualify for a given program or plan based on configurable criteria such as effective dates, waiting periods, and eligibility determination rules.

The view is not a simple projection. It embeds a session-aware filter that ties the returned rows to the current runtime context, making it behave like a date-effective (datetracked) inquiry view rather than a flat reporting table. This design is characteristic of EBS date-tracked views, where the effective date of the user's session — not the system date — governs which row version is returned.

Underlying Base Objects

The documented base objects for this view are BEN_PRTN_ELIG_F and FND_SESSIONS, both referenced as synonyms under APPS.

  • BEN_PRTN_ELIG_F is the base table that stores partition eligibility rule definitions. Its columns carry the core eligibility attributes — program, plan and option identifiers, effective dates, date-rule references, and the descriptive flexfield (DFF) attribute segment set (EPA_ATTRIBUTE1 through EPA_ATTRIBUTE30).
  • FND_SESSIONS supplies the runtime session context. The join condition SE.SESSION_ID = USERENV('SESSIONID') restricts rows to the current user session, while SE.EFFECTIVE_DATE BETWEEN EPA.EFFECTIVE_START_DATE AND EPA.EFFECTIVE_END_DATE restricts the base table to the row version effective as of the session's effective date.

Because of this join, the view returns exactly one effective-dated version of each eligibility rule per session, rather than the full history stored in the base table. The underlying base object is the date-tracked table; the view adds session scoping on top of it.

Key Columns

Common Use Cases and Queries

The view is typically used in eligibility diagnostics, benefit configuration reporting, and data extracts. Because it is session-filtered, it is best queried from within an active EBS session or converted to a direct base-table query when a specific effective date must be applied.

  • Retrieve active eligibility rules for a plan: SELECT prtn_elig_id, pl_id, prtn_eff_strt_dt_cd, wait_perd_val FROM ben_prtn_elig_v WHERE pl_id = :plan_id;
  • List maximum period of enrollment settings: SELECT prtn_elig_id, mx_poe_uom, mx_poe_val FROM ben_prtn_elig_v WHERE mx_poe_val IS NOT NULL;
  • Inspect DFF attributes: SELECT prtn_elig_id, epa_attribute_category, epa_attribute1 FROM ben_prtn_elig_v WHERE epa_attribute_category IS NOT NULL;
  • Audit recent changes: SELECT prtn_elig_id, last_update_date, last_updated_by FROM ben_prtn_elig_v ORDER BY last_update_date DESC;

For historical analysis reaching beyond the session effective date, developers should query BEN_PRTN_ELIG_F directly and supply explicit EFFECTIVE_START_DATE and EFFECTIVE_END_DATE predicates, since the view cannot return rows outside the active session context.