Results for “benbv_elig_hrly_slrd_prte_v”

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

Overview

BENBV_ELIG_HRLY_SLRD_PRTE_V is a read-only Oracle EBS view owned by the APPS schema within the Advanced Benefits (BEN) product family. Its purpose is to identify which hourly or salaried employment criteria are included in, or excluded from, a given eligibility profile. In Oracle Advanced Benefits, eligibility profiles act as the reusable rule containers that determine whether a person or assignment qualifies for a program, plan type, or plan. The hourly/salaried criterion is one such rule dimension: it allows an eligibility profile to target workers based on whether they are classified as hourly or salaried employees. This view exposes that criterion configuration in a flattened, reporting-friendly format.

The BENBV_ naming convention indicates a business view, a class of views in the BEN module designed primarily for inquiry, extracts, and integration rather than transaction processing. The view is declared WITH READ ONLY and status VALID, so it is safe for concurrent querying and can be consumed by BI Publisher reports, Oracle Discoverer workbooks, custom concurrent programs, and third-party integration extracts without risk of modifying underlying data.

Underlying Base Objects

The view is defined over two documented base objects. The first is BEN_ELIG_HRLY_SLRD_PRTE_F, the underlying Advanced Benefits table that stores the hourly/salaried eligibility criterion records. This is a date-tracked (effective-dated) table, referenced in the ETRM metadata as a synonym. It holds one row per defined hourly/salaried criterion line attached to an eligibility profile, preserved with effective start and end dates to support historical accuracy.

The second base object is the HR_BIS package, a shared HRMS business intelligence utility package. The view invokes it in two ways: through the function HR_BIS.BIS_DECODE_LOOKUP, which resolves coded values into their meaningful lookup meanings, and through HR_BIS.GET_SEC_PROFILE_BG_ID, which applies the session's security profile to restrict results to the appropriate business group. The WHERE clause filters BEN_ELIG_HRLY_SLRD_PRTE_F on BUSINESS_GROUP_ID using NVL against this security profile value, enforcing multi-tenant data isolation at the database layer.

Key Columns

• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — The date-tracked validity range of the criterion row, critical for as-of-date reporting.
• ORDR_NUM — The processing or display order of the criterion within the eligibility profile.
• HRLY_SLRD_CD — The stored code indicating the hourly/salaried classification used by the rule.
• HRLY_SLRD_CD_M — The decoded, user-readable meaning of HRLY_SLRD_CD, resolved via the HOURLY_SALARIED_CODE lookup.
• EXCLD_FLAG — Flag indicating whether the criterion is included in or excluded from the profile.
• EXCLD_FLAG_M — The decoded YES/NO meaning of EXCLD_FLAG.
• ELIG_HRLY_SLRD_PRTE_ID — Primary identifier of the underlying criterion record.
• ELIGY_PRFL_ID — Foreign key to the parent eligibility profile.
• BUSINESS_GROUP_ID — The business group that owns the record, central to security filtering.
• WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE) — Standard audit information.
• _DF:EHS — Placeholder token exposing the descriptive flexfield context for the criterion.

Common Use Cases and Queries

Typical uses include auditing which profiles restrict eligibility by employment type, feeding eligibility extracts for benefits processing, and troubleshooting why an employee was excluded from a plan. The following query lists all hourly/salaried criteria for a specific eligibility profile:

SELECT eligy_prfl_id, ordr_num, hrly_slrd_cd_m, excld_flag_m,
       effective_start_date, effective_end_date
 FROM apps.benbv_elig_hrly_slrd_prte_v
 WHERE eligy_prfl_id = :p_profile_id
 AND SYSDATE BETWEEN effective_start_date AND effective_end_date
 ORDER BY ordr_num;

A second scenario reports all profiles that exclude salaried workers:

SELECT eligy_prfl_id, hrly_slrd_cd_m, effective_start_date
 FROM apps.benbv_elig_hrly_slrd_prte_v
 WHERE excld_flag = 'Y'
 AND hrly_slrd_cd = 'S';

Because the view is read-only and security-aware, it is well suited to ad hoc analysis. Analysts should always apply effective-date predicates to avoid returning multiple historical versions of the same criterion, and should join ELIGY_PRFL_ID back to the eligibility profile tables to obtain profile names and context.