Search Results pay_input_values_f_tl




Overview
Explore in AI Chat

Overview

PAY_INPUT_VALUES_F_TL is the translation (MLS) table for payroll input value definitions in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It resides in the HR schema and belongs to the PAY (Payroll) product family. Every row stores the language-specific, translatable attributes of a single payroll input value, keyed by INPUT_VALUE_ID and LANGUAGE. The base, language-independent definition is held in PAY_INPUT_VALUES_F, while this table carries the user-facing NAME text per installed language, enabling multi-language payroll element configuration without duplicating structural attributes.

Under the heuristic Data Vault classification mined from the foreign-key structure, this object is classified as standalone. In modeling terms, it is therefore best treated as a standalone descriptive reference rather than as a hub, link, or satellite in a formal Data Vault model, because the FK mining did not surface dependencies that would place it in a dependent relationship.

Key Information Stored

The documented physical schema contains 10 columns: INPUT_VALUE_ID, NAME, LANGUAGE, SOURCE_LANG, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, and ZD_EDITION_NAME. The most important of these are:

  • INPUT_VALUE_ID — surrogate identifier of the parent input value definition. It is a component of the composite primary key and the join key back to PAY_INPUT_VALUES_F.
  • NAME — the translated display name of the input value shown to users in the selected language. This is the primary payload of the translation row.
  • LANGUAGE — the language code for the translated row and the second component of the primary key.
  • SOURCE_LANG — the language from which the row was originally seeded or copied, used by the MLS translation framework to track provenance.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard audit columns maintained by the EBS WHO columns convention.
  • ZD_EDITION_NAME — the edition label supporting the E-Business Suite online patching (editions) model introduced in 12.2.

The unique index PAY_INPUT_VALUES_F_TL_PK is defined on (INPUT_VALUE_ID, LANGUAGE, ZD_EDITION_NAME). The primary key object in the documentation is listed as PAY_INPUT_VALUES_F_TL_PK over (INPUT_VALUE_ID, LANGUAGE), making those two columns the business-key candidates, with ZD_EDITION_NAME included in the unique index to support edition-aware uniqueness.

Common Use Cases and Queries

The table is used whenever payroll element input values must be displayed, reported, or extracted in a specific language. Typical scenarios include element configuration screens, payroll setup reports, and localization audits.

  • Retrieving translated input value names for a given element definition by joining to the base table: 
    SELECT f.input_value_id, t.name, t.language
FROM   pay_input_values_f f,
       pay_input_values_f_tl t
WHERE  f.input_value_id = t.input_value_id
AND    t.language = USERENV('LANG');
  • Identifying input values missing a translation in a target language, a frequent localization validation query.
  • Comparing SOURCE_LANG against LANGUAGE to assess which rows were seeded versus manually translated.
  • Language-specific reporting extracts feeding downstream payroll analytics or migration programs.

Because of the MLS pattern, queries against translatable names should always constrain LANGUAGE to avoid duplicate rows per input value.

Related Objects

  • PAY_INPUT_VALUES_F — the base (non-translated) table that owns the definition; joined on INPUT_VALUE_ID.
  • PAY_INPUT_VALUES_F_TL — this table, joined to the base and to the language views.
  • PAY_ELEMENT_TYPES_F — element definitions to which input values belong, used for element-level reporting.
  • FND_LANGUAGES — the installed languages view that validates the LANGUAGE and SOURCE_LANG values.
  • PAY_INPUT_VALUE_RELATIONSHIPS — sequencing and dependency rules referencing input values.
  • PAY_ELEMENT_TYPE_USAGES — associates elements with input values in payroll processing contexts.

These relationships should be traversed using INPUT_VALUE_ID, LANGUAGE, and ZD_EDITION_NAME to preserve edition-aware, language-specific correctness.