Search Results gl_daily_rates_interface




Overview
Explore in AI Chat

Overview

The GL_DAILY_RATES_INTERFACE table is a core staging table within the Oracle E-Business Suite General Ledger (GL) module, serving as the primary data interface for importing daily currency conversion rates. Its fundamental role is to act as a temporary holding area for rate data before it is validated and processed into the permanent GL_DAILY_RATES table. This interface-driven architecture is standard in Oracle EBS, allowing for bulk data loading from external systems or spreadsheets while ensuring data integrity through the application's business logic before final commitment. The table is critical for multinational organizations that require accurate and up-to-date exchange rates for transactional currency conversion, translation, and revaluation processes in releases 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is designed to capture the essential attributes of a currency conversion rate. Its primary key, GL_DAILY_RATES_INTERFACE_PK, is a composite key consisting of FROM_CURRENCY, TO_CURRENCY, FROM_CONVERSION_DATE, TO_CONVERSION_DATE, and USER_CONVERSION_TYPE. This ensures unique rate definitions for a specific currency pair, date range, and rate type within the interface. Key columns include FROM_CURRENCY and TO_CURRENCY (foreign keys to FND_CURRENCIES), defining the conversion pair. The FROM_CONVERSION_DATE and TO_CONVERSION_DATE columns establish the effective date range for the rate. The USER_CONVERSION_TYPE specifies the type of rate (e.g., Corporate, Spot). Other critical columns typically include the CONVERSION_RATE itself, the USER_ID (foreign key to FND_USER) who submitted the data, and status columns like STATUS_CODE to track the success or failure of the import process.

Common Use Cases and Queries

The primary use case is the batch import of new or updated daily rates via a concurrent program, such as "Daily Rates Interface," which validates and transfers data from this interface table. Common operational queries involve monitoring the interface for errors. A typical diagnostic query would select records with a STATUS_CODE indicating an error, along with associated error message columns, to facilitate troubleshooting. For example:

SELECT from_currency, to_currency, conversion_rate, status_code, error_message FROM gl_daily_rates_interface WHERE status_code = 'E';

Another common pattern is to check for duplicate rate submissions before launching the import process by querying for overlapping date ranges for the same currency pair and conversion type. Reporting use cases often involve joining this table with FND_CURRENCIES to get currency names for more readable audit reports of what rates were submitted in a given batch.

Related Objects

  • GL_DAILY_RATES: The ultimate target table where validated rates are stored for use by all EBS applications.
  • FND_CURRENCIES: Referenced by foreign key constraints on FROM_CURRENCY and TO_CURRENCY to validate currency codes.
  • FND_USER: Referenced by foreign key on USER_ID to identify the submitter.
  • Concurrent Program: The "Daily Rates" or "Daily Rates Interface" concurrent program is the engine that processes records from this interface table.
  • Open Interface API: While often loaded via SQL*Loader or ADFdi, programmatic inserts can leverage underlying PL/SQL API logic for validation.