Search Results hourly_salaried_code




Overview
Explore in AI Chat

Overview

APPS.BENBV_ELIG_HRLY_SLRD_PRTE_V is a reporting view within the Oracle E-Business Suite Advanced Benefits (BEN) module. It exposes configuration data relating to hourly versus salaried eligibility rules used when evaluating whether an employee qualifies for a given benefits program or plan. In EBS 12.1.1 and 12.2.2 this view operates as a read-only projection over the eligibility profile rule table BEN_ELIG_HRLY_SLRD_PRTE_F.

The view is primarily intended for reporting, integration, and data extraction scenarios where consumers need a security-filtered, decoded presentation of hourly/salaried eligibility criteria. Notably the definition carries the WITH READ ONLY clause, confirming that it cannot be used for DML. Users searching for the term hourly_salaried_code will recognize that this view is the standard access path to the HRLY_SLRD_CD column and its decoded lookup description.

Underlying Base Objects

The view is defined over the following documented base objects:

  • BEN_ELIG_HRLY_SLRD_PRTE_F (referenced via synonym) — the eligibility profile rule table that stores the actual hourly/salaried inclusion and exclusion criteria.
  • HR_BIS (package) — a benefits business intelligence utility package supplying the BIS_DECODE_LOOKUP function and the security profile accessor GET_SEC_PROFILE_BG_ID.

Aliased as EHS, the base table supplies every data column and the effective-dating pairs. The HR_BIS package contributes only computed values: lookup decoding and the security predicate. The WHERE clause restricts results to the business group returned by HR_BIS.GET_SEC_PROFILE_BG_ID, falling back to the row-level BUSINESS_GROUP_ID when no security profile value exists. This embeds multi-tenant and responsibility-level security into the view itself.

Key Columns

  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-effectivity range governing validity of the rule.
  • ORDR_NUM — ordering sequence applied when multiple criteria are evaluated.
  • HRLY_SLRD_CD — the raw code from the HOURLY_SALARIED_CODE lookup, typically indicating hourly or salaried classification.
  • BIS_DECODE_LOOKUP('HOURLY_SALARIED_CODE', HRLY_SLRD_CD) — the translated, user-facing meaning of the hourly/salaried code.
  • EXCLD_FLAG — indicates whether the criterion is inclusionary or exclusionary.
  • BIS_DECODE_LOOKUP('YES_NO', EXCLD_FLAG) — the decoded Yes/No representation of the exclude flag.
  • ELIG_HRLY_SLRD_PRTE_ID — primary identifier for the eligibility rule row.
  • ELIGY_PRFL_ID — foreign key to the parent eligibility profile.
  • BUSINESS_GROUP_ID — the business group owning the record.
  • WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE for audit traceability.
  • Descriptive flexfield token — a literal string '_DF:BEN:BEN_ELIG_HRLY_SLRD_PRTE_F:EHS' used by Oracle's framework to render DFF segments.

Common Use Cases and Queries

Typical scenarios include auditing which eligibility profiles restrict or include hourly versus salaried workers, validating configuration before a benefits open enrollment, and feeding downstream warehouse or integration processes.

Sample query listing decoded hourly/salaried rules for a profile:

  • SELECT eligy_prfl_id, hrly_slrd_cd, bis_decode_lookup('HOURLY_SALARIED_CODE',hrly_slrd_cd) decoded, excls, effective_start_date FROM apps.benbv_elig_hrly_slrd_prte_v WHERE eligy_prfl_id = :p_profile_id;

Another common pattern joins the view to BEN_ELIGY_PRFL to report profile names alongside the hourly/salaried criterion, filtered by excl_flag = 'Y' to isolate exclusion rules. Because the view already applies business group security through HR_BIS.GET_SEC_PROFILE_BG_ID, callers do not need to add their own BUSINESS_GROUP_ID predicate, though doing so is harmless and can improve plan stability.