Search Results gl_cross_rate_rules

Overview

FND_CURRENCIES is the Application Object Library (FND) master table that defines the currencies enabled for use at a given Oracle E-Business Suite site. Owned by the APPLSYS schema, it functions as the single authoritative registry of currency codes across all EBS modules. Every functional area that records monetary values — General Ledger, Payables, Receivables, Assets, Projects, Purchasing, Order Management, Cash Management, and Tax — resolves its currency references back to this table.

The table sits near the center of the EBS data model and is referenced by an exceptionally large number of foreign keys. Its only outbound foreign key is to FND_TERRITORIES through ISSUING_TERRITORY_CODE, making it a low-dependency, high-fan-out reference object. Under the heuristic Data Vault classification supplied in the ETRM metadata, FND_CURRENCIES is described as hub-leaning: it behaves as a business key hub keyed on CURRENCY_CODE, with descriptive attributes (precision, symbol, territory) that would conventionally be modeled as a satellite. Practitioners designing a warehouse layer may reasonably treat it as a hub with an attached descriptive satellite.

Key Information Stored

The table contains 58 documented columns. The most operationally significant are:

• CURRENCY_CODE — the primary key of FND_CURRENCIES_PK and the business identifier (for example, USD, EUR, JPY). Defined as ISO-compliant three-character codes.
• ENABLED_FLAG — indicates whether the currency is active and selectable at the site.
• CURRENCY_FLAG — distinguishes currencies from other units of measure-like entries.
• DESCRIPTION — the display name of the currency.
• ISSUING_TERRITORY_CODE — the foreign key to FND_TERRITORIES identifying the issuing country or territory.
• PRECISION and EXTENDED_PRECISION — the number of decimal places used for standard and extended rounding.
• MINIMUM_ACCOUNTABLE_UNIT — the smallest unit considered accountable in accounting entries.
• SYMBOL — the printable currency symbol.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the effective date range during which the currency is usable.
• DERIVE_EFFECTIVE, DERIVE_TYPE, and DERIVE_FACTOR — attributes supporting derived or euro-conversion currency handling.
• ZD_EDITION_NAME — the editioning column that participates in the unique key FND_CURRENCIES_U1 (CURRENCY_CODE, ZD_EDITION_NAME) alongside the primary key.
• The ATTRIBUTE1–15, GLOBAL_ATTRIBUTE_CATEGORY, and GLOBAL_ATTRIBUTE1–20 columns — the standard EBS descriptive flexfield and DFF context columns available for site-specific extension.

The primary key FND_CURRENCIES_PK is defined on CURRENCY_CODE. The unique index FND_CURRENCIES_U1 (CURRENCY_CODE, ZD_EDITION_NAME) is the business-key candidate in an editioned (12.2.2) environment. Multilingual display text is held separately in FND_CURRENCIES_TL.

Common Use Cases and Queries

The most frequent use is validation and lookup of active currencies when building a value set, LOV, or interface loader. A typical query is:

• SELECT currency_code, description, precision FROM fnd_currencies WHERE enabled_flag = 'Y' ORDER BY currency_code;
• Joining to FND_TERRITORIES to attribute a currency to its issuing country: SELECT c.currency_code, c.description, t.territory_code FROM fnd_currencies c, fnd_territories t WHERE c.issuing_territory_code = t.territory_code;
• Auditing inactive or date-bounded currencies: SELECT currency_code, start_date_active, end_date_active FROM fnd_currencies WHERE enabled_flag = 'N' OR end_date_active < SYSDATE;

Reporting uses include currency-validation extracts for GL_DAILY_RATES and GL_DAILY_RATES_INTERFACE loads, checking which currencies are enabled before converting a ledger balance (GL_BALANCES.CURRENCY_CODE), and verifying that a multi-currency setup referenced by GL_LEDGERS.CURRENCY_CODE or GL_SETS_OF_BOOKS.CURRENCY_CODE is present and active. Because FND_CURRENCIES_TL carries the translated description, reports requiring localized names should join on CURRENCY_CODE with the appropriate language condition. Data-fix and conversion scripts routinely verify precision and minimum accountable unit here, since journal and subledger rounding derives from these values.

Related Objects

The relationship metadata shows FND_CURRENCIES as one of the most heavily referenced objects in EBS. The most significant dependents include:

• FND_TERRITORIES — referenced through FND_CURRENCIES.ISSUING_TERRITORY_CODE (the table's only outbound foreign key).
• FND_CURRENCIES_TL — the translation table, keyed on CURRENCY_CODE, supplying language-specific descriptions.
• GL_LEDGERS and GL_SETS_OF_BOOKS — reference CURRENCY_CODE to define each ledger's functional currency.
• GL_DAILY_RATES and GL_DAILY_RATES_INTERFACE — reference FROM_CURRENCY and TO_CURRENCY, the core of all conversion processing.
• GL_BALANCES and GL_JE_HEADERS — reference CURRENCY_CODE for entered and accounted balances and journals.
• AP_INVOICES_ALL, AP_CHECKS_ALL, and AR_CASH_RECEIPTS_ALL — reference CURRENCY_CODE to drive subledger and payment processing.
• AP_SYSTEM_PARAMETERS_ALL, AR_SYSTEM_PARAMETERS_ALL family, and FINANCIALS_SYSTEM_PARAMS_ALL — reference BASE, INVOICE, and PAYMENT currency codes for application defaults.
• PO_HEADERS_ALL and PO_VENDORS — reference CURRENCY_CODE, PAYMENT_CURRENCY_CODE, and INVOICE_CURRENCY_CODE for procurement.
• ZX_LINES and ZX_TAXES_B — reference TRX, REPORTING, and TAX currency codes within the E-Business Tax engine.

The breadth of these references confirms that FND_CURRENCIES should be treated as a protected reference table: keys are effectively immutable once transacted, and changes to precision or enabled status can ripple across every financial module that depends on it.