Search Results pay_payment_types_tl




Overview
Explore in AI Chat

Overview

PAY_PAYMENT_TYPES_TL is the translation (language) table for payment types within the Oracle Payroll (PAY) module. It resides in the HR schema and stores the translatable text attributes associated with each payment type, allowing the application to present payment type names and descriptions in the user's selected language. Payment types themselves are defined in the base table (PAY_PAYMENT_TYPES), while this "_TL" table carries the language-dependent name and description values used in forms, list of values, concurrent program outputs, and reports.

The object is owned by the HR schema and is marked VALID in the ETRM metadata for both Oracle EBS 12.1.1 and 12.2.2. The physical schema documents eleven columns for the 12.2.2 release. In 12.2.2, the translation table has been extended with the ZD_EDITION_NAME column, reflecting the adoption of edition-based redefinition (EBR) for online patching. Based on the documented foreign-key structure, the heuristic Data Vault classification is standalone. In Data Vault modeling terms, this suggests the table should be treated as a satellite-like structure keyed to its parent payment type and language, rather than as a hub or link.

Key Information Stored

The table's primary key is defined by the PAY_PAYMENT_TYPES_TL_PK constraint, comprising PAYMENT_TYPE_ID and LANGUAGE. These two columns uniquely identify a translated row for a given payment type in a specific language. PAYMENT_TYPE_ID serves as the surrogate foreign key linking back to the base payment type record, while LANGUAGE identifies the language of the translation. The ETRM metadata lists an additional unique index candidate, PAY_PAYMENT_TYPES_TL_PK, shown as (PAYMENT_TYPE_ID, LANGUAGE, ZD_EDITION_NAME), which in 12.2.2 incorporates the edition dimension.

The principal business content columns are PAYMENT_TYPE_NAME, which holds the translated display name of the payment type, and DESCRIPTION, which provides the translated descriptive text. SOURCE_LANG records the source language from which the translation was derived, supporting the multi-language translation framework. Auditor columns include CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN, which track who created and last modified each translated row and when. The ZD_EDITION_NAME column is the editioning column used by 12.2.2's online patching architecture.

Common Use Cases and Queries

Typical reporting and integration scenarios join the translation table to the base payment type table to retrieve a user-language name. A representative query retrieves the translated name and description filtered by language, for example:

  • SELECT payment_type_id, payment_type_name, description FROM pay_payment_types_tl WHERE language = 'US' ORDER BY payment_type_name;
  • Joining to the base table to combine non-translatable attributes with translated text, using PAYMENT_TYPE_ID as the join column.
  • Restricting lookups by SOURCE_LANG for translation audit or completeness reporting.
  • In 12.2.2, filtering by ZD_EDITION_NAME where edition-aware queries are required.

These patterns are commonly used in payroll payment type setup reports, list-of-values validation for payment method configuration, and data migration extracts that must supply language-specific labels.

Related Objects

Because the documented structure classifies this object as standalone, related objects are inferred from the shared PAYMENT_TYPE_ID key. The most significant related objects include:

  • PAY_PAYMENT_TYPES — the base payment type definition table, joined on PAYMENT_TYPE_ID.
  • PAY_PAYMENT_TYPES_TL — referenced by payroll payment method and disbursement setup entities keyed on payment type.
  • Payroll payment method configuration tables that resolve translated payment type names for display.
  • Concurrent program and report definitions that query payment type translations through the language join.
  • The PAY_PAYMENT_TYPES_TL_PK constraint and associated unique index governing row uniqueness.