Results for “hrly_slrd_meaning”

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

Overview

BEN_HRLY_SLRD_RT_D is a database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the BEN (Advanced Benefits) product. Its ETRM status is VALID, and the object is described as "Retrofitted," indicating that it was re-created or re-pointed to conform with a later EBS data model iteration. The view exposes configuration data for hourly salaried rates, a compensation attribute used in benefits plan and rate processing. It serves as a reporting and integration layer over the transactional base table BEN_HRLY_SLRD_RT_F, denormalizing foreign-key identifiers into user-readable names and meanings so that implementers, benefit administrators, and downstream extracts can query meaningful values without joining several lookup and profile tables manually. In EBS 12.1.1 and 12.2.2 the view is read-only by design; it is not an entity for DML and should never be used as a target for inserts or updates.

Underlying Base Objects

The view is defined over several documented objects. The primary source is the synonym BEN_HRLY_SLRD_RT_F, the effective-dated base ("_F") table holding hourly salaried rate rows. It is joined to BEN_VRBL_RT_PRFL_F, the effective-dated variable rate profile table, with the join predicated on the base row's effective start date falling between the profile's effective start and end dates (an outer join, so rate rows without a profile are retained). FND_USER is outer-joined on LAST_UPDATED_BY to resolve the application user who last modified the row. Two instances of the HR_LOOKUPS view are outer-joined: one on HRLY_SLRD_CD and one on EXCLD_FLAG, with lookup types of blank and YES_NO respectively, to translate coded values into their displayed meanings. The ETRM metadata also lists HR_API (PACKAGE) among the referenced base objects, reflecting the benefits API dependency chain associated with this functional area.

Key Columns

• ROW_ID — the base table's ROWID, providing a unique physical row identifier.
• HRLY_SLRD_RT_ID — the surrogate primary key for the hourly salaried rate row.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-effective range controlling which row is valid on a given date.
• VRBL_RT_PRFL_NAME — the name of the related variable rate profile, resolved from BEN_VRBL_RT_PRFL_F.
• HRLY_SLRD_MEANING — the display meaning of the HRLY_SLRD_CD lookup value; this is the column most often sought when users search for "hrly_slrd" terminology.
• EXCLD_MEANING — the YES/NO meaning of the EXCLD_FLAG exclusion indicator.
• ORDR_NUM — the ordering sequence used when displaying or processing rate rows.
• LAST_UPDATE_DATE / LAST_UPDATED_BY — audit columns; the latter holds the numeric user ID, while FND_USER is available for name resolution.

Common Use Cases and Queries

Typical uses include benefits configuration validation, audit reporting, and data extracts feeding interfaces or reconciliation reports. A frequently used pattern retrieves all current and historical hourly salaried rate definitions with their resolved lookup meanings:

• SELECT hrly_slrd_rt_id, effective_start_date, effective_end_date, vrbl_rt_prfl_name, hrly_slrd_meaning, excld_meaning, ordr_num FROM apps.ben_hrly_slrd_rt_d ORDER BY vrbl_rt_prfl_name, ordr_num;
• Point-in-time evaluation: add WHERE :p_effective_date BETWEEN effective_start_date AND effective_end_date to return only rows valid on a given date.
• Audit extraction: select last_updated_by, last_update_date filtered by a date window to identify recent configuration changes.
• Exclusion analysis: filter WHERE excld_meaning = 'Yes' to isolate rate rows flagged as excluded.

Because the joins to BEN_VRBL_RT_PRFL_F, FND_USER, and HR_LOOKUPS are all outer joins, the view preserves base rate rows even when related profile or lookup data is absent, making it safe for completeness-oriented reporting. Query performance should be assessed against BEN_HRLY_SLRD_RT_F, which typically carries the driving index on HRLY_SLRD_RT_ID and the effective dates.