Search Results pay_user_rows_f_tl_pk




Overview
Explore in AI Chat

Overview

PAY_USER_ROWS_F_TL is the translation table for the Payroll module's user-defined row definitions. In Oracle EBS 12.1.1 and 12.2.2, it resides in the HR schema and stores the language-specific names of rows defined within user-defined tables (such as those used for element classification, balance feeds, or payroll reporting structures). The base, language-independent definition of each row is held in the corresponding base table, while PAY_USER_ROWS_F_TL carries the translated row names and description text keyed by language.

From a data modeling perspective, the object can be viewed as a translation satellite attached to the user-row entity. Its grain is one row per user row identifier per language, making it a descriptive attribute store rather than a transactional fact. The heuristic Data Vault classification for this table is "standalone," meaning no foreign key relationships were mined from the schema; however, functionally it depends on the base user-row definition through the USER_ROW_ID column.

Key Information Stored

The table contains ten documented columns. The most significant are:

  • USER_ROW_ID — Surrogate identifier of the parent user row; part of the primary key and the primary join key to the base table.
  • LANGUAGE — The NLS language code for the translation; part of the primary key.
  • SOURCE_LANG — The language in which the row was originally authored, used to track translation origin.
  • ROW_LOW_RANGE_OR_NAME — The translated name or low-range value displayed for the user row in the selected language.
  • ZD_EDITION_NAME — Editioning column inherited from the 12.2 Edition-Based Redefinition framework; part of the unique index.
  • LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN — Standard audit columns recording the last modification.
  • CREATED_BY / CREATION_DATE — Standard creation audit columns.

The primary key PAY_USER_ROWS_F_TL_PK is defined on (USER_ROW_ID, LANGUAGE). A unique index PAY_USER_ROWS_F_TL_PK (USER_ROW_ID, LANGUAGE, ZD_EDITION_NAME) serves as the business-key candidate, confirming that the effective business identity adds the edition dimension in 12.2.

Common Use Cases and Queries

Typical usage involves joining translations back to the base table to present localized row names in reports, concurrent programs, or custom forms. A common pattern filters on the session language:

  • Reporting user-defined rows in the user's language: SELECT t.row_low_range_or_name FROM pay_user_rows_f b, pay_user_rows_f_tl t WHERE b.user_row_id = t.user_row_id AND t.language = USERENV('LANG').
  • Auditing missing translations by comparing COUNT(DISTINCT LANGUAGE) against the expected language list from FND_LANGUAGES.
  • Data migration extracts that require both the base and translated names for a specific edition (ZD_EDITION_NAME).

Because the table is narrow and frequently queried with the base, indexing on USER_ROW_ID and LANGUAGE is critical for performance.

Related Objects

As a standalone satellite, no database-level foreign keys constrain PAY_USER_ROWS_F_TL, but effective joins to the base table are mandatory for meaningful data retrieval.