Search Results fun_trx_types_tl




Overview
Explore in AI Chat

Overview

FUN_TRX_TYPES_TL is a translation (TL) table in the FUN — Financials Common Modules schema of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It stores the language-dependent, translatable attributes for Intercompany transaction types defined in the Financials Common Modules architecture. Every Intercompany transaction type maintained by the application requires a base-language row plus one row per additional installed language into which the transaction type name and description have been translated.

From a data modeling perspective, the metadata classifies this table heuristically as standalone. In Data Vault terms, the table is best understood as a satellite attached to the transaction type hub: the combination of TRX_TYPE_ID plus LANGUAGE identifies the parent business key, while the descriptive text columns (TRX_TYPE_NAME, DESCRIPTION) are attributes that can change over time and across languages. The lone documented foreign key, TRX_TYPE_ID → IGI_EXP_TRX_TYPE, reinforces this hub-and-satellite interpretation, since TRX_TYPE_ID is the shared business identifier linking the translation rows back to the driving transaction type entity.

Key Information Stored

The table comprises eleven documented columns. The most significant are:

  • TRX_TYPE_ID — the numeric identifier of the Intercompany transaction type. It is both a foreign key to IGI_EXP_TRX_TYPE and part of the unique business key of this table.
  • LANGUAGE — the NLS language code (for example, US or DE) indicating which translation the row carries. It is the second component of the unique business key.
  • ZD_EDITION_NAME — the editioning column used by the EBS 12.2 online patching architecture; it participates in the unique index and isolates rows by edition.
  • SOURCE_LANG — the language of the source (base) row from which the translation was derived, used by the translation framework to determine completeness.
  • TRX_TYPE_NAME — the translated, user-facing name of the Intercompany transaction type, displayed in lookup lists and transaction entry forms.
  • DESCRIPTION — the translated longer description of the transaction type.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS WHO columns that capture audit and concurrency information for each row.

The surrogate primary key for the table is not documented as a separate system-generated identifier; the definitive business-key candidate is the unique index FUN_TRX_TYPES_TL_U1, defined on (TRX_TYPE_ID, LANGUAGE, ZD_EDITION_NAME). Application logic should therefore treat that triplet as the logical identity of a translation row, while the WHO columns provide the audit trail.

Common Use Cases and Queries

Typical use cases include building bilingual or multilingual reports of Intercompany transaction types, validating that a translation exists for every installed language, and joining translated names onto transaction data for user-facing output. A common query pattern retrieves the translated name for a specific language:

  • SELECT t.trx_type_id, t.trx_type_name, t.description FROM fun.fun_trx_types_tl t WHERE t.language = USERENV('LANG') AND t.trx_type_id = :p_id;
  • Completeness check: join to the base transaction type table and flag records where no row exists in FUN_TRX_TYPES_TL for a given LANGUAGE or where SOURCE_LANG indicates a stale translation.
  • Audit reporting on LAST_UPDATED_BY and LAST_UPDATE_DATE to identify recently maintained transaction types.
  • In 12.2 environments, partition-aware queries should include ZD_EDITION_NAME filters to restrict results to the active edition.

Related Objects

The following objects are most significant when working with this table:

  • IGI_EXP_TRX_TYPE — referenced by the TRX_TYPE_ID foreign key; supplies the driving Intercompany transaction type definition.
  • FUN_TRX_TYPES_B — the base (non-translatable) table that holds language-independent attributes and is joined on TRX_TYPE_ID.
  • FUN_TRX_TYPES_VL — the translated view that conventionally joins the _B and _TL tables using TRX_TYPE_ID, LANGUAGE, and ZD_EDITION_NAME to present a single localized row.
  • FND_LANGUAGES — the language definition table used to validate the LANGUAGE and SOURCE_LANG values and to report installed languages.
  • FND_TERRITORIES and related NLS objects — relevant when mapping language codes to reporting locales.

These relationships should be used as the basis for joins, since all translation lookups depend on the TRX_TYPE_ID and LANGUAGE combination defined by the unique index.