Results for “ar_mc_cash_receipt_hist”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AR_MC_CASH_RECEIPT_HIST is a Receivables (AR) module table owned by the AR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the Multiple Reporting Currencies (MRC) representation of receipt life-cycle events. Whereas AR_CASH_RECEIPT_HISTORY_ALL records the transactional history of a receipt in the functional currency of the operating unit's ledger, AR_MC_CASH_RECEIPT_HIST persists the corresponding currency-related information for each step in that receipt's life cycle, restated into every reporting set of books assigned to the source ledger. The table is therefore a reporting-currency shadow of the receipt history, providing the amounts, exchange rates, and posting references required to report and reconcile receipt activity in non-functional reporting currencies.

In Data Vault terms, the metadata heuristic classifies this object as a link. This reflects its role as an associative structure that connects a receipt history event to a specific reporting set of books, carrying descriptive and quantitative attributes around that combination. The composite primary key reinforces this interpretation: the table is defined by relationships between a receipt-history event and a ledger, rather than by a single independent business entity.

Key Information Stored

The documented physical schema contains 16 columns. The primary key, AR_CASH_RECEIPT_HIST_PK, is composed of CASH_RECEIPT_HISTORY_ID and SET_OF_BOOKS_ID. A unique index, AR_MC_CASH_RECEIPT_HIST_U1, enforces the same pair of columns, making this composite the business-key candidate and confirming that one reporting-currency row exists per receipt-history event per set of books.

Common Use Cases and Queries

This table is primarily queried for MRC reporting and reconciliation: verifying that receipt posting amounts in a reporting currency agree with the source ledger, tracing the exchange rate and rate type applied at each event, and identifying events that posted to GL (or reversed) by date. A typical join aligns it with the source history and the reporting ledger:

SELECT m.cash_receipt_history_id,
       m.set_of_books_id,
       m.acctd_amount,
       m.exchange_rate,
       m.exchange_rate_type,
       m.gl_posted_date
FROM   ar.ar_mc_cash_receipt_hist m
WHERE  m.cash_receipt_id = :receipt_id
AND    m.set_of_books_id = :reporting_ledger_id;

To compare source and reporting-currency amounts, join on CASH_RECEIPT_HISTORY_ID to AR_CASH_RECEIPT_HISTORY_ALL. To find posting anomalies, filter where FIRST_POSTED_RECORD_FLAG is set and GL_POSTED_DATE is null, or where REVERSAL_POSTING_CONTROL_ID is populated but REVERSAL_GL_POSTED_DATE is null.

Related Objects

  • AR_CASH_RECEIPT_HISTORY_ALL — source transactional history; joined via CASH_RECEIPT_HISTORY_ID. Parent of the receipt-event dimension.
  • AR_CASH_RECEIPTS_ALL — the receipt header; joined via CASH_RECEIPT_ID.
  • GL_SETS_OF_BOOKS — the reporting ledger definition; joined via SET_OF_BOOKS_ID.
  • AR_POSTING_CONTROL — referenced twice, via POSTING_CONTROL_ID and REVERSAL_POSTING_CONTROL_ID, providing posting and reversal accounting context.