Search Results gl_cross_rate_rules




Overview
Explore in AI Chat

Overview

GL_CROSS_RATE_RULES is a General Ledger configuration table that defines cross rate rules within Oracle EBS 12.1.1 and 12.2.2. Cross rate rules govern how foreign currency conversions are performed when a direct exchange rate between two currencies is unavailable. Rather than requiring an explicit rate for every currency pair, Oracle General Ledger uses a pivot currency and a defined conversion type to triangulate the rate. The CONVERSION_TYPE column links the rule to an Oracle-defined daily conversion rate type, while the PIVOT_CURRENCY column designates the intermediate currency through which all cross rates are calculated, most commonly USD or EUR in multi-currency environments.

In Data Vault modeling terms, the mined foreign key structure suggests this object is satellite-leaning. It carries descriptive and configuration attributes tied to a business key (CONVERSION_TYPE) and references a limited number of parent hubs (GL_DAILY_CONVERSION_TYPES and FND_CURRENCIES) rather than acting as a pure junction between many-to-many entities. The rule set is therefore best understood as an attribute-bearing extension of the conversion type dimension.

Key Information Stored

The table comprises eight documented columns, four of which are standard EBS WHO (Who Columns) audit columns. The most significant columns are:

  • CONVERSION_TYPE — The primary key column (enforced by GL_CROSS_RATE_RULES_PK) and the unique business key candidate (enforced by GL_CROSS_RATE_RULES_U1). It identifies the rate type for which the cross rate rule applies and is the sole component of both the primary key and the unique index.
  • PIVOT_CURRENCY — The intermediate currency used to derive cross rates. This is the operational heart of the rule, determining the triangulation path.
  • DESCRIPTION — Free-text description of the cross rate rule, useful for reporting and audit clarity.
  • LAST_UPDATE_DATE — Timestamp of the most recent modification, used for change tracking and incremental ETL extracts.
  • LAST_UPDATED_BY — The application user ID responsible for the last change.
  • CREATION_DATE — Timestamp when the rule row was first created.
  • CREATED_BY — The application user ID that created the rule.
  • LAST_UPDATE_LOGIN — The login session identifier associated with the last update.

Because CONVERSION_TYPE is both the primary key and a unique index, there is no separate surrogate key; the business key and the physical key coincide, which simplifies joins but requires care when integrating with systems that expect a numeric surrogate.

Common Use Cases and Queries

Cross rate rules are typically reviewed during multi-currency implementations, conversions, and troubleshooting of rate derivation. A common validation query identifies which rules exist and their pivot currencies:

SELECT crr.conversion_type, crr.pivot_currency, crr.description, dct.description rate_type_desc
FROM gl_cross_rate_rules crr, gl_daily_conversion_types dct
WHERE crr.conversion_type = dct.conversion_type;

Reconciliation reporting frequently joins the rule header to its detail rows to confirm the full derivation path:

SELECT h.conversion_type, h.pivot_currency, d.from_currency, d.to_currency
FROM gl_cross_rate_rules h, gl_cross_rate_rule_dtls d
WHERE h.conversion_type = d.conversion_type;

Incremental ETL or audit processes commonly filter on the WHO columns, for example selecting rows where LAST_UPDATE_DATE exceeds a prior load watermark. Validating that a PIVOT_CURRENCY exists and is enabled in FND_CURRENCIES is another routine check, since an inactive pivot currency silently breaks cross rate derivation.

Related Objects

  • GL_DAILY_CONVERSION_TYPES — Parent of GL_CROSS_RATE_RULES via CONVERSION_TYPE; holds the rate type definitions used across General Ledger.
  • FND_CURRENCIES — Parent of GL_CROSS_RATE_RULES via PIVOT_CURRENCY; validates and describes the pivot currency.
  • GL_CROSS_RATE_RULE_DTLS — Child detail table referencing GL_CROSS_RATE_RULES via CONVERSION_TYPE; stores the currency pair combinations that the rule resolves.
  • GL_DAILY_CONVERSION_RATES — Stores the actual daily rates consumed once the cross rate path is resolved.
  • GL_DAILY_RATES / GL_DAILY_RATES_INTERFACE — Rate entry and interface objects that interact with the resolved conversion logic.
  • FND_CURRENCY_API and GL currency conversion APIs — Programmatic consumers that apply cross rate rule logic during journal entry and translation processing.