Results for “elig_dpnt_cvrd_pgm_flag”

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

Overview

BENBV_ELIGY_PRFL_V is a business view owned by the APPS schema within the Oracle Advanced Benefits (BEN) module. It is defined over the eligibility profile entity, which encapsulates the set of eligibility factors or rules that a person must collectively satisfy in order to qualify for a benefit program, plan, or option. In Oracle EBS 12.1.1 and 12.2.2, this view serves as the primary reporting and integration surface for eligibility profile definitions, presenting the profile name and description alongside the full complement of eligibility rule indicators and their decoded display values.

The view carries the "BV" (business view) prefix characteristic of Oracle's multi-lingual and business-layer views, and its status is documented as VALID in the ETRM 12.2.2 metadata. Its central value to implementers is that it translates the internal code values stored on the profile record into user-facing meanings through the HR_BIS package, which is especially important because the majority of the profile's classification and eligibility flags are stored as Yes/No indicators.

Underlying Base Objects

The view is defined over two documented referenced objects:

• BEN_ELIGY_PRFL_F (referenced via synonym) — the base table holding the eligibility profile definitions, including effective dating, name, description, and all rule flags and code columns.
• HR_BIS (package) — the HR business intelligence/decoding package referenced through its BIS_DECODE_LOOKUP function, which converts stored lookup codes into their translated display meanings.

The view inherits the standard effective-dating model of the BEN product family via EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, which are passed through directly from BEN_ELIGY_PRFL_F. A descriptive flexfield placeholder, '_DF:BEN:BEN_ELIGY_PRFL_F:ELP', is exposed so that reporting tools can resolve the descriptive flexfield context of the underlying profile record.

Key Columns

The projection consists of paired columns: the raw stored code and its decoded value produced by HR_BIS.BIS_DECODE_LOOKUP.

• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — date-effective range of the profile definition.
• NAME / DESCRIPTION — profile identification text.
• STAT_CD — status code, decoded against the BEN_STAT lookup.
• ASG_TYP_CD — assignment type, decoded against BEN_ASGN_TYP.
• ASMT_TO_USE_CD — assessment to use, decoded against BEN_ASMT_TO_USE.
• BNFT_CAGR_PRTN_CD — benefits coverage group participation, decoded against BEN_BNFT_CAGR_PRTN.
• Yes/No rule flags — ELIG_ENRLD_PLIP_FLAG, ELIG_CBR_QUALD_BNF_FLAG, ELIG_ENRLD_PTIP_FLAG, ELIG_DPNT_CVRD_PLIP_FLAG, ELIG_DPNT_CVRD_PTIP_FLAG, ELIG_DPNT_CVRD_PGM_FLAG, ELIG_JOB_FLAG, ELIG_HRLY_SLRD_FLAG, ELIG_PSTL_CD_FLAG, ELIG_LBR_MMBR_FLAG, ELIG_LGL_ENTY_FLAG, ELIG_BENFTS_GRP_FLAG, ELIG_WK_LOC_FLAG, ELIG_BRGNG_UNIT_FLAG, ELIG_AGE_FLAG, among others. Each is decoded against the YES_NO lookup, which is the lookup the "yes_no" search term corresponds to.

Each flag indicates whether the corresponding criterion (job, hourly/salaried status, postal code, bargaining unit, benefits group, work location, age, and so on) is an active factor in the eligibility determination.

Common Use Cases and Queries

Typical applications include reporting which eligibility factors are active on a given profile, auditing profiles across a date range, and feeding downstream benefit enrollment reconciliation extracts.

SELECT name
     , description
     , bis_decode_lookup_col
  FROM apps.benbv_eligy_prfl_v
 WHERE effective_start_date <= SYSDATE
   AND effective_end_date   >  SYSDATE;

To isolate profiles driven by age:

SELECT name
     , elig_age_flag
  FROM apps.benbv_eligy_prfl_v
 WHERE elig_age_flag = 'Y';

Because each flag is paired with a decoded value, consumers can either filter on the stored code (for performance and consistency) or present the decoded value to end users. Implementers should join to BEN_ELIGY_PRFL_F on the surrogate key when additional undecoded attributes are required.