Search Results hr_s_user_rows_f




Overview
Explore in AI Chat

Overview

HR_S_USER_ROWS_F is a date-tracked (effective-dated) table in the PER – Human Resources product of Oracle E-Business Suite, owned by the HR schema. It forms part of the Payroll and HR "user tables" framework, a flexible construct that allows implementers and payroll administrators to define custom lookup values, ranges, and validation lists that drive fast formulas, element eligibility, and validation of descriptive flexfield and payroll input values. The "_F" suffix and the presence of EFFECTIVE_START_DATE and EFFECTIVE_END_DATE indicate that this is a date-effective (non-translated) table, typically paired with a "_F" base table and a "_TL" translation table where multilingual support is required.

Under the heuristic Data Vault classification derived from the foreign-key structure, this object is modeled as a standalone satellite-style entity. It carries descriptive, chronology-bound attributes (the row values themselves) attached to a parent business key represented by USER_TABLE_ID, which references PAY_USER_TABLES. In Data Vault terms it behaves as a satellite hanging off the PAY_USER_TABLES hub, capturing the changing set of valid rows for a given user table over time.

Key Information Stored

The table contains 16 documented columns. The most significant are outlined below.

  • USER_ROW_ID — The surrogate primary key that uniquely identifies each user-table row record.
  • USER_TABLE_ID — The business-key foreign key to PAY_USER_TABLES, linking each row back to the parent user table definition.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — The date-effective range that governs when the row value is valid, the defining characteristic of the "_F" date-tracked design.
  • ROW_LOW_RANGE_OR_NAME — The low-end value of a validation range, or the literal name/label of a discrete user-defined entry.
  • ROW_HIGH_RANGE — The high-end value of a validation range; together with the low range it defines an inclusive band.
  • DISPLAY_SEQUENCE — Controls the ordering in which rows are presented in list-of-values displays.
  • LEGISLATION_CODE / LEGISLATION_SUBGROUP — Restricts the applicability of the row to a specific country and legislative subgroup.
  • BUSINESS_GROUP_ID — The multi-tenant identifier partitioning data by enterprise business group.
  • OBJECT_VERSION_NUMBER — The optimistic-locking version stamp used by the OAF/Forms framework.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard audit columns.

No unique indexes beyond the primary key are documented in the metadata; USER_TABLE_ID combined with the effective-date range and legislation fields effectively constitutes the natural business key.

Common Use Cases and Queries

Typical scenarios include validating payroll input values, driving element eligibility, and reporting on the configured list of user-table entries. A common query retrieves the current valid rows for a given user table:

  • Current rows: SELECT ROW_LOW_RANGE_OR_NAME, ROW_HIGH_RANGE, DISPLAY_SEQUENCE FROM HR.HR_S_USER_ROWS_F WHERE USER_TABLE_ID = :id AND SYSDATE BETWEEN EFFECTIVE_START_DATE AND EFFECTIVE_END_DATE ORDER BY DISPLAY_SEQUENCE;
  • Effective-dated history: filter on a specific date to reconstruct the value set that was active at that point, useful for retroactive payroll audits.
  • Legislation-scoped LOVs: constrain by LEGISLATION_CODE and LEGISLATION_SUBGROUP to present only locally relevant values.

Related Objects

The most significant related objects and their join columns are:

  • PAY_USER_TABLES — Parent definition of the user table; joined on USER_TABLE_ID = PAY_USER_TABLES.USER_TABLE_ID.
  • HR_S_USER_ROWS_TL — The translated-language counterpart, joined by USER_ROW_ID, supplying row descriptions in multiple languages.
  • PAY_USER_COLUMNS / PAY_USER_ROWS — Related user-table configuration tables sharing the USER_TABLE_ID business key.
  • Payroll element and validation formulas — Fast formulas and validation logic that reference user tables and resolve values from these rows at runtime.
  • Descriptive flexfield / value-set definitions — Frequently sourced from user-table rows for validation.