Search Results pay_input_values_f_tl_pk

Overview

HR.PAY_INPUT_VALUES_F_TL is the translation (TL) table for Oracle Payroll input value definitions in Oracle E-Business Suite 12.1.1 and 12.2.2. An input value is an element-level parameter that determines the amount, rate, or unit of pay associated with an element entry — for example, hours worked, a rate, or a flat amount. While the base definition and its non-translated attributes reside in PAY_INPUT_VALUES_F, the _TL table stores the language-specific display name of each input value, enabling a single payroll configuration to present user-facing labels in multiple installed languages.

From a dimensional modeling perspective, the metadata classifies this object heuristically as standalone (no mined foreign key relationships in the provided relationship data). In Data Vault terms, PAY_INPUT_VALUES_F_TL is best modeled as a satellite attached to the input value business key, carrying descriptive, language-dependent attributes. The translation nature of the table means each satellite row is qualified by language and, in the 12.2.2 physical schema, by edition.

Key Information Stored

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

• INPUT_VALUE_ID (NUMBER) — System-generated primary key originating from PAY_INPUT_VALUES_F; identifies the parent input value definition.
• LANGUAGE (VARCHAR2) — The language of the translated row; part of the composite primary key.
• NAME (VARCHAR2, 80) — The translated, user-facing name of the input value; this is the primary descriptive payload of the table.
• SOURCE_LANG (VARCHAR2) — The language in which the row was originally authored, used by the translation framework to identify rows pending translation.
• ZD_EDITION_NAME — Edition identifier present in the 12.2.2 physical schema, supporting Edition-Based Redefinition (EBR).
• Standard Who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE provide full audit lineage.

The surrogate primary key is defined by the unique index PAY_INPUT_VALUES_F_TL_PK on (INPUT_VALUE_ID, LANGUAGE). In the 12.2.2 physical schema the unique index is documented as (INPUT_VALUE_ID, LANGUAGE, ZD_EDITION_NAME), reflecting the edition dimension. A secondary non-unique index, PAY_INPUT_VALUES_F_TL_N2, exists on (LANGUAGE, NAME) to accelerate translation lookups by name. As a _TL table, it does not itself hold the business-key candidates such as input value short name or element linkage; those reside in the base _F table.

Common Use Cases and Queries

Typical scenarios include building bilingual or multilingual payroll reporting, auditing which input value names remain untranslated, and joining translated labels onto element entry data.

• Retrieve translated names for a language:

  SELECT t.input_value_id, t.name, t.source_lang
  FROM   hr.pay_input_values_f_tl t
  WHERE  t.language = USERENV('LANG');

• Identify rows still in the source language (translation gaps):

  SELECT input_value_id, language, name
  FROM   hr.pay_input_values_f_tl
  WHERE  language <> source_lang;

• Join to the base definition for a fully labeled input value list:

  SELECT f.input_value_id, f.name base_name, t.name translated_name
  FROM   hr.pay_input_values_f  f,
         hr.pay_input_values_f_tl t
  WHERE  f.input_value_id = t.input_value_id
  AND    t.language = USERENV('LANG');

Because the table is read-mostly configuration data, reporting queries should generally run against a current-edition view or filtered by ZD_EDITION_NAME in 12.2.2.

Related Objects

• HR.PAY_INPUT_VALUES_F — The base (non-translated) definition table; joined on INPUT_VALUE_ID. This is the parent entity of the satellite.
• HR.PAY_INPUT_VALUES_F_TL (self / public synonym) — Public synonym and edition view referencing the table; the APPS synonym PAY_INPUT_VALUES_F_TL and the EBR helper view PAY_INPUT_VALUES_F_T041437_WHO are documented dependents.
• PAY_ELEMENT_TYPES_F / PAY_ELEMENT_TYPES_F_TL — Element definitions that consume input values; linked through the input value's owning element type.
• PAY_ELEMENT_ENTRY_VALUES_F — Runtime element entry values that reference input value IDs, providing the transactional context for reporting.
• FND_USER / FND_LOGINS — Referenced by the standard Who columns for audit resolution.

All dependencies documented for this object are inbound: HR.PAY_INPUT_VALUES_F_TL does not reference any database object directly, confirming its role as a leaf satellite depending outward only on its parent key and the FND audit tables.