Results for “ben_elig_hrly_slrd_prte”

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

Overview

BEN_ELIG_HRLY_SLRD_PRTE is an Oracle EBS Advanced Benefits (BEN) view owned by the APPS schema. It presents a date-effective, security-filtered projection of the eligibility rule configuration that associates hourly salaried designations with an eligibility profile. In Oracle Advanced Benefits, eligibility profiles determine which participants qualify for a program, plan, or option. This view specifically supports eligibility criteria defined on an hourly/salaried (HRLY_SLRD) basis — that is, rules that include or exclude participants according to whether their assignment is classified as hourly or salaried. The view is described in the ETRM documentation as "Retrofitted," indicating that it was introduced or re-engineered as part of the product's directed-terminology retrofit, rather than being part of the original 11i data model.

For custom reporting and integrations, the view provides a convenient, session-aware read interface over the underlying Flexfield-enabled base table. Rather than querying the _F table directly and re-implementing the effective-date logic, developers and reporting tools can select from this view to obtain only the rows that are effective as of the current FND session date.

Underlying Base Objects

The view is defined over a single documented base object, BEN_ELIG_HRLY_SLRD_PRTE_F (referenced through a synonym), plus a correlated subquery against FND_SESSIONS. The definition joins each row of the base table to the current session by comparing the row's EFFECTIVE_START_DATE and EFFECTIVE_END_DATE against the SS.EFFECTIVE_DATE value returned from FND_SESSIONS for USERENV('SESSIONID'). The _F suffix confirms that the base table is date-tracked (datetracked) and holds the full historical record; the view filters this to the currently effective slice only. Because the view is a thin wrapper, it exposes essentially the same columns as the base table without transformation.

Key Columns

• ELIG_HRLY_SLRD_PRTE_ID — Primary surrogate key for the eligibility rule row.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Date-effective range of the record; used to restrict output to the active session date.
• ORDR_NUM — Ordering sequence number controlling the evaluation order of the rule.
• HRLY_SLRD_CD — The hourly/salaried classification code that the rule tests against.
• EXCLD_FLAG — Indicates whether the criterion is used to exclude (Y) or include (N) matching participants.
• ELIGY_PRFL_ID — Foreign key to the eligibility profile (BEN_ELIGY_PRFL) to which this criterion belongs.
• BUSINESS_GROUP_ID — Business group context for multi-tenant separation of configuration data.
• EHS_ATTRIBUTE_CATEGORY and EHS_ATTRIBUTE1–30 — Descriptive flexfield (DFF) context and segment columns for customer-defined extensions.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER — Standard WHO and optimistic-locking audit columns.

Common Use Cases and Queries

Typical uses include auditing which eligibility profiles carry hourly/salaried criteria, exporting criteria for data migration, and driving custom eligibility validation in integrations. Because the view automatically restricts to the session-effective rows, queries should not usually add their own date predicates.

List all hourly/salaried criteria for a profile:

SELECT elig_hrly_slrd_prte_id, ordr_num, hrly_slrd_cd, excld_flag, eligy_prfl_id
FROM ben_elig_hrly_slrd_prte
WHERE eligy_prfl_id = :p_profile_id
ORDER BY ordr_num;

Identify exclusion rules (flag set to exclude):

SELECT p.eligy_prfl_id, p.hrly_slrD_cd, p.excld_flag
FROM ben_elig_hrly_slrd_prte p
WHERE p.excld_flag = 'Y'
AND p.business_group_id = :p_bg_id;

Combine with the profile name for reporting:

SELECT p.elig_hrly_slrd_prte_id, ep.eligy_prfl_name, p.hrly_slrd_cd, p.excld_flag
FROM ben_elig_hrly_slrd_prte p, ben_eligy_prfl_f ep
WHERE p.eligy_prfl_id = ep.eligy_prfl_id
AND p.business_group_id = :p_bg_id;

Developers should note that the view returns only rows effective at the session date, so historical point-in-time analysis requires querying BEN_ELIG_HRLY_SLRD_PRTE_F directly with explicit date ranges.