Search Results pay_run_types_tl_pk




Overview
Explore in AI Chat

Overview

PAY_RUN_TYPES_F_TL is a translation (TL) table in the Oracle EBS Payroll (PAY) module, owned by the HR schema. It stores the language-dependent, translated descriptive attributes for payroll run types — specifically the display name and short name used in the user interface and reports. It is the translated counterpart to the base run types table, PAY_RUN_TYPES_F, and follows the standard Oracle Applications multilingual (MLS) design pattern, where a language-independent base row is paired with one or more language-specific TL rows. In the documented ETRM 12.2.2 physical schema, the table contains 11 columns and is classified as VALID.

The heuristic Data Vault classification mined from the FK structure is standalone. In modeling terms, this reflects that the table does not carry the foreign-key dependency footprint typical of a hub or link; it is best treated as a language-specific descriptive component (analogous to a satellite) attached to the run type business key. Rather than describing a business event, it enriches the run type with locale-specific text.

Key Information Stored

The table’s core identity and content columns are:

  • RUN_TYPE_ID — Surrogate identifier of the parent run type; part of the primary key.
  • LANGUAGE — Language/locale code of the translated row; part of the primary key.
  • SOURCE_LANG — The source language from which the translation was derived, used internally by the MLS framework.
  • RUN_TYPE_NAME — The translated, user-facing name of the payroll run type.
  • SHORTNAME — The translated short name or abbreviation displayed in list-of-values and compact UI contexts.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording who last modified the row and when.
  • CREATED_BY, CREATION_DATE — Standard audit columns recording row creation.
  • ZD_EDITION_NAME — Editioning column supporting Oracle EBS online patching (ADOP), enabling edition-based redefinition.

The primary key is PAY_RUN_TYPES_TL_PK on (RUN_TYPE_ID, LANGUAGE). The documented unique index additionally includes ZD_EDITION_NAME, giving the business-key candidate (RUN_TYPE_ID, LANGUAGE, ZD_EDITION_NAME). RUN_TYPE_ID links each translated row to its base run type definition; LANGUAGE determines which localized row is returned.

Common Use Cases and Queries

Typical scenarios include building multilingual payroll run type picklists, retrieving locale-specific names for concurrent process reporting, and validating translation coverage across installed languages. A representative query joins the TL table to the base table and filters to the session language:

  • Retrieve translated names: SELECT b.run_type_id, t.run_type_name, t.shortname FROM pay_run_types_f b, pay_run_types_f_tl t WHERE b.run_type_id = t.run_type_id AND t.language = USERENV('LANG').
  • Audit translations: select all rows for a given RUN_TYPE_ID across LANGUAGES to confirm coverage.
  • Reporting: join to PAY_RUN_TYPES_F and payroll process/run results to present user-friendly run type descriptions in BI Publisher or Discoverer reports.
  • Data migration or patching: verify SOURCE_LANG and ZD_EDITION_NAME values when moving configuration between environments.

Related Objects

The most significant related objects are the base run type tables and their dependent payroll structures:

  • PAY_RUN_TYPES_F — Base (language-independent) run type definition; joined on RUN_TYPE_ID.
  • PAY_RUN_TYPES_TL — Synonymous translation view/table exposing translated names.
  • Payroll process and run tables (for example payroll run/action results) that reference RUN_TYPE_ID.
  • Concurrent program and process definitions in PAY that consume run type identifiers.
  • Lookup and MLS framework views supporting the _F / _TL pattern.

Because the classification is standalone, dependencies are primarily driven by the shared RUN_TYPE_ID business key rather than by strict foreign-key constraints.