Search Results pay_user_rows_f




Overview
Explore in AI Chat

Overview

PAY_USER_ROWS_F is a payroll configuration table in the Oracle E-Business Suite HR schema that stores the row definitions for user-defined tables. User-defined tables in Oracle Payroll (often called "user tables" or "quickpay" / "formula" lookups) allow implementers to define custom sets of rows that payroll formulas and elements can reference at runtime — for example tax brackets, age bands, service tiers, or region-specific rates. Each record in PAY_USER_ROWS_F defines a single row within one of those user tables, including the row's identifying name or low range value, an optional high range value, display sequencing, and legislation context.

The table is date-tracked via EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, reflecting the standard Oracle HRMS datetrack pattern. Under a heuristic Data Vault classification, it leans toward satellite: it is keyed on a surrogate identifier (USER_ROW_ID) plus datetrack dates, and it carries descriptive attributes about a parent entity (PAY_USER_TABLES) rather than resolving many-to-many relationships itself.

Key Information Stored

The primary key, PAY_USER_ROWS_F_PK, is composed of USER_ROW_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE; the documented unique index also includes ZD_EDITION_NAME, supporting edition-based redefinition in 12.2.x. Key columns include:

Common Use Cases and Queries

The most common requirement is resolving the rows belonging to a named user table so they can be inspected, migrated, or validated against formulas. A typical query joins the parent table:

  • Listing rows for a specific user table: 
    SELECT r.row_low_range_or_name, r.row_high_range, r.display_sequence
FROM   pay_user_rows_f r, pay_user_tables t
WHERE  r.user_table_id = t.user_table_id
AND    t.user_table_name = :p_name
AND    TRUNC(SYSDATE) BETWEEN r.effective_start_date AND r.effective_end_date;
  • Date-track auditing: identifying which rows were valid on a given payroll run date.
  • Legislation filtering: restricting results by LEGISLATION_CODE for a given country's payroll.
  • Migration/reporting extracts: comparing row definitions between environments.

Because the table is datetracked, all reporting queries should constrain on the effective dates to avoid returning historical or future-dated definitions.

Related Objects

  • PAY_USER_TABLES — parent table joined via USER_TABLE_ID; defines the user table itself.
  • PAY_USER_COLUMNS_F — column definitions for the same user tables, joined indirectly through USER_TABLE_ID.
  • PAY_USER_ROWS_F_PK — the primary key index enforcing uniqueness across USER_ROW_ID and datetrack dates.
  • PAY_FORMULA_RESULTS_F / FF_FORMULAS_F — formulas frequently reference user table rows by name at runtime.
  • PAY_ELEMENT_TYPES_F — element definitions whose validation or processing logic consumes user table rows.

Together these objects form the user-defined table framework that supports configurable, legislation-sensitive payroll logic in Oracle EBS 12.1.1 and 12.2.2.