Search Results gl_cross_rate_rules_dtls_pk

Overview

GL_CROSS_RATE_RULE_DTLS is a General Ledger (GL) table in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. It stores the line-level detail records that define cross currency rate rules used by the GL currency conversion engine. Cross rate rules allow an organization to specify explicit conversion relationships between a from currency and a to currency under a named conversion type, rather than relying solely on the default triangulation logic that derives a rate through the functional currency.

The table acts as a child of GL_CROSS_RATE_RULES. Where the parent defines the rule header, this detail table enumerates the individual currency pair mappings that belong to each rule and the enablement status of each pair. From a heuristic Data Vault modeling perspective, the table can be classified as a link entity: it connects the conversion-type rule header with the FND_CURRENCIES reference entities for the from and to currencies, capturing the relationships between them.

Key Information Stored

The physical schema documents nine columns. The most significant are:

• CONVERSION_TYPE — Identifies the conversion type to which the detail line belongs; part of the composite primary key and foreign key to GL_CROSS_RATE_RULES.
• FROM_CURRENCY — The source currency code for the cross rate mapping; part of the composite primary key and foreign key to FND_CURRENCIES.
• TO_CURRENCY — The target currency code; part of the composite primary key and foreign key to FND_CURRENCIES.
• ENABLED_FLAG — Indicates whether the specific currency pair detail line is active for use in rate resolution.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle WHO-audit columns recording creation and modification metadata.

The documented surrogate-free composite primary key is GL_CROSS_RATE_RULES_DTLS_PK on (CONVERSION_TYPE, FROM_CURRENCY, TO_CURRENCY). A unique index, GL_CROSS_RATE_RULES_DTLS_U1, shares the same column set (CONVERSION_TYPE, FROM_CURRENCY, TO_CURRENCY), confirming that the natural business key of a detail line is the conversion type plus the directed currency pair.

Common Use Cases and Queries

Typical scenarios include auditing which currency pairs are configured under a conversion type, verifying enablement status, and tracing the source-to-target mapping used by cross-rate calculations. A representative query joining to the currency reference table follows:

• List enabled pairs for a conversion type:

  SELECT d.CONVERSION_TYPE, d.FROM_CURRENCY, d.TO_CURRENCY, d.ENABLED_FLAG
  FROM   GL_CROSS_RATE_RULE_DTLS d
  WHERE  d.CONVERSION_TYPE = :conv_type
  AND    d.ENABLED_FLAG = 'Y';
  

• Resolve currency names via FND_CURRENCIES:

  SELECT d.FROM_CURRENCY, cf.NAME AS from_name,
         d.TO_CURRENCY,   ct.NAME AS to_name
  FROM   GL_CROSS_RATE_RULE_DTLS d,
         FND_CURRENCIES cf, FND_CURRENCIES ct
  WHERE  d.FROM_CURRENCY = cf.CURRENCY_CODE
  AND    d.TO_CURRENCY   = ct.CURRENCY_CODE;
  

These patterns support configuration reviews, migration validation, and troubleshooting when GL conversion produces unexpected rates because an explicit pair overrides default triangulation.

Related Objects

• GL_CROSS_RATE_RULES — Parent rule header; joined on CONVERSION_TYPE.
• FND_CURRENCIES — Reference table joined on FROM_CURRENCY and again on TO_CURRENCY.
• GL_DAILY_RATES — Rate source consulted for enabled currency pairs defined here.
• GL_CURRENCY_API / GL_CROSS_RATE_API — Public APIs that read rule detail configuration during conversion.

Together these objects form the cross-rate configuration and rate-resolution path within Oracle General Ledger.