Search Results rcv_transactions_mrc_v




Overview
Explore in AI Chat

Overview

RCV_TRANSACTIONS_MRC_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, catalogued under the PO – Purchasing product family. In the ETRM metadata it carries the description "Retrofitted," indicating that the object was re-created or re-pointed as part of an upgrade or patch cycle, a common characteristic of multi-reporting-currency (MRC) objects maintained during the 12.1.1 to 12.2.2 release transitions.

The view exposes receiving transaction data alongside multiple-reporting-currency conversion attributes. It is a currency-aware companion to the transactional receiving tables, presenting the base receipt or delivery record together with the conversion type, conversion date, and conversion rate used to translate the transaction amount into a reporting currency. The presence of both source-level price columns (PO_UNIT_PRICE) and MRC-prefixed conversion columns (MRC_CURRENCY_CONVERSION_TYPE, MRC_CURRENCY_CONVERSION_DATE, MRC_CURRENCY_CONVERSION_RATE, AMOUNT_BILLED) makes the view suitable for financial reconciliation, accrual analysis, and multi-currency receipt reporting. It is typically used for inquiry and reporting rather than for transactional DML.

Notably, the view exposes INSPECTION_STATUS_CODE, the receipt inspection state of the transaction, which is the column most frequently searched by users. This makes the view relevant to quality and receiving teams querying inspection disposition across currencies.

Underlying Base Objects

The documented base objects underpinning this view are:

  • RCV_TRANSACTIONS (accessed via a synonym) — the core receiving transaction table holding receipt, delivery, return, and correction records.
  • RCV_MC_TRANSACTIONS (accessed via a synonym) — the multiple-reporting-currency extension table supplying the MRC conversion columns.

The view text indicates a join between the core transaction rows (aliased PO) and the MRC rows (aliased MC), with the conversion attributes drawn from the MRC source and the operational attributes drawn from the base transaction. Because both are referenced as synonyms, the physical tables reside in the RCV schema while the view is owned by APPS. The view effectively flattens the one-to-many relationship between a receiving transaction and its multiple currency conversions into a single currency-oriented projection.

Key Columns

Common Use Cases and Queries

A primary use case is reporting receiving activity filtered by inspection status while retaining currency conversion context, for example:

  • Receipts awaiting inspection, to support quality backlog reporting.
  • Reconciliation of receipt quantities and billed amounts across reporting currencies.
  • Accrual and exception analysis for uninvoiced or exception-flagged receipts.

Sample query filtering on the searched column:

  • SELECT transaction_id, transaction_type, transaction_date, quantity, uom_code, inspection_status_code, currency_code, mrc_currency_conversion_rate, amount_billed FROM apps.rcv_transactions_mrc_v WHERE inspection_status_code = 'PENDING' AND organization_id = :org_id;
  • SELECT po_header_id, po_line_id, inspection_status_code, SUM(quantity) FROM apps.rcv_transactions_mrc_v WHERE transaction_date BETWEEN :start_date AND :end_date GROUP BY po_header_id, po_line_id, inspection_status_code;

Because the view spans both operational and currency-mapped data, it is best treated as a read-only reporting source, consistent with its retrofitted MRC role in the PO/Purchasing reporting layer.