Search Results fun_trx_types_tl_n2




Overview

FUN.FUN_TRX_TYPES_TL is the translation table for Intercompany transaction types within the Oracle E-Business Suite Financials (FUN) schema. In Oracle EBS Release 12.1.1 and 12.2.2, the FUN schema supports the Intercompany and Intracompany balancing functionality, and the transaction type definitions that drive this functionality are stored across the base table FUN_TRX_TYPES_B and this translation table, FUN_TRX_TYPES_TL. The "TL" suffix denotes a translatable table: it stores the language-dependent descriptive attributes — namely the transaction type name and long description — in each installed language, allowing users to view intercompany transaction type labels in their preferred language while preserving a single shared identifier.

The table is stored in the APPS_TS_TX_DATA tablespace with PCT Free 10, and its indexes reside in APPS_TS_TX_IDX. The ETRM records the object status as VALID and its FND Design Data reference as FUN.FUN_TRX_TYPES_TL. From a Data Vault modeling heuristic, the table is classified as standalone, which suggests treating it as a descriptive satellite or reference data set keyed by the transaction type identifier and language rather than as a hub or link; the classification is a modeling suggestion derived from the FK structure, not a physical constraint. The documentation notes only a single inbound referential relationship, from FUN_TRX_TYPES_TL.TRX_TYPE_ID to IGI_EXP_TRX_TYPE, indicating a loosely coupled relationship to the IGI expense transaction type structures.

Key Information Stored

The table contains eleven documented columns. The most important are:

  • TRX_TYPE_ID — System-generated primary key identifying the intercompany transaction type. It is the surrogate key and also the leading column of every index.
  • LANGUAGE — The language code of the translated row; combined with TRX_TYPE_ID it identifies the translated record.
  • SOURCE_LANG — The source language of the original (untranslated) description, used by the multi-language support facilities to track derivation.
  • TRX_TYPE_NAME — The user-facing name of the transaction type, currently up to 25 characters. This is a business-key candidate and is indexed non-uniquely.
  • DESCRIPTION — A longer free-text description, up to 240 characters, of the transaction type.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard "Who" audit columns populated by the Oracle Forms/AD foundation layer.
  • ZD_EDITION_NAME — The edition name supporting Oracle's Edition-Based Redefinition (EBR) introduced in 12.2, used to isolate online patching editions.

The unique index FUN_TRX_TYPES_TL_U1 (TRX_TYPE_ID, LANGUAGE, ZD_EDITION_NAME) is the effective business-key candidate, guaranteeing one translated row per transaction type, per language, per edition. Two non-unique indexes, FUN_TRX_TYPES_TL_N1 (TRX_TYPE_ID) and FUN_TRX_TYPES_TL_N2 (TRX_TYPE_NAME), support lookup by identifier and by name respectively.

Common Use Cases and Queries

Typical uses include multilingual reporting, data migration validation, and intercompany setup auditing. A common query retrieves the active-language name for a given transaction type:

  • SELECT TRX_TYPE_ID, TRX_TYPE_NAME, DESCRIPTION FROM FUN.FUN_TRX_TYPES_TL WHERE LANGUAGE = USERENV('LANG') AND TRX_TYPE_ID = :p_id;
  • Join to FUN_TRX_TYPES_B on TRX_TYPE_ID to correlate base attributes with translated text.
  • Query all languages for a single type: SELECT LANGUAGE, TRX_TYPE_NAME FROM FUN.FUN_TRX_TYPES_TL WHERE TRX_TYPE_ID = :p_id;
  • Search by name using the FUN_TRX_TYPES_TL_N2 index: WHERE TRX_TYPE_NAME LIKE 'ABC%'.

Because FUN_TRX_TYPES_TL does not reference any database object directly, queries are normally driven from the base table or from reporting views that perform the language join.

Related Objects

  • FUN.FUN_TRX_TYPES_B — The base table holding language-independent transaction type attributes; joined via TRX_TYPE_ID.
  • FUN.FUN_TRX_TYPES_TL# — The editioning view or synonym counterpart referenced in 12.2 EBR installations.
  • IGI_EXP_TRX_TYPE — Referenced by the inbound FK on TRX_TYPE_ID; intercompany expense transaction type definitions.
  • FUN_TRX_TYPES_TL_U1, FUN_TRX_TYPES_TL_N1, FUN_TRX_TYPES_TL_N2 — Supporting indexes in APPS_TS_TX_IDX.
  • FND_LANGUAGES — Provides the valid LANGUAGE and SOURCE_LANG code values used by this table.