Search Results ar_mc_batches_u1

Overview

The AR.AR_MC_BATCHES table is a Multiple Reporting Currencies (MRC) subtable within the Oracle Receivables (AR) module. It stores currency-related information about receipt batches for each reporting set of books associated with a parent record in the AR_BATCHES_ALL table. In Oracle EBS 12.1.1 and 12.2.2, MRC functionality enables organizations to maintain accounting records in multiple currencies simultaneously, and AR_MC_BATCHES serves as the currency-translation extension for Receivables batch processing.

The object resides in the AR schema under the FND Design Data designation AR.AR_MC_BATCHES and has a status of VALID. Its physical storage is allocated to the APPS_TS_TX_DATA tablespace with a PCT Free of 10, while its unique index AR_MC_BATCHES_U1 is stored separately in APPS_TS_TX_IDX — a standard separation of transactional data from index structures in EBS deployments.

From a heuristic Data Vault modeling perspective, AR_MC_BATCHES exhibits the characteristics of a satellite. It does not introduce an independent business key of its own; instead, it hangs off the parent AR_BATCHES_ALL record, carrying descriptive and translation attributes (exchange rate, exchange date, rate type) that describe the parent batch within a specific reporting set of books context. The composite of BATCH_ID and SET_OF_BOOKS_ID functions as the satellite's driving key, identifying the parent hub record (the batch) and the additional context (the reporting ledger).

Key Information Stored

The table is physically documented with five columns, and the most significant are described below.

• BATCH_ID (NUMBER, 15) — Mandatory. Identifier of the payment batch. This is one half of the composite unique key and the foreign key pointing back to AR_BATCHES_ALL. It is the primary linkage between the MRC record and its transactional parent.
• SET_OF_BOOKS_ID (NUMBER, 15) — Mandatory. Identifier of the General Ledger Set of Books associated with the batch. This is the second half of the composite unique key and the foreign key to GL_SETS_OF_BOOKS. It determines which reporting currency context the record describes.
• EXCHANGE_RATE (NUMBER) — The currency conversion rate used to convert the transactional currency amount into the reporting currency amount.
• EXCHANGE_DATE (DATE) — The currency conversion date applied when converting the transactional currency amount into the reporting currency amount.
• EXCHANGE_RATE_TYPE (VARCHAR2, 30) — The currency conversion type (for example, a daily, corporate, or user-defined rate type) used for the conversion.

The unique index AR_MC_BATCHES_U1 (BATCH_ID, SET_OF_BOOKS_ID) is the business-key candidate: it guarantees that a given batch has at most one MRC translation record per reporting set of books. There is no separate single-column surrogate primary key documented; the composite unique index effectively serves that role.

Common Use Cases and Queries

AR_MC_BATCHES is most commonly queried when reconciling reporting-currency amounts for Receivables batches, auditing exchange rate application, or building multi-currency reporting extracts. A typical pattern joins the MRC record back to its parent batch and to the set of books to present readable reporting context:

• Retrieving all MRC translation rows for a specific batch across reporting books — filter on BATCH_ID.
• Comparing the translation rate and rate type actually stored against the rate expected for a given EXCHANGE_DATE.
• Producing a per-book listing of batches, showing SET_OF_BOOKS_ID alongside the rate used, for FX audit trails.

The simplest query pattern is the documented select against the five columns. A more practical reporting join combines the MRC row with the parent batch and the ledger:

• SELECT BATCH_ID, SET_OF_BOOKS_ID, EXCHANGE_RATE, EXCHANGE_DATE, EXCHANGE_RATE_TYPE FROM AR.AR_MC_BATCHES;
• Join AR.AR_MC_BATCHES to AR.AR_BATCHES_ALL on BATCH_ID, and to GL.GL_SETS_OF_BOOKS on SET_OF_BOOKS_ID, when the reporting ledger name is required.

Related Objects

The ETRM metadata documents the following reference relationships. AR_MC_BATCHES does not itself reference any database object within the extract, but it is referenced by and linked to the following significant objects.

• AR.AR_BATCHES_ALL — The parent transactional table. AR_MC_BATCHES.BATCH_ID references AR_BATCHES_ALL, and the MRC subtable extends each parent batch with per-reporting-book currency information.
• GL.GL_SETS_OF_BOOKS — AR_MC_BATCHES.SET_OF_BOOKS_ID references GL_SETS_OF_BOOKS, establishing which reporting set of books the translation applies to.
• APPS.AR_MC_BATCHES — The APPS synonym/view layer that exposes the AR-owned table to application code and end-user queries.

Because AR_MC_BATCHES is an MRC subtable, code and reports that manipulate Receivables batches in a multi-currency environment typically touch it indirectly through the shared MRC maintenance logic that keeps the parent AR_BATCHES_ALL row and its reporting-currency children synchronized.