Results for “to_currency_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GL_XCHG_RTE is the exchange rate table owned by the GMF schema (Process Manufacturing Financials) within Oracle EBS 12.1.1 and 12.2.2. It stores the daily currency conversion rates used to translate foreign-currency amounts into the functional or reporting currency for process manufacturing transactions and their downstream financial postings. The table is a core reference object: rather than holding transactional detail itself, it supplies the rate factor applied at the point a monetary amount is converted, and it preserves that factor historically by effective date so that historical conversions remain reproducible.

From a Data Vault modeling perspective, the documented metadata classifies this object heuristically as standalone. This suggests the table functions as a reference or lookup construct rather than a true hub, link, or satellite. Because no foreign key relationships were mined, it should be treated as an independently maintained rate repository whose natural business key is defined entirely by its own columns.

Key Information Stored

The table contains 18 documented columns. The most significant are the four that together form the primary key and business key:

• TO_CURRENCY_CODE and FROM_CURRENCY_CODE — the target and source currencies for the conversion pair. Together they identify the direction of the rate.
• RATE_TYPE_CODE — the rate classification (for example, spot, corporate, or user-defined types) that selects which rate set applies.
• EXCHANGE_RATE_DATE — the effective date of the rate, enabling date-effective retrieval of the correct historical conversion factor.
• EXCHANGE_RATE — the numeric conversion factor applied when translating the amount.
• MUL_DIV_SIGN — indicates whether the rate is applied by multiplication or division, essential for correct conversion arithmetic.
• TEXT_CODE — descriptive text associated with the rate record.
• TRANS_CNT — a transaction/usage counter column.
• DELETE_MARK — the soft-delete flag; active records typically carry a zero value.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
• PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — concurrent program and request context columns.

The primary key GL_XCHG_RTE_PK covers TO_CURRENCY_CODE, FROM_CURRENCY_CODE, RATE_TYPE_CODE, and EXCHANGE_RATE_DATE. Because this unique index also constitutes the business-key candidate, the table employs no separate surrogate key; the composite business columns serve directly as the identifier.

Common Use Cases and Queries

Typical usage centers on retrieving the correct rate for a currency pair, rate type, and date. A representative query pattern is:

• SELECT exchange_rate, mul_div_sign FROM gl_xchg_rte WHERE from_currency_code = :p_from AND to_currency_code = :p_to AND rate_type_code = :p_type AND exchange_rate_date = :p_date AND delete_mark = 0;
• Reporting of rate maintenance activity: SELECT from_currency_code, to_currency_code, rate_type_code, exchange_rate, exchange_rate_date, last_updated_by, last_update_date FROM gl_xchg_rte ORDER BY exchange_rate_date DESC;
• Audit of rate changes by concurrent request: filtering on PROGRAM_ID, REQUEST_ID, or PROGRAM_UPDATE_DATE to trace which process inserted or modified rates.
• Detection of gaps or duplicate rate definitions across a date range, useful for reconciliation prior to period-close currency translation runs.

Related Objects

Because the metadata documents no foreign keys and classifies the object as standalone, dependencies are behavioral rather than structural. The most significant related objects include:

• GL_DAILY_RATES — the standard General Ledger rate table that supplies the equivalent rates used in financial conversions; GMF rates are commonly reconciled against it.
• FND_CURRENCIES — validates the TO_CURRENCY_CODE and FROM_CURRENCY_CODE values.
• GL_DAILY_CONVERSION_TYPES — validates RATE_TYPE_CODE against defined conversion types.
• GMF periodic costing and translation processes — consume these rates during cost rollup and currency revaluation.
• Standard audit columns join to FND_CONCURRENT_REQUESTS via REQUEST_ID and to FND_USER via CREATED_BY / LAST_UPDATED_BY for lineage reporting.