Search Results derive_effective

Overview

FND_CURRENCIES_VL is a translatable (VL, "view with language") database view owned by the APPS schema in Oracle E-Business Suite. It is part of the FND — Application Object Library product and is present in both release 12.1.1 and 12.2.2. The view is the standard reporting and integration interface for currency definitions maintained in Oracle General Ledger and shared across the entire E-Business Suite. EBS stores currency setup in a pair of tables: FND_CURRENCIES, which holds the non-translated attributes such as precision, symbol, and active dates, and FND_CURRENCIES_TL, which holds the language-dependent name and description. FND_CURRENCIES_VL joins the two and restricts the translation side to the session language, presenting one consolidated row per currency with its descriptive text already resolved. For that reason, almost all seeded Oracle forms, concurrent programs, and reports that reference a currency name or description query this view rather than the underlying tables directly. It is equally important as a lookup source for custom reports, interfaces, and conversions that must return a readable currency name alongside the currency code.

Underlying Base Objects

The view is defined over two synonyms: FND_CURRENCIES (the base table, aliased B in the view text) and FND_CURRENCIES_TL (the translation table, aliased T). The join condition is B.CURRENCY_CODE = T.CURRENCY_CODE AND T.LANGUAGE = USERENV('LANG'). The USERENV('LANG') predicate is the defining characteristic of the VL pattern: it returns only the translation row matching the language of the current session, so a user running with a French language setting sees French names and descriptions while the underlying code-based attributes remain identical. All columns sourced from the base table are inherited unchanged, including the descriptive flexfield (CONTEXT and ATTRIBUTE1–15) and the global descriptive flexfield (GLOBAL_ATTRIBUTE_CATEGORY and GLOBAL_ATTRIBUTE1–20). ROW_ID is derived from the base table ROWID. Because the view is owned by APPS and the base objects are exposed as public synonyms, the view should be referenced with the APPS or FND prefix in custom code, for example APPS.FND_CURRENCIES_VL.

Key Columns

• CURRENCY_CODE — The ISO-style currency code (for example USD, EUR, JPY); the unique business key and the join column to the translation table.
• NAME and DESCRIPTION — Language-dependent descriptive text from FND_CURRENCIES_TL, resolved for the session language.
• ENABLED_FLAG — Indicates whether the currency is enabled and selectable for transactions.
• CURRENCY_FLAG — Classifies the record as an actual currency, an issuing territory, or a summary/related currency type.
• PRECISION and EXTENDED_PRECISION — The number of decimal places used for standard and extended (journal entry) amounts.
• MINIMUM_ACCOUNTABLE_UNIT — The smallest amount that may be entered, used to enforce rounding rules such as the Euro conversion constraint.
• SYMBOL — The display symbol associated with the currency.
• START_DATE_ACTIVE / END_DATE_ACTIVE — The date range during which the currency is active.
• ISSUING_TERRITORY_CODE and ISO_FLAG — The issuing territory identifier and an indicator of ISO 4217 compliance.
• DERIVE_EFFECTIVE, DERIVE_TYPE, DERIVE_FACTOR — Attributes supporting derived (euro-influenced) currency definitions.
• ATTRIBUTE1–15 and GLOBAL_ATTRIBUTE1–20 — Descriptive flexfield columns available for customer extensions.

Common Use Cases and Queries

The view is typically used to validate a currency code, to obtain the number of decimals for rounding in a custom calculation, or to populate a list of valid currencies in a custom form or report. The following query lists all enabled currencies with their localized names:

SELECT currency_code, name, precision, symbol
  FROM apps.fnd_currencies_vl
 WHERE enabled_flag = 'Y'
   AND currency_flag = 'Y'
 ORDER BY currency_code;

To retrieve the reporting precision for a specific currency:

SELECT currency_code, name, precision, extended_precision,
       minimum_accountable_unit
  FROM apps.fnd_currencies_vl
 WHERE currency_code = 'USD';

A third common pattern joins the view to a transaction or setup table to return a readable currency name in a custom concurrent program — for example, joining FND_CURRENCIES_VL to GL_LEDGERS on CURRENCY_CODE. Because the view filters on USERENV('LANG'), results always reflect the language of the session in which the query executes; code that must return a specific language regardless of session settings should query FND_CURRENCIES_TL directly with an explicit LANGUAGE predicate.