Search Results pay_user_rows




Overview
Explore in AI Chat

Overview

PAY_USER_ROWS is a date-effective (date-tracked) view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PAY (Payroll) product family. It presents the currently effective rows of the underlying user-defined table row definitions used by Oracle Payroll and Oracle Human Resources for configurable lookups, validations, and legislative data structures. The object is documented in ETRM for both 12.1.1 and 12.2.2 with a status of VALID.

The view derives its name from the fact that it exposes "user rows" — the individual range or name based entries that belong to a user-defined table. A user table (PAY_USER_TABLES) defines a lookup structure; its rows (PAY_USER_ROWS) supply the discrete values, ranges, or names that populate that structure for a given business group and legislation. Because the definition of these rows can change over time, the underlying data is stored with effective start and end dates, and the view filters that data to return only the row version in effect for the current session's effective date.

From a reporting and integration perspective, PAY_USER_ROWS provides a convenient, session-aware read interface. Rather than requiring a developer to manually join to the base table and apply date-effective filtering logic, the view encapsulates that logic centrally, ensuring consistent point-in-time resolution across concurrent requests, forms, and custom SQL.

Underlying Base Objects

The view is defined over two documented synonyms:

  • PAY_USER_ROWS_F — the "_F" (date-effective) base table that physically stores the user row records, including their effective start and end dates, business group, legislation, and user table membership.
  • FND_SESSIONS — the Applications session table, used here to resolve the effective date for the active session.

The view text selects all columns from PAY_USER_ROWS_F with a WHERE clause that restricts rows to those whose EFFECTIVE_START_DATE is on or before, and whose EFFECTIVE_END_DATE is on or after, the effective date recorded for the current session. The session effective date is obtained by subquerying FND_SESSIONS using USERENV('SESSIONID') to identify the active session. This is the standard Oracle EBS date-effective (datetrack) view pattern, pairing a "_F" table with a session-driven date filter.

Key Columns

Common Use Cases and Queries

Typical uses include resolving valid values for a user-defined table during payroll processing, building reports of lookup entries, and validating ranges in custom fast formulas or interfaces.

Query all effective rows for a business group and legislation:

  • SELECT user_row_id, user_table_id, row_low_range_or_name, row_high_range, display_sequence FROM pay_user_rows WHERE business_group_id = :p_bg_id AND legislation_code = :p_leg ORDER BY display_sequence;

Join to the parent user table to list rows with their table name:

  • SELECT r.user_row_id, t.user_table_name, r.row_low_range_or_name FROM pay_user_rows r, pay_user_tables t WHERE r.user_table_id = t.user_table_id;

Because the view already enforces session-level date effectiveness, it is the preferred access path for any custom SQL that must reflect the same point-in-time view of user rows that the application itself uses.