Search Results ar_mc_cash_receipt_hist




Overview
Explore in AI Chat

Overview

The AR_MC_CASH_RECEIPT_HIST table is a core data object within the Oracle E-Business Suite Receivables (AR) module, specifically designed to support multiple reporting currencies. It stores currency-specific transactional history for each step in a cash receipt's life cycle, recorded for each designated reporting set of books. This table is essential in deployments where legal or management reporting requires financial records to be maintained in currencies different from the primary transactional currency. It operates as a detailed subsidiary ledger, ensuring a complete audit trail of currency conversions, gains, and losses associated with receipt activities—such as application, reversal, or unapplication—across all reporting ledgers.

Key Information Stored

The table's structure centers on linking receipt history events to specific reporting ledgers and capturing the resulting monetary amounts. Its primary key is a composite of CASH_RECEIPT_HISTORY_ID and SET_OF_BOOKS_ID, enforcing uniqueness per history event per reporting ledger. Critical columns include CASH_RECEIPT_HISTORY_ID, which links to the base transaction history in AR_CASH_RECEIPT_HISTORY_ALL, and SET_OF_BOOKS_ID, which references the reporting ledger in GL_SETS_OF_BOOKS. The table stores the CASH_RECEIPT_ID to tie data to the original receipt. Currency amount columns (e.g., AMOUNT, ACCTD_AMOUNT) hold the converted values for the reporting ledger. The POSTING_CONTROL_ID and REVERSAL_POSTING_CONTROL_ID columns are vital for tracking the General Ledger transfer status of these amounts, linking to the AR_POSTING_CONTROL table.

Common Use Cases and Queries

This table is primarily queried for multi-currency financial reporting, reconciliation, and audit purposes. A common use case is generating a report of all receipt applications in a specific reporting currency for a period. Analysts also query it to investigate foreign exchange gains or losses realized during receipt applications across different ledgers. A typical reporting query joins to the base history and receipts tables to provide context.

SELECT mc.cash_receipt_id,
       mc.set_of_books_id,
       mc.amount,
       mc.acctd_amount,
       h.status
  FROM ar_mc_cash_receipt_hist mc,
       ar_cash_receipt_history_all h
 WHERE mc.cash_receipt_history_id = h.cash_receipt_history_id
   AND mc.set_of_books_id = :reporting_sob_id
   AND h.trx_date BETWEEN :p_start_date AND :p_end_date;

Another critical use case is reconciling the AR subledger to the General Ledger for a reporting currency, using the POSTING_CONTROL_ID to identify posted versus unposted entries.

Related Objects

The AR_MC_CASH_RECEIPT_HIST table maintains defined foreign key relationships with several core Receivables and General Ledger tables, forming an integral part of the subledger accounting architecture.

  • AR_CASH_RECEIPT_HISTORY_ALL: Linked via CASH_RECEIPT_HISTORY_ID. This is the primary relationship, where each row in the multi-currency table corresponds to a specific lifecycle event (history) of a receipt.
  • GL_SETS_OF_BOOKS: Linked via SET_OF_BOOKS_ID. This identifies the specific reporting ledger for which the currency conversion data is stored.
  • AR_CASH_RECEIPTS_ALL: Linked via CASH_RECEIPT_ID. This provides a direct link to the master receipt record.
  • AR_POSTING_CONTROL: Linked via POSTING_CONTROL_ID and REVERSAL_POSTING_CONTROL_ID. These relationships track the batch posting status of the accounting entries generated from this multi-currency data to the General Ledger.