Results for “ar_rgw_rate_adjustments_v”

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

Overview

AR_RGW_RATE_ADJUSTMENTS_V is an APPS-owned reporting view in the Oracle Receivables (AR) module. It exposes exchange rate adjustment activity recorded against cash receipts, presenting both the original and revised exchange rate attributes alongside the resulting gain or loss. The object is documented as valid in the ETRM metadata for Release 12.2.2, carrying the original note "(Release 10SC Only)" in its description, which indicates it originated in the older 10SC code line and has been retained as a compatibility view for legacy integrations and reports that continue to reference it.

The view is primarily relevant to multi-currency Receivables operations in Oracle EBS 12.1.1 and 12.2.2, where cash receipts are entered, cleared, or revalued using changing exchange rates. When a rate adjustment is applied, the difference between the old and new converted amounts produces a foreign exchange gain or loss. This view surfaces that adjustment in a denormalized, join-ready form, making it suitable for reporting, reconciliation, and downstream integration. Because it is a view rather than a table, it provides no independent storage; all data is derived at query time from its base objects.

Underlying Base Objects

The view is defined over two documented referenced base objects, both exposed to APPS as synonyms:

• AR_RATE_ADJUSTMENTS (SYNONYM) — the primary Receivables table holding rate adjustment records, aliased RADJ. It supplies all core identifiers, exchange rate values, dates, the gain/loss amount, and the descriptive flexfield attribute columns.
• GL_DAILY_CONVERSION_TYPES (SYNONYM) — the General Ledger conversion type definitions, joined twice as DCT_NEW and DCT_OLD. These joins resolve the stored conversion type codes into user-facing display names for both the new and old exchange rate types.

The join conditions are DCT_NEW.CONVERSION_TYPE = RADJ.NEW_EXCHANGE_RATE_TYPE and DCT_OLD.CONVERSION_TYPE = RADJ.OLD_EXCHANGE_RATE_TYPE. The presence of these inner joins means a row is only returned when both the old and new conversion types exist in GL_DAILY_CONVERSION_TYPES.

Key Columns

• ROW_ID — the RADJ.ROWID pseudo-column, providing a unique row identifier usable for updates or drill-down.
• RATE_ADJUSTMENT_ID — primary key of the underlying rate adjustment record.
• CASH_RECEIPT_ID — identifies the cash receipt to which the adjustment applies, linking the view back to receipt activity.
• OLD_EXCHANGE_RATE / NEW_EXCHANGE_RATE — the previous and revised exchange rates.
• OLD_EXCHANGE_RATE_TYPE / NEW_EXCHANGE_RATE_TYPE — stored conversion type codes.
• OLD_EXCHANGE_RATE_TYPE_DSP / NEW_EXCHANGE_RATE_TYPE_DSP — user conversion type names resolved from GL_DAILY_CONVERSION_TYPES.
• OLD_EXCHANGE_DATE / NEW_EXCHANGE_DATE — effective dates of the respective rates.
• GAIN_LOSS — the foreign exchange gain or loss amount arising from the adjustment; this is the column most directly associated with the "gain_loss" search term.
• GL_DATE — the accounting date for the adjustment.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield columns for supplementary, customer-defined information.

Common Use Cases and Queries

Typical scenarios include reporting realized and unrealized foreign exchange gains and losses on receipts, reconciling rate adjustment entries to the general ledger, and feeding adjustment data into downstream consolidation or treasury systems. A representative query selecting gain/loss activity for a specified receipt follows:

SELECT rate_adjustment_id, cash_receipt_id, old_exchange_rate, new_exchange_rate, gain_loss, gl_date FROM apps.ar_rgw_rate_adjustments_v WHERE cash_receipt_id = :p_receipt_id ORDER BY gl_date;

For aggregate gain/loss analysis by conversion type, the display columns may be used directly:

SELECT new_exchange_rate_type_dsp, SUM(gain_loss) total_gain_loss FROM apps.ar_rgw_rate_adjustments_v WHERE gl_date BETWEEN :p_start AND :p_end GROUP BY new_exchange_rate_type_dsp;

Because the view is read-only in practice and inherited from an older release, deployments should confirm continued validity during upgrades from 12.1.1 to 12.2.2 and consider migrating new development to current Receivables reporting objects where equivalent data is available.