Results for “benbv_lee_rsn_v”

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

Overview

BENBV_LEE_RSN_V is a read-only Oracle EBS view owned by the APPS schema within the BEN (Advanced Benefits) product family. Its name derives from its role: it exposes the "Life Event Enrollment Reason" (LEE_RSN) processing rules that govern how a life event triggers enrollment activity for a program or plan. In functional terms, the view identifies the parameters that control program or plan enrollment activities — defining when key enrollment activities occur and how enrollment dates are determined relative to a qualifying life event.

The view is the primary interface used by the Advanced Benefits setup forms (notably the life event reason configuration) and by downstream reporting and integration logic that must resolve date-processing rules for a given life event reason. Because it carries descriptive flexfield context markers and lookup-code decodes, it is equally usable by personalizations, BI Publisher reports, and outbound interfaces that need human-readable values rather than raw codes.

Underlying Base Objects

The view text is defined exclusively over the BEN_LEE_RSN_F table (referenced in the metadata as a synonym resolved to the base object) and the HR_BIS package.

• BEN_LEE_RSN_F — the life event enrollment reason base (and date-tracked) table holding one row per life event reason per effective date range. All business columns, ID columns, and WHO columns in BENBV_LEE_RSN_V originate here.
• HR_BIS — the HR/Benefits utility package supplying two functions used inside the SQL: HR_BIS.BIS_DECODE_LOOKUP (to decode each listed lookup code into its meaning) and HR_BIS.GET_SEC_PROFILE_BG_ID (to constrain rows to the business group derived from the user's security profile).

The view is created WITH READ ONLY, confirming it is intended purely for query access; it is not a DML target. The business group filter is applied as LEN.BUSINESS_GROUP_ID = NVL(HR_BIS.GET_SEC_PROFILE_BG_ID, LEN.BUSINESS_GROUP_ID), so users see only the business group permitted by their security profile, or all groups if no profile value is returned.

Key Columns

The view exposes date, numeric, rule, code, ID, and WHO columns. Principal columns include:

• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — date-tracked validity of the rule row.
• ENRT_PERD_STRT_DT_RL / ENRT_PERD_END_DT_RL — rules determining the start and end of the enrollment period.
• ENRT_CVG_STRT_DT_RL / ENRT_CVG_END_DT_RL — rules determining when enrollment coverage begins and ends.
• RT_STRT_DT_RL / RT_END_DT_RL — start and end rules for the life event itself.
• DYS_AFTR_END_TO_DFLT_NUM, ADDL_PROCG_DYS_NUM, DYS_NO_ENRL_NOT_ELIG_NUM, DYS_NO_ENRL_CANT_ENRL_NUM — day-count parameters controlling defaulting, processing windows, and ineligibility handling.
• 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, RT_STRT_DT_CD, RT_END_DT_CD, ENRT_PERD_DET_OVRLP_BCKDT_CD — each paired with a decoded meaning produced by BIS_DECODE_LOOKUP.
• LEE_RSN_ID, BUSINESS_GROUP_ID, POPL_ENRT_TYP_CYCL_ID, LER_ID — surrogate identifiers and foreign keys.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — standard WHO audit columns.

Common Use Cases and Queries

A typical query returns active life event enrollment reasons with decoded rules for a report or interface:

• Retrieve all enabled date rules for a specific life event reason: SELECT lee_rsn_id, enrt_perd_strt_dt_cd, rt_strt_dt_cd, rt_end_dt_cd FROM apps.benbv_lee_rsn_v WHERE lee_rsn_id = :p_id AND SYSDATE BETWEEN effective_start_date AND effective_end_date;
• Join to lookup meaning columns to display human-readable rule descriptions in a BI Publisher report.
• Feed date-processing parameters (DYS_AFTR_END_TO_DFLT_NUM, ADDL_PROCG_DYS_NUM) into custom enrollment-window calculations.
• Use as a validation source when processing life event enrollments via the public BEN APIs.

Because the view is read-only and secured by business group, it is safe to grant SELECT to reporting users. Any DML must target BEN_LEE_RSN_F directly through supported APIs.