Search Results fnd_currencies_tl




Overview
Explore in AI Chat

Overview

FND_CURRENCIES_TL is the translation table for FND_CURRENCIES in the Oracle E-Business Suite Application Object Library (product FND). It is owned by the APPLSYS schema and is classified as VALID in Oracle EBS releases 12.1.1 and 12.2.2. While the parent table FND_CURRENCIES stores the operational attributes of a currency — precision, extended precision, symbol, and enablement flags — FND_CURRENCIES_TL stores the language-specific descriptive text, principally the currency name and description. Because Oracle EBS is deployed in multilingual environments using the Multi-Language Support (MLS) architecture, every translatable attribute is separated into a "_TL" companion table keyed by CURRENCY_CODE and LANGUAGE.

From a Data Vault modeling perspective, the mined relationship structure classifies this object as satellite-leaning. The reason is that FND_CURRENCIES_TL does not introduce a new business key of its own: it inherits CURRENCY_CODE from FND_CURRENCIES through a foreign key, and simply adds the LANGUAGE qualifier along with descriptive, language-dependent attributes. In a Data Vault model it would typically be modeled as a satellite attached to the FND_CURRENCIES hub, with LANGUAGE acting as a multi-active or descriptive discriminator rather than an independent hub key.

Key Information Stored

The table contains 11 documented columns. The most significant are the following:

  • CURRENCY_CODE — The ISO-style currency identifier (for example, USD, EUR, GBP). It is both part of the composite primary key and a foreign key to FND_CURRENCIES.
  • LANGUAGE — The Oracle language code (for example, US, DE, FR) identifying the translation. It is the second component of the composite primary key.
  • NAME — The translated currency name displayed to users in forms, reports, and LOVs for the given language.
  • DESCRIPTION — The translated descriptive text for the currency.
  • SOURCE_LANG — The language in which the row was originally authored, used by the MLS translation synchronization process.
  • ZD_EDITION_NAME — The editioning column used for online patching in EBS 12.2.x; it forms part of both unique indexes.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking row creation and modification.

The primary key is FND_CURRENCIES_TL_PK on (CURRENCY_CODE, LANGUAGE). Two business-key candidates are documented: FND_CURRENCIES_TL_U1 on (CURRENCY_CODE, LANGUAGE, ZD_EDITION_NAME) and FND_CURRENCIES_TL_U2 on (NAME, LANGUAGE, ZD_EDITION_NAME). Because NAME appears in a unique index, currency names must be unique within a language, which is a notable constraint when defining custom currencies. There is no separately generated surrogate key; the surrogate role is effectively served by the natural composite of CURRENCY_CODE and LANGUAGE.

Common Use Cases and Queries

Typical reporting scenarios require resolving a currency code into its translated name, often constrained by the session language or a specific reporting language.

  • Retrieving the display name for a currency in a given language: SELECT name FROM fnd_currencies_tl WHERE currency_code = 'USD' AND language = 'US';
  • Joining translated names to transactional data through FND_CURRENCIES: SELECT c.currency_code, t.name FROM fnd_currencies c, fnd_currencies_tl t WHERE c.currency_code = t.currency_code AND t.language = USERENV('LANG');
  • Auditing translation coverage to find currencies lacking a translation in a target language.
  • Building multilingual LOVs and report parameter lists that present currency names in the end user's preferred language.

Because FND_CURRENCIES and FND_CURRENCIES_TL are frequently cached by the application, direct DML should be avoided; use the FND_CURRENCY_PKG APIs or the Currency definition form instead.

Related Objects

  • FND_CURRENCIES — The base (non-translated) table; joined on CURRENCY_CODE. This is the only documented foreign key reference.
  • FND_CURRENCIES_TL (via FND_CURRENCIES_TL_PK / _U1 / _U2) — The unique indexes enforcing key and name uniqueness.
  • GL_DAILY_RATES — Stores daily conversion rates referencing CURRENCY_CODE.
  • GL_SETS_OF_BOOKS — References currencies as functional currency.
  • FND_CURRENCY_PKG — The PL/SQL API that maintains currency definitions and their translations.
  • FND_CURRENCY (view / LOV) — The user-facing view often joined against this table for display purposes.