Search Results prtn_eff_strt_dt_cd




Overview
Explore in AI Chat

Overview

BEN_PRTN_ELIG_F is a transactional table in the BEN (Advanced Benefits) product of Oracle E-Business Suite, documented as valid across ETRM 12.1.1 and 12.2.2. Its stated purpose is to store the eligibility criteria for a compensation object. In practice it functions as an eligibility rule definition table: each row describes the qualifying conditions and timing rules that determine whether a person or assignment is eligible for a given compensation object, such as a plan, program, plan type, or option.

The table is date-tracked. Its primary key, BEN_PRTN_ELIG_F_PK, is a composite of PRTN_ELIG_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE, which is the standard Oracle effective-dating pattern used throughout the BEN schema. Records are versioned by date rather than overwritten, so historical eligibility definitions remain queryable.

The ETRM metadata classifies this object heuristically as standalone under a Data Vault lens. As a modeling suggestion, that indicates the table is not formally joined to other tables through declared foreign keys in the vault classification. In practice it is best treated as a satellite-style eligibility attribute set keyed by a business entity identifier (PRTN_ELIG_ID) and its effective dates. The physical schema documents 62 columns.

Key Information Stored

The following columns carry the substantive eligibility logic:

Common Use Cases and Queries

Typical uses include auditing eligibility rule configuration, reproducing eligibility decisions for a given date, and reporting on waiting-period or maximum-period-of-enrollment settings across plans.

A common pattern is to retrieve the rule or rules effective on a given date, using the standard effective-date predicate:

  • SELECT prtn_elig_id, pl_id, ptn_elig_id, effective_start_date, effective_end_date FROM ben.ben_prtn_elig_f WHERE TRUNC(:p_date) BETWEEN effective_start_date AND effective_end_date;
  • Filter by compensation object when reconciling configuration for a specific plan: WHERE pl_id = :pl_id AND SYSDATE BETWEEN effective_start_date AND effective_end_date.
  • Report waiting-period configuration grouped by unit: SELECT wait_perd_uom, COUNT(*) FROM ben.ben_prtn_elig_f GROUP BY wait_perd_uom.
  • Join the DFF block to a value set for descriptive reporting: SELECT prtn_elig_id, epa_attribute1, epa_attribute2 FROM ben.ben_prtn_elig_f, then resolve each attribute against its registered value set.

Because the table is date-tracked, any reporting query should include an effective-date predicate to avoid duplicate historical versions of the same PRTN_ELIG_ID.

Related Objects

Eligibility rules defined in this table are consumed by the BEN eligibility engine and by the configuration tables it qualifies. The most significant related objects are:

  • BEN_PRTN_ELIG (and its non-date-tracked counterpart) — the master entity to which the _F date-tracked rows belong, joined on PRTN_ELIG_ID.
  • BEN_PL_F — plan definition, joined on PL_ID.
  • BEN_PGM_F — program definition, joined on PGM_ID.
  • BEN_PTIP_F — plan type in program, joined on PTIP_ID.
  • BEN_PLIP_F — plan in program, joined on PLIP_ID.
  • BEN_OIPL_F — option in plan list, joined on OIPL_ID.
  • BEN_PRTN_ELIG_F's DFF views — the descriptive flexfield view associated with EPA_ATTRIBUTE_CATEGORY / EPA_ATTRIBUTE1–30.
  • The BEN eligibility APIs and the Advanced Benefits concurrent processes that evaluate eligibility at run time and persist results into participant eligibility and enrollment tables.

No declared foreign keys exist per the heuristic classification, so all relationships above are established by the referenced identifier columns rather than enforced database constraints.