Results for “elig_hrly_slrd_prte_id”

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

Overview

BEN_ELIG_HRLY_SLRD_PRTE_D is an APPS-owned reporting view within the Oracle Advanced Benefits (BEN) module, delivered under the E-Business Suite 12.1.1 and 12.2.2 code lines. The object is a denormalized, "D"-suffixed view: the suffix convention distinguishes it from the base "_F" table (BEN_ELIG_HRLY_SLRD_PRTE_F), which stores the raw eligibility rule rows, while the view resolves foreign-key identifiers into human-readable meanings for display and extraction. The subject matter is the hourly salaried prerequisite — the eligibility configuration that governs whether an employee classified as hourly or salaried qualifies for a given benefit program or plan.

In ETRM the object carries the status VALID with the description "- Retrofitted," indicating that the view was re-created or re-pointed as part of a product retrofit rather than authored as net-new functionality. Functionally, it presents a flat projection of benefit eligibility prerequisite rows joined to lookup translations, eligibility profile names, and audit columns, making it suitable for concurrent-program extracts, Oracle Discoverer/BIP data models, and ad hoc operational reporting.

Underlying Base Objects

The documented referenced base objects are:

• BEN_ELIG_HRLY_SLRD_PRTE_F (SYNONYM) — the primary driver table, holding one row per hourly/salaried eligibility prerequisite definition with surrogate key ELIG_HRLY_SLRD_PRTE_ID.
• BEN_ELIGY_PRFL_F (SYNONYM) — the eligibility profile header, joined on ELIGY_PRFL_ID to supply the profile NAME.
• HR_LOOKUPS (VIEW) — the Oracle HR lookup view, joined twice: once against LOOKUP_TYPE = 'PAY_BASIS' for HRLY_SLRD_CD, and once against LOOKUP_TYPE = 'YES_NO' for EXCLD_FLAG.
• FND_USER (SYNONYM) — the application user table, joined on LAST_UPDATED_BY for the audit trail.
• HR_API (PACKAGE) — referenced for the date-effective/row-id handling that underpins the view's ROW_ID exposure.

All joins to FND_USER, BEN_ELIGY_PRFL_F, and both HR_LOOKUPS instances are outer joins (shown with the Oracle (+) operator), so prerequisite rows are returned even when the lookup or profile name is unresolved. This defensive design prevents configuration rows from disappearing in reports due to incomplete lookup setup.

Key Columns

• ROW_ID — the physical ROWID of the underlying BEN_ELIG_HRLY_SLRD_PRTE_F row; the unique handle for the record.
• ELIG_HRLY_SLRD_PRTE_ID — the surrogate primary key for the prerequisite definition.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-effective range controlling when the prerequisite applies. Because the view itself does not apply a date filter, callers must supply their own effective-date predicate.
• ORDR_NUM — the evaluation sequence in which this prerequisite is assessed relative to others in the same eligibility profile.
• HRLY_SLRD_MEANING — the decoded PAY_BASIS lookup meaning, i.e., the hourly/salaried value the rule tests against. This is the column most often referenced when users search on "hrly_slrd_cd."
• EXCLD_MEANING — the decoded YES_NO lookup meaning for EXCLD_FLAG, indicating whether the prerequisite is treated as an inclusion or exclusion criterion.
• ELIGY_PRFL_NAME — the descriptive name of the owning eligibility profile.
• LAST_UPDATE_DATE / LAST_UPDATED_BY — the standard audit pair for change tracking and support diagnostics.

Common Use Cases and Queries

The view is typically used to audit benefit eligibility configuration, to verify which profiles reference hourly or salaried prerequisites, and to feed downstream extracts. A representative query filters to currently effective rows:

• SELECT elig_hrly_slrd_prte_id, eligy_prfl_name, hrly_slrd_meaning, excld_meaning, ordr_num FROM apps.ben_elig_hrly_slrd_prte_d WHERE hrly_slrd_meaning IS NOT NULL AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date ORDER BY eligy_prfl_name, ordr_num;
• To identify profiles that exclude salaried staff: SELECT eligy_prfl_name, hrly_slrd_meaning, excld_meaning FROM apps.ben_elig_hrly_slrd_prte_d WHERE hrly_slrd_meaning = 'Salaried' AND excld_meaning = 'Yes';
• For a change audit: SELECT elig_hrly_slrd_prte_id, last_updated_by, last_update_date FROM apps.ben_elig_hrly_slrd_prte_d WHERE last_update_date >= :p_since;

Because the view exposes ROW_ID rather than a full date-effective stack, consumers should not treat it as an HRMS date-tracked entity; joins back to the base table or to HR_API-based queries are required when effective-dated history rather than a point-in-time snapshot is needed.