Results for “tx_typ”

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

Overview

BEN_ENRT_LOV_INFO_V is a presentation-layer view owned by the APPS schema in Oracle Advanced Benefits (BEN). It is a denormalized, read-only construct that assembles the data required to populate List of Values (LOV) windows and self-service enrollment pages within the Oracle E-Business Suite, particularly the participant-facing benefits enrollment flows and the plan/option selection screens used by administrators. The view combines eligibility records, enrollment benefit assignments, plan and option definitions, and rate/valuation attributes into a single flat row set, allowing the forms and OAF pages to render benefit choices without issuing multiple joins against the base configuration tables.

The view is engineered around the concept of a potential election — a plan or option for which a person may enroll — and enriches that potential election with the numeric and coverage characteristics that the enrollment UI must display or validate. Status is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2, and the view follows the standard ETRM (E-Business Tables and Views Reference Manual) documentation conventions for the BEN product family.

Underlying Base Objects

The documented base objects referenced by BEN_ENRT_LOV_INFO_V are: BEN_ELIG_PER_ELCTBL_CHC, BEN_ENRT_BNFT, BEN_ENRT_RT, BEN_LER_F, BEN_OIPL_F, BEN_OPT_F, BEN_PER_IN_LER, BEN_PL_F, BEN_PL_TYP_F, FND_SESSIONS, HR_LOOKUPS, and the HR_API package. All table references are resolved through APPS synonyms.

• BEN_ELIG_PER_ELCTBL_CHC — supplies the eligibility record for each person's electable choice and carries the enrollment coverage start date code (ENRT_CVG_STRT_DT_CD) that maps to the user search term.
• BEN_ENRT_BNFT — provides enrollment benefit assignments and their valuation attributes, aliased as B in the view text.
• BEN_ENRT_RT — contributes enrollment-specific rate rows (RB1), contrasted with plan-level rate rows (R1) through DECODE logic keyed on ENRT_BNFT_ID.
• BEN_LER_F, BEN_OIPL_F, BEN_PL_F, BEN_OPT_F, BEN_PL_TYP_F — the plan, option, plan-in-program, and plan-type definitions that supply ordering numbers, identifiers, and descriptive names.
• BEN_PER_IN_LER — links the person to their life event and eligibility context.
• HR_LOOKUPS and FND_SESSIONS — resolve lookup meanings (for units of measure, coverage start date, transaction type, and compensation reference period) and session context.
• HR_API — the HR utility package invoked for derived person or date attributes.

Key Columns

• PL_TYP_ID, PL_ID, OPT_ID, OIPL_ID — identifiers for the plan type, plan, option, and option-in-plan combination, forming the primary LOV key.
• PL_TYP_NAME, PL_OPT_NAME — concatenated display names for the LOV.
• BNFT_VAL, MN_VAL, MX_VAL, INCRMT_VAL, BNFT_NNMNTRY_UOM — benefit amount, minimum, maximum, increment, and monetary unit of measure.
• ANN_VAL, CMCD_VAL, PRE_TAX_VAL — annual, per-compensation-period, and pre-tax values, resolved from either enrollment rate or plan rate rows.
• ENRT_CVG_STRT_DT_CD and ENRT_CVG_STRT_DT_MEANING — the coverage start date code from BEN_ELIG_PER_ELCTBL_CHC and its HR_LOOKUPS meaning; this column is the direct object of the user's search.
• RT_STRT_DT, RT_NNMNTRY_UOM, RT_NNMNTRY_UOM_MEANING — rate effective start date and rate monetary unit.
• CRNTLY_ENRD_FLAG — derived flag indicating whether the person is currently enrolled, based on EPE.CRNTLY_ENRD_FLAG and the enrollment benefit context.
• TX_TYP_CD, CMCD_REF_PERD — tax type code and compensation period reference.

Common Use Cases and Queries

Typical consumers are the Benefits enrollment OAF pages and the Plan/Option LOV in the administrative Benefits forms, which require both the electable choice and its coverage start date behavior. A representative query that emphasizes the coverage start date dimension is:

• SELECT pl_typ_name, pl_opt_name, bnft_val, bnft_nnmntry_uom_meaning, enrt_cvg_strt_dt_cd, enrt_cvg_strt_dt_meaning FROM apps.ben_enrt_lov_info_v WHERE pl_id = :p_plan_id;
• SELECT pl_id, opt_id, pl_opt_name, ann_val, pre_tax_val FROM apps.ben_enrt_lov_info_v WHERE crntly_enrd_flag = 'Y';
• SELECT pl_opt_name, mx_val, mn_val, incrmt_val FROM apps.ben_enrt_lov_info_v WHERE pl_typ_id = :p_pl_typ_id ORDER BY pl_ordr_num;

Because the view is a non-key-preserved join across many BEN tables, it should be queried with selective predicates on PL_ID, OPT_ID, or PL_TYP_ID. It is intended as a read-only LOV source and should not be used for DML.