Results for “len_attribute30”

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

Overview

The BEN_LEE_RSN view is a public API-layer database object owned by the APPS schema within the Oracle E-Business Suite Advanced Benefits (BEN) product family. Its status is VALID, and it is classified in the ETRM repository as a retrofitted view, meaning it forms part of the standardized interface layer through which Oracle delivers read-only access to Benefits configuration data. The view exposes the Life Event Reasons (LER) and Life Event Reason eligibility-rule definitions processed by the Benefits engine during life event and open enrollment processing.

In Oracle EBS 12.1.1 and 12.2.2, this object presents a date-effective, session-aware snapshot of the underlying Life Event Reason rules. Its principal role in reporting and integration is to give SQL-based consumers — custom reports, concurrent programs, interfaces, and third-party integrations — a stable, developer-friendly projection of the ben_lee_rsn_f table without requiring direct access to the base entity. Because the view filters records against the effective date registered in FND_SESSIONS, queries return only those rule versions valid for the user's current application session, which aligns reported data with the same temporal context the Oracle Forms UI uses.

Underlying Base Objects

According to the documented ETRM 12.2.2 metadata, BEN_LEE_RSN is defined over two referenced base objects, both exposed to the view as synonyms:

• BEN_LEE_RSN_F (SYNONYM) — the principal base table holding Life Event Reason eligibility-rule rows. The _F suffix denotes a date-effective (datetracked) or translated entity, consistent with the presence of EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns.
• FND_SESSIONS (SYNONYM) — the Applications session table. The view text joins this object in its WHERE clause to resolve the current session's effective date through USERENV('SESSIONID').

The view does not perform aggregation, joins to other Benefits entities, or translation; it is a straight projection with an inline session-based effective-date predicate applied to the outer _F table. The documented view text confirms a single-source SELECT from BEN_LEE_RSN_F LEN with two correlated subqueries against FND_SESSIONS SS, matching on SESSION_ID and constraining EFFECTIVE_START_DATE and EFFECTIVE_END_DATE around the session effective date.

Key Columns

The view exposes the full column set of BEN_LEE_RSN_F. Significant columns include:

• LEE_RSN_ID — primary identifier of the life event reason record.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — datetrack effective range; the view's predicate is built upon these two columns.
• BUSINESS_GROUP_ID — owning business group, enabling multi-organization filtering.
• POPL_ENRT_TYP_CYCL_ID — identifier of the associated enrollment type cycle.
• LER_ID — foreign key to the life event reason definition in the Benefits LER tables.
• Enrollment-dating columns (CLS_ENRT_DT_TO_USE_CD, ENRT_CVG_STRT_DT_CD, ENRT_CVG_END_DT_CD, ENRT_PERD_STRT_DT_CD, ENRT_PERD_END_DT_CD and their RL variants) — control how coverage and enrollment period dates are derived when the reason is triggered.
• REINSTATE_CD / REINSTATE_OVRDN_CD — reinstate behavior flags.
• ENRT_PERD_STRT_DAYS / ENRT_PERD_END_DAYS — day offsets applied to enrollment period boundaries.
• LEN_ATTRIBUTE1 … LEN_ATTRIBUTE30 — descriptive flexfield attribute columns for customer-defined data.
• Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) — standard EBS audit and optimistic-locking fields.

Common Use Cases and Queries

This view is typically queried to validate life event reason configuration, to feed downstream eligibility interfaces, and to reconcile enrollment-cycle rule data during implementation or support activities. Because it is session-sensitive, a database session initialized by an EBS application user returns the same effective version that the forms layer would surface. A representative query is shown below.

• Retrieve all active life event reason rules for a business group:

  SELECT lee_rsn_id, ler_id, popl_enrt_typ_cycl_id,
         effective_start_date, effective_end_date
    FROM ben_lee_rsn
   WHERE business_group_id = :p_bg_id
   ORDER BY effective_start_date DESC;

• Enumerate the flexfield attributes configured on a rule:

  SELECT lee_rsn_id,
         len_attribute_category,
         len_attribute1, len_attribute2, len_attribute3
    FROM ben_lee_rsn
   WHERE lee_rsn_id = :p_lee_rsn_id;

• Reconcile the view against its base table to confirm datetrack alignment:

  SELECT v.lee_rsn_id, f.effective_start_date
    FROM ben_lee_rsn v, ben_lee_rsn_f f
   WHERE v.lee_rsn_id = f.lee_rsn_id
     AND v.effective_start_date = f.effective_start_date;

Integrators should note that the session-effective filter is intrinsic to the view; queries executed from non-EBS sessions lacking a matching FND_SESSIONS row will return no data, and direct base-table access should be used only where all datetrack versions are required.