Search Results ben_lee_rsn_f




Overview
Explore in AI Chat

Overview

The BEN_LEE_RSN_F table resides in the BEN schema, the database foundation of the Advanced Benefits (BEN) module in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the configuration of life event enrollment reasons — the rules that determine how a participant's benefits elections are handled when a qualifying life event (marriage, birth, divorce, change of employment status) is processed. Each row defines a distinct enrollment reason that the benefits engine consults during life event processing to establish enrollment periods, coverage effective dates, eligibility windows, and reinstatement behavior.

The object is a date-tracked (effective-dated) table. Its primary key, BEN_LEE_RSN_F_PK, is a composite of LEE_RSN_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE, allowing multiple temporal versions of the same logical reason to coexist. The heuristic Data Vault classification derived from the foreign-key structure is standalone, meaning the table is modeled as an independent construct with no enforced parent relationships in the mined metadata; in a Data Vault design it would most naturally be treated as a hub anchored on LEE_RSN_ID, with a satellite capturing the effective-dated descriptive attributes.

Key Information Stored

The table contains 67 documented columns. The most operationally significant are:

The surrogate key is LEE_RSN_ID as qualified by the effective dates; the unique index BEN_LEE_RSN_F_PK confirms the business-key candidate as the combination of LEE_RSN_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE.

Common Use Cases and Queries

Typical reporting scenarios include listing active enrollment reasons for a business group and auditing date-rule configuration for a life event.

  • Retrieve the current version of a reason: SELECT * FROM ben.ben_lee_rsn_f WHERE lee_rsn_id = :p_id AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;
  • List reasons by business group: SELECT lee_rsn_id, effective_start_date, ler_id FROM ben.ben_lee_rsn_f WHERE business_group_id = :p_bg ORDER BY lee_rsn_id;
  • Audit enrollable windows using the date-code columns ENRT_PERD_STRT_DT_CD and ENRT_PERD_END_DT_CD.
  • Trace life event processing by joining to the associated life event reason through LER_ID.

Because the table is effective-dated, every query should filter on the effective range to avoid returning historical versions.

Related Objects

  • BEN_LER_F / BEN_LER_RSN_F — the life event reason tables joined through LER_ID.
  • BEN_ENRT_TYP_CYCL_F — the enrollment type cycle joined through POPL_ENRT_TYP_CYCL_ID.
  • BEN_PTIP_F — plan type in program definitions used during enrollment cycle resolution.
  • BEN_ELIG_* — eligibility rule tables evaluated when a life event reason is processed.
  • BEN_PER_LEE_F — participant life event records that reference the reason identifier.
  • BEN_LEE_RSN_F_PK — the unique index enforcing the composite business key.

These relationships, together with the code columns embedded in BEN_LEE_RSN_F, form the configuration backbone that Advanced Benefits reads at runtime to create enrollment opportunities and to apply correct coverage, rate, and reinstatement dates for each qualified life event.