Results for “dct_old”

4 results




Overview
Explore in AI Chat

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

Overview

APPS.AR_RGW_RATE_ADJUSTMENTS_V is a reporting and integration view in the Oracle E-Business Suite Receivables (AR) module. Its purpose is to expose exchange rate adjustment records associated with cash receipts, presenting both the raw key values and the user-facing descriptive values for the old and new exchange rate types. The view is owned by the APPS schema and is available in both Oracle EBS 12.1.1 and 12.2.2. It is part of the ETRM (E-Business Suite Technical Reference Manual) catalog and serves as a denormalized read layer over the AR_RATE_ADJUSTMENTS base table, enriching each rate adjustment row with descriptive conversion type names drawn from the General Ledger daily conversion types table.

The view is particularly relevant in the context of foreign currency receipts, where a receipt's exchange rate may be adjusted after the fact, producing a realized gain or loss. By joining to GL_DAILY_CONVERSION_TYPES twice — once for the old rate type and once for the new rate type — the view eliminates the need for report authors and interface developers to perform these lookups themselves. This is the source of the documented alias DCT_NEW, which represents the GL_DAILY_CONVERSION_TYPES instance joined on the new exchange rate type and exposes NEW_EXCHANGE_RATE_TYPE_DSP.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as synonyms in the APPS schema:

  • AR_RATE_ADJUSTMENTS (aliased RADJ) — the primary transaction table holding rate adjustment records keyed by RATE_ADJUSTMENT_ID and linked to a CASH_RECEIPT_ID.
  • GL_DAILY_CONVERSION_TYPES (aliased DCT_OLD and DCT_NEW) — the General Ledger reference table of currency conversion types, joined twice to resolve the user-facing descriptions of the old and new exchange rate types.

The join predicates are equality joins on CONVERSION_TYPE: DCT_NEW.CONVERSION_TYPE = RADJ.NEW_EXCHANGE_RATE_TYPE and DCT_OLD.CONVERSION_TYPE = RADJ.OLD_EXCHANGE_RATE_TYPE. Because these are inner joins, only rate adjustment rows whose old and new rate types both exist in GL_DAILY_CONVERSION_TYPES are returned.

Key Columns

  • ROW_ID — the ROWID of the underlying AR_RATE_ADJUSTMENTS row, useful for updates or drill-back.
  • RATE_ADJUSTMENT_ID — primary identifier of the rate adjustment.
  • CASH_RECEIPT_ID — the cash receipt to which the adjustment applies.
  • OLD_EXCHANGE_RATE / NEW_EXCHANGE_RATE — the exchange rate values before and after adjustment.
  • OLD_EXCHANGE_RATE_TYPE / NEW_EXCHANGE_RATE_TYPE — the internal conversion type codes.
  • OLD_EXCHANGE_RATE_TYPE_DSP / NEW_EXCHANGE_RATE_TYPE_DSP — user-facing conversion type names resolved via DCT_OLD and DCT_NEW.
  • OLD_EXCHANGE_DATE / NEW_EXCHANGE_DATE — effective dates of the respective rates.
  • GAIN_LOSS — the realized gain or loss arising from the adjustment.
  • GL_DATE — the accounting date for the adjustment.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard descriptive flexfield columns for optional, client-defined data.

Common Use Cases and Queries

The view is typically used for reconciliation and audit reporting of currency rate adjustments on receipts, and for feeding downstream integrations that require human-readable conversion type names. A representative query lists adjustments with their descriptive rate types and gain/loss amounts:

  • SELECT RATE_ADJUSTMENT_ID, CASH_RECEIPT_ID, OLD_EXCHANGE_RATE_TYPE_DSP, NEW_EXCHANGE_RATE_TYPE_DSP, GAIN_LOSS, GL_DATE FROM APPS.AR_RGW_RATE_ADJUSTMENTS_V;
  • Filtering by receipt: ... WHERE CASH_RECEIPT_ID = :p_receipt_id.
  • Filtering adjustments by new rate type: ... WHERE NEW_EXCHANGE_RATE_TYPE_DSP = 'Corporate'.
  • Aggregating gain/loss by GL period: SELECT GL_DATE, SUM(GAIN_LOSS) FROM APPS.AR_RGW_RATE_ADJUSTMENTS_V GROUP BY GL_DATE;

Because the view joins only on rate type and performs no functional security or org-based filtering, callers should apply their own ledger, receipt, or date predicates. When the underlying rate type codes are not present in GL_DAILY_CONVERSION_TYPES, the inner joins suppress those rows, so completeness checks should be run against AR_RATE_ADJUSTMENTS when validating the view's output.