Search Results interface_header_context




Overview

The view RA_CUSTOMER_TRX_ALL_MRC_V is a Multi-Reporting Currency (MRC) view owned by the APPS schema within the Oracle Receivables (AR) product. It provides a consolidated presentation of customer transaction header information drawn from the transactional base table and its associated multiple reporting currency records. The view exposes the full set of transaction header attributes—transaction numbers, dates, customer and site identifiers, agreement and commitment data, printing metadata, descriptive flexfield attributes, and interface attributes—alongside the currency conversion columns that distinguish each reporting set of books.

The presence of SET_OF_BOOKS_ID, EXCHANGE_RATE_TYPE, EXCHANGE_DATE, and EXCHANGE_RATE confirms that this view is designed to surface the same logical transaction under each reporting currency in which it has been recorded, enabling reporting and integration processes to operate in the appropriate ledger context. In EBS release 12.1.1 and 12.2.2, MRC views of this type remain relevant for organizations that maintain secondary ledgers through the Multiple Reporting Currencies architecture, and they are frequently leveraged when the reporting requirement spans more than one functional currency.

Underlying Base Objects

The ETRM metadata for release 12.2.2 documents two underlying references for this view: RA_CUSTOMER_TRX_ALL and RA_MC_CUSTOMER_TRX, both accessed through synonyms. Functionally, the view joins the primary transaction record in RA_CUSTOMER_TRX_ALL to the reporting-currency transaction record in RA_MC_CUSTOMER_TRX on the shared customer transaction identifier, using PRIMARY.CUSTOMER_TRX_ID as the linkage key. The primary table supplies the transaction’s defining identity and attributes, while the MC table contributes the set-of-books context and the currency conversion parameters (rate type, exchange date, and exchange rate) applicable to each reporting currency.

Key Columns

Common Use Cases and Queries

This view is commonly used to report customer transactions across multiple reporting currencies, to reconcile transaction amounts by ledger, and to feed downstream integrations that must operate in a specific set of books. A user searching on remittance_batch_id is typically investigating how transactions are grouped for remittance processing; while the documented column list of this view does not include REMITTANCE_BATCH_ID, remittance batch association is generally held on receipt or transaction-line level objects rather than the transaction header, so this view would be coupled with those objects to trace a transaction to its remittance batch.

A representative query filters by ledger and date range:

  • SELECT customer_trx_id, trx_number, trx_date, set_of_books_id, invoice_currency_code, exchange_rate, complete_flag
  • FROM ra_customer_trx_all_mrc_v
  • WHERE set_of_books_id = :p_sob_id
  • AND trx_date BETWEEN :p_from_date AND :p_to_date;

To investigate remittance grouping, the result set is joined to the appropriate receipt or batch-related objects using CUSTOMER_TRX_ID as the linking key. All access should be performed under a responsibility with sufficient Receivables query privileges.