Search Results extended_precision

Overview

GLBV_CURRENCIES is an Oracle E-Business Suite view owned by the APPS schema and classified under the General Ledger (GL) product family. It exposes currency definition information maintained in Oracle General Ledger and is commonly consumed by reporting, integration, and multi-currency conversion logic. The view is a validation view rather than a transactional object; its purpose is to present the curated set of currency attributes that Oracle EBS uses when performing foreign currency transactions, revaluation, translation, and reporting across subledgers.

The prefix "GLBV" follows the Oracle EBS convention for General Ledger views that are exposed for public or programmatic use, and the view is built with a read-only clause, confirming it is intended strictly for querying and not for DML. Because currency data is foundational to virtually every Oracle Financials module, GLBV_CURRENCIES frequently appears in cross-product reporting and interface extracts.

Underlying Base Objects

Per the documented view definition, GLBV_CURRENCIES is defined over a single base table: FND_CURRENCIES, aliased in the view text as CURRENCY. The view is declared WITH READ ONLY, reinforcing its role as a controlled, read-only projection of the underlying Oracle Application Object Library (FND) currency table maintained by Oracle General Ledger.

The FND_CURRENCIES table stores the master list of currencies that have been enabled for use in the EBS instance, along with precision settings, effective dates, symbol, and euro conversion information. GLBV_CURRENCIES does not simply perform a SELECT *; it substitutes specific columns with "_LA:" tagged expressions that resolve to descriptive meaning values, particularly for the ENABLED_FLAG and DERIVE_TYPE attributes. This design allows the view to present human-readable descriptions rather than raw coded values.

Key Columns

• CURRENCY_CODE — The ISO currency identifier (for example USD, EUR, GBP) as enabled in the instance.
• "_LA:ENABLED_FLAG" — A descriptive rendering of the currency enabled status, resolved against FND_LOOKUPS using the YES_NO_NEVER lookup type; returns the MEANING of the lookup code.
• PRECISION — The standard number of decimal places used for the currency.
• EXTENDED_PRECISION — The extended number of decimal places supported for the currency, used in calculations requiring higher accuracy than the standard precision.
• MINIMUM_ACCOUNTABLE_UNIT — The smallest unit that may be recorded for the currency, governing rounding and account balance behavior.
• SYMBOL — The display symbol associated with the currency.
• START_EFFECTIVE_DATE / END_EFFECTIVE_DATE — The active date range during which the currency definition applies.
• EURO_EFFECTIVE_DATE, "_LA:EURO_CURRENCY_TYPE", EURO_CONVERSION_FACTOR — Attributes supporting European Monetary Union conversion and the relationship of the currency to the euro.
• DERIVE_EFFECTIVE, "_LA:CURRENCY.DERIVE_TYPE:GL_LOOKUPS:DERIVE_TYPE:MEANING", DERIVE_FACTOR — Parameters governing derived currency relationships and rates.

The EXTENDED_PRECISION column is of particular interest to implementers, since it determines the level of rounding precision available for high-precision currencies and directly affects journal amounts and balance calculations.

Common Use Cases and Queries

Typical usage includes reporting the enabled currencies available in an instance, verifying precision and extended precision settings prior to configuring a new ledger, and driving conversion logic in custom interfaces. A representative query retrieving currency precision details is shown below.

SELECT CURRENCY_CODE, PRECISION, EXTENDED_PRECISION, MINIMUM_ACCOUNTABLE_UNIT, SYMBOL FROM APPS.GLBV_CURRENCIES WHERE CURRENCY_CODE = 'JPY';

To list all enabled currencies with their effective dates, a query against the descriptive columns and date ranges is used.

SELECT CURRENCY_CODE, "_LA:ENABLED_FLAG", START_EFFECTIVE_DATE, END_EFFECTIVE_DATE FROM APPS.GLBV_CURRENCIES;

Because the view is read-only and resolves lookup meanings, it is well suited for concurrent program extracts, BI Publisher data models, and integration feeds where display-friendly currency definitions are required without exposing DML access to FND_CURRENCIES.