Results for “ben_elctbl_chc_bnft_v”

36 results




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

Overview

The BEN_ELCTBL_CHC_BNFT_V view is a denormalized reporting and integration object within the Oracle E-Business Suite Advanced Benefits (BEN) module. It is owned by the APPS schema and carries a VALID status in both EBS 12.1.1 and 12.2.2. Its central purpose is to flatten the relationship between an eligible person's electable choice, the underlying plan and plan type, and the benefit enrollment details associated with that choice. Rather than requiring report authors to repeatedly join the same set of BEN configuration tables, the view presents plan names, plan type names, option names, order numbers, and enrollment attributes in a single row.

The view is heavily used wherever a user-facing list of enrollable benefits must be produced — self-service enrollment pages, benefits confirmation extracts, payroll feeds, and third-party benefits carrier interfaces. The presence of the synthetic column FAKE_CHOICE_ID (a DECODE that returns the eligibility record ID when no enrollment benefit exists) is a well-known characteristic that allows consumers to treat elective items and already-enrolled items uniformly. The user search term ptip_ordr_num maps directly to the PTIP_ORDR_NUM column, which exposes the display order number of the Plan Type in Plan (BEN_PTIP_F).

Underlying Base Objects

The view is defined over the following documented base objects, all referenced through APPS synonyms:

  • BEN_ELIG_PER_ELCTBL_CHC — the driver table aliased EPE, holding each eligible person's electable choice record.
  • BEN_ENRT_BNFT — aliased ENB, holding enrollment benefit values, minimums, maximums, increments, and defaults.
  • BEN_PER_IN_LER — aliased as the person-in-life-event-reason source that identifies participants.
  • BEN_PL_F, BEN_OIPL_F, BEN_PLIP_F, BEN_OPT_F, BEN_PL_TYP_F, BEN_PTIP_F — the plan, option-in-plan, plan-in-program, option, plan type, and plan-type-in-program configuration tables supplying names and order numbers.
  • FND_SESSIONS — the standard Oracle Applications session table, typically joined to scope rows to the current runtime session or business group context.

The joins are driven from EPE outward, which means the view returns every electable choice for a participant and augments it with descriptive plan metadata. Because the F tables (*_F) are date-effective, the view implicitly assumes the caller supplies an effective date or relies on the synonym's standard filtration.

Key Columns

Common Use Cases and Queries

Typical usage includes generating an enrollment worksheet per participant, sorting benefits by plan-type order, and extracting defaults for auto-enrollment processing. A representative query isolating the PTIP_ORDR_NUM column is:

  • SELECT per_in_ler_id, pl_and_opt_names, ptip_ordr_num, pl_ordr_num, opt_name, dflt_flag FROM apps.ben_elctbl_chc_bnft_v WHERE per_in_ler_id = :p_pil_id ORDER BY ptip_ordr_num, pl_ordr_num;
  • SELECT pl_name, pl_typ_name, val, mnmntry_uom FROM apps.ben_elctbl_chc_bnft_v WHERE elctbl_flag = 'Y' AND elig_flag = 'Y';
  • SELECT fake_choice_id, enrt_bnft_id, val FROM apps.ben_elctbl_chc_bnft_v WHERE auto_enrt_flag = 'Y';

Because the view references FND_SESSIONS and effective-dated configuration tables, callers should filter by the appropriate effective date and business group, and should expect the ordering columns (PTIP_ORDR_NUM foremost among them) to serve as the standard sort key for any benefits presentation list.