Search Results gl_fixed_conv_rates_u1

Overview

GL_FIXED_CONV_RATES is a General Ledger reference table that stores fixed conversion rates established between a currency being phased out (the "old" currency) and the currency that replaces it. This mechanism supports currency redenomination and euro-conversion-style scenarios, where a legacy currency is retired at a legally or contractually fixed rate against its successor. Each row defines a one-to-one mapping between an old currency and its single permitted replacement currency, together with the rate and the effective date from which the relationship applies.

The table resides in the GL schema under the APPS_TS_TX_DATA tablespace, with a PCT Free of 10. It carries FND Design Data reference SQLGL.GL_FIXED_CONV_RATES, indicating it is a registered Oracle Application Object Library/General Ledger schema object. The metadata classifies this object heuristically as a Data Vault link table. This modeling suggestion reflects the fact that the table records an association between two currency entities rather than describing a single attribute of one entity: OLD_CURRENCY and REPLACEMENT_CURRENCY each act as references into the currency domain, and the row itself captures the relationship.

Key Information Stored

Of the nine documented columns, the business content is carried by four:

• OLD_CURRENCY (VARCHAR2(15)) — the currency being phased out. This column is the subject of the unique index GL_FIXED_CONV_RATES_U1, which is the business-key candidate enforcing the rule that each old currency appears only once and therefore maps to a single replacement.
• REPLACEMENT_CURRENCY (VARCHAR2(15)) — the successor currency. It is indexed by the non-unique index GL_FIXED_CONV_RATES_N1, supporting lookups in the reverse direction. The metadata further constrains the model so that a currency appearing as a replacement should not also appear as an old currency.
• FIXED_CONVERSION_RATE (NUMBER) — the fixed multiplier from the old currency to the replacement currency.
• EFFECTIVE_START_DATE (DATE) — the date from which the fixed-rate relationship is valid.

Although the physical primary key constraint GL_FIXED_CONV_RATES_PK is documented on OLD_CURRENCY, there is no separate surrogate key column; the old currency code itself serves as the unique identifier, while OLD_CURRENCY and REPLACEMENT_CURRENCY together constitute the link's two business references. The remaining columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — are standard Who columns recording audit and session context.

Common Use Cases and Queries

Typical usage involves resolving a fixed rate during currency conversion, validating that a redenomination setup is complete, and auditing which currencies have been phased out and when. A common pattern joins both currency columns to FND_CURRENCIES to retrieve descriptive names:

• Rate lookup for a specific pair: SELECT FIXED_CONVERSION_RATE FROM GL_FIXED_CONV_RATES WHERE OLD_CURRENCY = :old AND REPLACEMENT_CURRENCY = :new AND EFFECTIVE_START_DATE <= :as_of;
• Reverse resolution using the N1 index: filter on REPLACEMENT_CURRENCY to find the originating legacy currency.
• Setup validation: confirm no currency is both an OLD_CURRENCY and a REPLACEMENT_CURRENCY, using a self-join or INTERSECT between the two columns.
• Reporting: join to FND_CURRENCIES on both OLD_CURRENCY and REPLACEMENT_CURRENCY to present user-friendly currency names alongside the rate and effective date.

Related Objects

The documented FK relationships tie OLD_CURRENCY and REPLACEMENT_CURRENCY to FND_CURRENCIES, the central currency definition table, which is the most significant related object. The table also exposes the database trigger GL_FIXED_CONV_RATES# (the "#" form denotes the underlying trigger package generated for the table), which is referenced by the object itself. For conversion-rate processing, related GL objects include the currency and rate tables that supply daily and spot rates, and the General Ledger conversion APIs that consume fixed rates when translating balances between the old and replacement currencies. Because the table references FND_CURRENCIES and holds only nine columns, the practical join surface is narrow: FND_CURRENCIES for both currency keys, and the GL conversion routines that apply FIXED_CONVERSION_RATE during redenomination processing.