Search Results first_posted_record_flag




Overview
Explore in AI Chat

Overview

AR_TRX_HISTORY_ALL_MRC_V is a multi-reporting-currency (MRC) view owned by the APPS schema within the Oracle Receivables (AR) module. It exposes the transaction history records of Receivables transactions as they exist across multiple sets of books, joining the primary transaction history data to its reporting-currency counterpart. The "_MRC" suffix identifies the object as part of Oracle's Multi-Reporting Currency architecture, which permits a single transaction to be represented in more than one set of books within a single operating unit. For installations running Oracle E-Business Suite 12.1.1 or 12.2.2, this view serves reporting, reconciliation, and integration functions where the accounting representation of a Receivables transaction history must be evaluated against the reporting set of books selected at runtime.

The column list includes PRV_TRX_HISTORY_ID (the previous transaction history identifier), a foreign key linking each history record to the transaction history row from which it originated. This column is frequently the subject of user searches because it identifies the prior state of a transaction in audit and history investigations.

Underlying Base Objects

The view is defined over two synonyms documented in ETRM 12.2.2:

  • AR_TRANSACTION_HISTORY_ALL – the primary source, referenced as the alias PRIMARY. It supplies transaction history rows across operating units (indicated by the ORG_ID column).
  • AR_MC_TRANSACTION_HISTORY – the multiple-reporting-currency companion table, referenced as the alias MC. It supplies posting control and reporting-currency values.

The two objects are joined on TRANSACTION_HISTORY_ID, and the reporting set of books is filtered by matching MC.SET_OF_BOOKS_ID against the value returned from USERENV('CLIENT_INFO') at offset 45, ten bytes wide, defaulting to -99 if unavailable. This confirms the view is intended for multi-org, MRC-enabled environments where the active set of books is derived from the client environment rather than supplied as a bind variable.

Key Columns

Common Use Cases and Queries

Typical uses include reconciliation of transaction history across sets of books, audit reconstruction of a transaction's status transitions, and reporting where posting control and GL-posted information must be shown per reporting currency.

Retrieving the history chain for a specific Receivables transaction:

  • SELECT transaction_history_id, prv_trx_history_id, event, status, trx_date, gl_date, gl_posted_date, current_record_flag FROM ar_trx_history_all_mrc_v WHERE customer_trx_id = :trx_id ORDER BY transaction_history_id;

Identifying the predecessor of a record using the searched column:

  • SELECT transaction_history_id, prv_trx_history_id, status, event FROM ar_trx_history_all_mrc_v WHERE prv_trx_history_id = :history_id;

Isolating postable history rows for a given operating unit and accounting period:

  • SELECT transaction_history_id, customer_trx_id, gl_date, posting_control_id FROM ar_trx_history_all_mrc_v WHERE org_id = :org_id AND postable_flag = 'Y' AND gl_date BETWEEN :from_date AND :to_date;

Because the view filters on the MRC set of books derived from USERENV('CLIENT_INFO'), queries must be executed in an initialization context where the client information is correctly populated; otherwise the default value of -99 applies and no MRC rows are returned.