Search Results rcv_mc_transactions




Overview
Explore in AI Chat

Overview

RCV_MC_TRANSACTIONS is a Multiple Reporting Currencies (MRC) sub-table of RCV_TRANSACTIONS, owned by the PO schema within the Purchasing module of Oracle E-Business Suite. In releases 12.1.1 and 12.2.2, MRC architecture maintains a separate set of accounting books per reporting currency, and each base transaction in the primary ledger is mirrored into a corresponding reporting-currency row. RCV_MC_TRANSACTIONS stores the currency conversion attributes that permit receiving transactions to be reported and accounted in a reporting set of books distinct from the primary ledger.

The table is narrow by design: the documented physical schema contains only five columns. From a Data Vault modeling perspective, the metadata classifies this object heuristically as a standalone structure. This reflects its nature as a satellite-like extension of the receiving transaction entity, carrying the descriptive conversion context for a given reporting book rather than acting as a hub or link in its own right. Analysts constructing a vault model may therefore treat it as a satellite attached to the receiving transaction hub, keyed by reporting book and transaction identifier.

Key Information Stored

The composite primary key, RCV_MC_TRANSACTIONS_PK, is defined over (SET_OF_BOOKS_ID, TRANSACTION_ID). A unique index, RCV_MC_TRANSACTIONS_U1, is documented over the inverse ordering (TRANSACTION_ID, SET_OF_BOOKS_ID); both enforce the same business-key candidate and guarantee a single reporting-currency row per transaction per book. Because the key columns are themselves the business identifiers, the table carries no separate surrogate sequence key.

  • SET_OF_BOOKS_ID — identifies the reporting set of books for which the mirrored row is maintained; part of the primary key and the discriminator that separates one reporting currency from another.
  • TRANSACTION_ID — the receiving transaction identifier inherited from RCV_TRANSACTIONS; part of the primary key and the join vehicle back to the base transaction.
  • CURRENCY_CONVERSION_TYPE — the Oracle General Ledger conversion rate type (for example, Corporate, Spot, or User-defined) applied when translating the receiving transaction into the reporting currency.
  • CURRENCY_CONVERSION_DATE — the effective date used to select the exchange rate for the reporting-currency amount.
  • CURRENCY_CONVERSION_RATE — the numeric rate applied to convert the base-currency receiving amounts into the reporting book currency.

Common Use Cases and Queries

Typical uses include MRC reconciliation, reporting-currency receiving audits, and rate-verification reporting. The most frequent access pattern joins the reporting-currency row back to its base receiving transaction and then to the underlying receipt or shipment.

  • Identify all reporting books that mirror a given transaction:
  • SELECT set_of_books_id, currency_conversion_type, currency_conversion_date, currency_conversion_rate FROM rcv_mc_transactions WHERE transaction_id = :transaction_id;
  • Detect conversion-type anomalies across reporting books:
  • SELECT transaction_id, set_of_books_id, currency_conversion_type FROM rcv_mc_transactions WHERE currency_conversion_type IS NULL;
  • Reconcile rate and date pairs for period-end review by joining to the base table on TRANSACTION_ID and filtering by SET_OF_BOOKS_ID.

Related Objects

The table's relationships are driven by the TRANSACTION_ID foreign key and, indirectly, the reporting set of books.

  • RCV_TRANSACTIONS — the base (primary-ledger) receiving transactions table; join on TRANSACTION_ID = TRANSACTION_ID and align SET_OF_BOOKS_ID with the reporting book.
  • RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES — receipt headers and lines referenced by the base transaction.
  • PO_HEADERS_ALL and PO_LINES_ALL — purchase order context for the receiving transaction.
  • GL_SETS_OF_BOOKS — defines the reporting book identified by SET_OF_BOOKS_ID and its currency.
  • GL_DAILY_CONVERSION_TYPES — validates the CURRENCY_CONVERSION_TYPE and its rate definitions.
  • RCV_TRANSACTIONS_INTERFACE — inbound receiving interface whose base rows are mirrored into the MRC structure on accounting.

Because transactions are mirrored at posting time, this table should be treated as a reading-only reporting companion to RCV_TRANSACTIONS rather than a primary transaction store.