Search Results euro_effective_date




Overview
Explore in AI Chat

Overview

APPS.GLFV_CURRENCIES is a Business Intelligence System (BIS) view in the Oracle E-Business Suite APPS schema. It is registered in the FND Design Data repository under the identifier SQLGL.GLFV_CURRENCIES and is shipped with a VALID status across EBS 12.1.1 and 12.2.2. The view presents the master list of currencies recognized by Oracle General Ledger, encompassing both the predefined ISO currencies supplied by Oracle Applications and user-defined non-ISO currencies, together with the special statistical currency used for reporting-only balances. Because every set of books must be defined by a currency, this view functions as the authoritative reference for currency-level attributes that drive journal entry validation, accounting precision rules, and multi-currency reporting.

Underlying Base Objects

According to the documented dependency information, APPS.GLFV_CURRENCIES references the base table APPS.FND_CURRENCIES. It is not referenced by any other database object, meaning it is a terminal reporting view and can safely be queried or replaced without cascading invalidation. FND_CURRENCIES is the application foundation table that stores currency definitions at the localization level; the GLFV_CURRENCIES view projects those definitions into the General Ledger functional context, applying the GL naming convention and exposing Euro-related attributes that are specific to the European Monetary Union transition requirements. Because the metadata documentation lists no further base objects, integrations should treat FND_CURRENCIES as the single upstream source.

Key Columns

  • CURRENCY_CODE (VARCHAR2, 15) — The unique code identifying each currency, such as USD, EUR, or a user-defined non-ISO code.
  • PRECISION and EXTENDED_PRECISION (NUMBER) — Define the standard and extended decimal precision used when storing and displaying monetary amounts.
  • MINIMUM_ACCOUNTABLE_UNIT (NUMBER) — The smallest unit that can be represented in journal entries for the currency.
  • SYMBOL (VARCHAR2, 12) — The display symbol associated with the currency.
  • START_EFFECTIVE_DATE and END_EFFECTIVE_DATE (DATE) — The validity window during which the currency may be used in transactions.
  • EURO_EFFECTIVE_DATE (DATE) — The date on which the currency became subject to Euro conversion processing.
  • EURO_CURRENCY_TYPE (CHAR, 55) — Descriptive type classification used for Euro transposition logic, surfaced through the localization attribute _LA:EURO_CURRENCY_TYPE.
  • EURO_CONVERSION_FACTOR (NUMBER) — The fixed conversion rate with which an EMU legacy currency is translated into the Euro. This is the column most directly related to the user's search term.
  • ENABLED_FLAG (_LA:ENABLED_FLAG, CHAR, 58) — Localization attribute indicating whether the currency is active.
  • _DF (CHAR, 31) — A descriptive flexfield context or reference column exposed by the view.

Common Use Cases and Queries

The view is typically queried to validate that a currency is enabled before inserting journal lines, to retrieve precision settings when formatting amounts in custom reports, and to resolve Euro conversion factors during EMU legacy data migration. The following example lists all enabled currencies along with their precision and Euro attributes:

SELECT CURRENCY_CODE, PRECISION, EXTENDED_PRECISION, MINIMUM_ACCOUNTABLE_UNIT, SYMBOL, START_EFFECTIVE_DATE, END_EFFECTIVE_DATE, EURO_EFFECTIVE_DATE, _LA:EURO_CURRENCY_TYPE, EURO_CONVERSION_FACTOR, _LA:ENABLED_FLAG, _DF FROM APPS.GLFV_CURRENCIES;

A targeted query returning the Euro conversion factor for a specific currency would read: SELECT CURRENCY_CODE, EURO_EFFECTIVE_DATE, EURO_CONVERSION_FACTOR, _LA:EURO_CURRENCY_TYPE FROM APPS.GLFV_CURRENCIES WHERE CURRENCY_CODE = 'DEM'; This pattern is commonly embedded in conversion and reporting programs that must apply the legally mandated fixed rates during Euro translation. Analysts should note that the localization columns prefixed with _LA are exposed only in the context of the Business Intelligence System view and are not directly part of the FND_CURRENCIES physical table schema.