Results for “elig_inelig_cd”

50+ results




Overview
Explore in AI Chat

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

Overview

BENBV_ELIG_TO_PRTE_RSN_V is an APPS-owned, read-only database view in the Oracle E-Business Suite Advanced Benefits (BEN) module. It is available in both EBS 12.1.1 and 12.2.2 and carries a VALID status in the ETRM repository. The view identifies the impact of a life event reason on eligibility for a program, plan type in program, plan in program, plan, or option in plan.

In the Benefits architecture, life event reasons trigger eligibility re-evaluation when an employee experiences a qualifying event. This view exposes the configuration that determines how a given life event reason (LER) affects participation eligibility at each level of the benefits hierarchy. It is a "BV" (business view) style object frequently used by Oracle Advanced Benefits forms, concurrent processes, and third-party or custom reporting tools. Because the view is defined WITH READ ONLY, it is intended exclusively for query access, not for DML.

Underlying Base Objects

The view is defined over two documented objects:

The view text aliases the base table as PEO and joins it to decode logic for each coded column. Two decode patterns are used. First, HR_BIS.BIS_DECODE_LOOKUP(lookup_type, code) returns the meaning for coded flexfield values such as BEN_ELIG_INELIG, BEN_PRTN_ELIG_STRT, BEN_PRTN_ELIG_END, BEN_MX_WTG_DT_TO_USE, BEN_MX_POE_DET_DT, BEN_MX_POE_APLS, BEN_FMLY_MMBR, and YES_NO. Second, the descriptive flexfield segment is referenced through the token '_DF:BEN:BEN_ELIG_TO_PRTE_RSN_F:PEO'. The WHERE clause applies business group security via NVL(HR_BIS.GET_SEC_PROFILE_BG_ID, PEO.BUSINESS_GROUP_ID), restricting rows to the session's security profile.

Key Columns

Effective dating is controlled by EFFECTIVE_START_DATE and EFFECTIVE_END_DATE. Core control columns include PRTN_EFF_STRT_DT_RL, PRTN_EFF_END_DT_RL, WAIT_PERD_UOM, WAIT_PERD_VAL, WAIT_PERD_RL, WAIT_PERD_DT_TO_USE_RL, MX_POE_UOM, MX_POE_VAL, MX_POE_RL, MX_POE_DET_DT_RL, and VRFY_FMLY_MMBR_RL, which govern waiting periods, maximum period of enrollment, and family member verification.

Coded columns, each paired with a decoded meaning from BIS_DECODE_LOOKUP, include ELIG_INELIG_CD (eligible/ineligible), PRTN_EFF_STRT_DT_CD and PRTN_EFF_END_DT_CD (participation effective start/end rules), WAIT_PERD_DT_TO_USE_CD, MX_POE_DET_DT_CD, MX_POE_APLS_CD, VRFY_FMLY_MMBR_CD, PRTN_OVRIDBL_FLAG, and IGNR_PRTN_OVRID_FLAG. Identity and foreign key columns are ELIG_TO_PRTE_RSN_ID, BUSINESS_GROUP_ID, LER_ID, PTIP_ID, PLIP_ID, OIPL_ID, PL_ID, and PGM_ID, linking the record to a life event reason, plan type in program, plan in program, option in plan, plan, or program. WHO columns are LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, and CREATION_DATE.

Common Use Cases and Queries

Typical uses include auditing life event reason eligibility configuration, troubleshooting why a life event failed to open enrollment, and feeding downstream reporting. A basic query joins the decoded columns:

  • SELECT elig_to_prte_rsn_id, ler_id, pl_id, pgm_id, elig_inelig_cd, wait_perd_val, effective_start_date, effective_end_date FROM apps.benbv_elig_to_prte_rsn_v WHERE effective_end_date = TO_DATE('4712/12/31','YYYY/MM/DD');

To inspect all reasons configured for a specific life event reason:

  • SELECT * FROM apps.benbv_elig_to_prte_rsn_v WHERE ler_id = :p_ler_id;

To confirm participation override behavior:

  • SELECT elig_to_prte_rsn_id, prtn_ovridbl_flag, ignr_prtn_ovrid_flag FROM apps.benbv_elig_to_prte_rsn_v WHERE prtn_ovridbl_flag = 'Y';

Because business group security is applied inside the view, queries automatically return only rows permitted by the caller's security profile, making the view safe for delegated and multi-org reporting.