Search Results ar_mc_transaction_history




Overview
Explore in AI Chat

Overview

The AR_MC_TRANSACTION_HISTORY table is a core data object within the Oracle E-Business Suite Receivables (AR) module, specifically designed to support the Multi-Currency (MC) and Multi-Reporting Ledger architecture. Its primary role is to store posting-related information for transaction history lines, such as invoices and credit memos, for each reporting set of books associated with a primary transaction. This table is essential for maintaining accurate financial records across different reporting currencies and accounting representations, enabling statutory and management reporting in compliance with various international accounting standards. It acts as a child table, holding the detailed accounting history generated when transactions are posted to the general ledger for each configured reporting ledger.

Key Information Stored

The table's structure is defined by its foreign key relationships, which highlight the critical data points it manages. Each record links a transaction history line to a specific reporting set of books. Key columns include TRANSACTION_HISTORY_ID, which references the parent record in AR_TRANSACTION_HISTORY_ALL, and CUSTOMER_TRX_ID, linking to the source transaction in RA_CUSTOMER_TRX_ALL. The SET_OF_BOOKS_ID column identifies the specific reporting ledger for which the posting information is stored. Furthermore, the POSTING_CONTROL_ID links to AR_POSTING_CONTROL, which manages the batch posting process status. This table typically stores amounts converted into the reporting ledger's currency, the accounting date in the reporting ledger context, and the status of the posting for that specific ledger.

Common Use Cases and Queries

This table is central to reconciliation and audit reporting across multiple ledgers. A common use case involves tracing the accounting impact of a single invoice across all reporting sets of books. For instance, to retrieve the posted amounts for a specific transaction in every reporting ledger, a query would join AR_MC_TRANSACTION_HISTORY to GL_SETS_OF_BOOKS and AR_TRANSACTION_HISTORY_ALL. Another critical scenario is troubleshooting posting issues; developers or DBAs might query this table to identify transactions where posting to a secondary ledger has failed by checking the status against AR_POSTING_CONTROL. Reporting on unposted items for a specific reporting ledger also relies heavily on this table to filter and isolate data not yet transferred to the general ledger interface.

Related Objects

AR_MC_TRANSACTION_HISTORY is intrinsically linked to several key Receivables and General Ledger tables, as documented in its foreign key constraints. Its primary parent is AR_TRANSACTION_HISTORY_ALL, which holds the main transaction accounting history. It derives its source transaction from RA_CUSTOMER_TRX_ALL. The reporting ledger structure is defined by its link to GL_SETS_OF_BOOKS (or its 11i equivalent, GL_SETS_OF_BOOKS_11I, as noted in the metadata). The posting process is governed by its relationship with AR_POSTING_CONTROL. Consequently, any custom reporting or interface logic involving multi-currency transaction history must account for these relationships to ensure data integrity and completeness across all reporting ledgers.