Results for “tx_typ_cd”

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

Overview

BEN_ELCTBL_LOV_INFO_V is a database view owned by the APPS schema within the Oracle E-Business Suite Advanced Benefits (BEN) module. Its name reflects its purpose: it supplies the information required to drive a List of Values (LOV) for electable benefit choices presented to participants during enrollment. The view flattens and enriches data drawn from eligibility, plan, option, and enrollment rate structures so that forms and self-service pages can present a single, human-readable row per electable option.

The view exposes ordering numbers, plan and option identifiers, descriptive names, benefit values, minimum and maximum election amounts, increments, annual and per-paycheck monetary limits, tax treatment, and coverage start-date logic. It is a read-only reporting and integration object; the underlying business logic supports the Benefits enrollment flows rather than performing transactional writes itself. Because it consolidates descriptive flexfield-independent lookups (via HR_LOOKUPS) and session context (via FND_SESSIONS) alongside core benefit tables, it is commonly used in custom reports, extracts, and interfaces that must mirror what a participant is eligible to elect.

Underlying Base Objects

According to the documented 12.2.2 metadata, the view is defined over the following base objects, all referenced through APPS synonyms:

• BEN_ELIG_PER_ELCTBL_CHC — the eligibility-to-electable-choice link, the central driver of the LOV rows.
• BEN_OIPL_F — the option-in-plan relationship, supplying plan type, plan, and option ordering.
• BEN_PL_F, BEN_PL_TYP_F, BEN_OPT_F — plan, plan type, and option definition tables supplying descriptive names.
• BEN_ENRT_BNFT and BEN_ENRT_RT — enrollment benefit and rate records that override or supplement default values.
• BEN_PER_IN_LER and BEN_LER_F — person-in-life-event-reason and life event reason data used in the DECODE logic that selects enrolled versus default amounts.
• BEN_PRTT_ENRT_RSLT_F — participant enrollment results, referenced for currently-enrolled flags and effective values.
• HR_LOOKUPS — a view providing lookup meanings such as non-monetary unit, tax type, and reference period descriptions.
• HR_API — a package used within the view logic, and FND_SESSIONS — supplying application session context.

The view therefore sits on top of the core Benefits configuration and enrollment model, joining eligibility, plan/option setup, and rate definitions into a single denormalized structure.

Key Columns

• PL_TYP_ID, PL_ID, OPT_ID, OIPL_ID — identifiers for the plan type, plan, option, and option-in-plan relationship.
• PL_TYP_NAME, PL_OPT_NAME — concatenated display names used directly in the LOV.
• BNFT_VAL, MN_VAL, MX_VAL, INCRMT_VAL — the benefit value, minimum, maximum, and increment, resolved through NVL against default values.
• BNFT_NNMNTRY_UOM / _MEANING — the non-monetary unit of measure and its lookup meaning.
• ANN_VAL, ANN_MN_VAL, ANN_MX_VAL — annualized amounts and limits, chosen conditionally on whether an enrollment benefit record exists (DECODE on ENRT_BNFT_ID).
• CMCD_VAL, CMCD_MN_VAL, CMCD_MX_VAL, CMCD_REF_PERD — communicated values, limits, and reference period.
• PRE_TAX_VAL, TX_TYP_CD, TX_TYP — pre-tax value and tax treatment code/meaning.
• ENRT_CVG_STRT_DT_CD / _MEANING — coverage start date rule and its description.
• RT_STRT_DT, RT_NNMNTRY_UOM, RT_NNMNTRY_UOM_MEANING — rate start date and rate non-monetary unit.
• CRNTLY_ENRD_FLAG — indicates whether the participant is currently enrolled in the option.
• PGM_ID, PTIP_ID, PLIP_ID — program and plan-in-program identifiers for context.

Common Use Cases and Queries

The view is typically queried to populate or validate enrollment LOVs, to build eligibility extracts, and to reconcile electable options against configured plans and rates. A representative query follows:

• SELECT pl_typ_name, pl_opt_name, bnft_val, mn_val, mx_val, incrmt_val, crntly_enrd_flag FROM apps.ben_elctbl_lov_info_v WHERE pgm_id = :p_program_id ORDER BY ptip_ordr_num, plip_ordr_num, pl_ordr_num, oipl_ordr_num;
• SELECT pl_id, pl_opt_name, ann_val, ann_mn_val, ann_mx_val, tx_typ FROM apps.ben_elctbl_lov_info_v WHERE crntly_enrd_flag = 'Y';
• SELECT DISTINCT pl_typ_name FROM apps.ben_elctbl_lov_info_v;

Because the ordering columns (PTIP_ORDR_NUM, PLIP_ORDR_NUM, PL_ORDR_NUM, OIPL_ORDR_NUM) are exposed, the view is well suited to reproducing the exact sequence in which options appear in native Benefits LOVs.