Search Results rcv_mc_transactions_u1

Overview

PO.RCV_MC_TRANSACTIONS is the Multiple Reporting Currencies (MRC) sub-table associated with RCV_TRANSACTIONS, the core Receiving transaction table in Oracle E-Business Suite. The MRC architecture allows a single transaction to be recorded in the functional (primary) set of books while simultaneously reporting its equivalent amounts in one or more additional reporting sets of books. RCV_MC_TRANSACTIONS stores the currency conversion attributes — conversion type, conversion date, and conversion rate — required to translate each receiving transaction into each associated reporting set of books. It resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and is owned by the PO schema. The FND Design Data registration PO.RCV_MC_TRANSACTIONS confirms it as a recognized application object in both 12.1.1 and 12.2.2.

From a heuristic Data Vault modeling perspective, and as a modeling suggestion only, this table qualifies as a satellite. Its key structure — a composite of SET_OF_BOOKS_ID and TRANSACTION_ID — attaches descriptive, context-dependent conversion attributes to the hub record identified by TRANSACTION_ID, with SET_OF_BOOKS_ID providing the multi-tenant reporting dimension. No outbound foreign key dependencies are documented, so the relationship to the parent transaction is maintained by application logic rather than by declarative referential integrity.

Key Information Stored

The table contains five documented columns. The physical primary key, RCV_MC_TRANSACTIONS_PK, is the composite of SET_OF_BOOKS_ID and TRANSACTION_ID. A second unique index, RCV_MC_TRANSACTIONS_U1, is defined on the same two columns in reversed order — TRANSACTION_ID then SET_OF_BOOKS_ID — making it the documented business-key candidate and the index most commonly cited in query hints and tuning discussions. The most important columns are:

• SET_OF_BOOKS_ID — the reporting set of books identifier; a mandatory NUMBER(15) and half of the primary key.
• TRANSACTION_ID — the receiving transaction identifier linking back to the parent transaction; a mandatory NUMBER(15) and the other half of the primary key.
• CURRENCY_CONVERSION_TYPE — VARCHAR2(30) holding the conversion type used to derive the reporting-currency exchange rate, such as Spot, Corporate, or User-defined.
• CURRENCY_CONVERSION_DATE — the effective DATE of the exchange rate, which governs which daily rate is applied.
• CURRENCY_CONVERSION_RATE — the numeric rate applied to convert the transactional currency amount into the reporting currency amount.

Common Use Cases and Queries

The table is primarily queried during MRC reconciliation, reporting-set reporting, and exchange-rate audit. A standard pattern joins the MRC sub-table to its parent transaction by TRANSACTION_ID and filters on a target set of books:

• SELECT TRANSACTION_ID, CURRENCY_CONVERSION_RATE FROM PO.RCV_MC_TRANSACTIONS WHERE SET_OF_BOOKS_ID = :p_sob_id; — retrieve conversion details for one reporting set of books.
• Join to the parent by TRANSACTION_ID to compare reporting-currency and functional-currency amounts for a receipt.
• Aggregate by CURRENCY_CONVERSION_TYPE to verify that the correct rate source was applied across a period.
• Use CURRENCY_CONVERSION_DATE to audit rate selection when period-end rates differ from transaction-date rates.

Because the RCV_MC_TRANSACTIONS_U1 index leads with TRANSACTION_ID, queries filtering on that column alone benefit from an index range scan.

Related Objects

The most significant associated objects are:

• RCV_TRANSACTIONS — the parent transactional table; joined on TRANSACTION_ID.
• RCV_SHIPMENT_HEADERS — receipt header context, related through the transaction lineage.
• RCV_MC_SHIPMENT_HEADERS — the parallel MRC sub-table for shipment and receipt headers.
• GL_SETS_OF_BOOKS — provides the reporting set of books reference for SET_OF_BOOKS_ID.
• FND_CURRENCIES and GL_DAILY_CONVERSION_TYPES — source the currencies and conversion types represented in the rate columns.

The documented dependency section records no outbound references from RCV_MC_TRANSACTIONS and records only the table itself as a dependent, confirming its role as a leaf-level satellite maintained by the Receiving application and its MRC processes.