Results for “ar_distributions_all_mrc_v”

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

Overview

The AR_DISTRIBUTIONS_ALL_MRC_V view in the APPS schema presents accounting distribution records for Oracle Receivables transactions in a multiple reporting currency (MRC) context. It exposes the accounted and entered debit and credit amounts for receipt-related accounting entries across multiple sets of books, enabling reconciliation and reporting against secondary ledgers. The view is owned by APPS and carries a VALID status in Oracle EBS 12.1.1 and 12.2.2, and it belongs to the Receivables (AR) product family. Its central purpose is to filter the underlying MRC distributions to the set of books defined in the session, which is particularly relevant for installations that maintain multiple reporting currencies before the introduction of the full Subledger Accounting / secondary ledger framework.

Underlying Base Objects

The view is defined over a single documented base object, AR_MC_DISTRIBUTIONS_ALL (referenced through a SYNONYM), and selects from the alias MC in the underlying view text. The defining query joins no additional tables; instead, it applies a runtime predicate that restricts returned rows by SET_OF_BOOKS_ID. Specifically, the WHERE clause filters records where SET_OF_BOOKS_ID equals NVL(TO_NUMBER(SUBSTRB(USERENV('CLIENT_INFO'), 45, 10)), -99). This construct reads a set-of-books identifier from the client information string and defaults to -99 when no value is present, so the view returns only distributions belonging to the active reporting set of books. Because it maps almost one-to-one to the base table columns, the view is essentially a security- and context-filtered projection of AR_MC_DISTRIBUTIONS_ALL.

Key Columns

The view exposes the full accounting attribute set of the MRC distributions table. The columns most directly associated with the user's search term include AMOUNT_DR, AMOUNT_CR, ACCTD_AMOUNT_DR, and ACCTD_AMOUNT_CR. ACCTD_AMOUNT_CR holds the accounted credit amount for the reporting currency, expressed in the functional currency of the set of books identified by SET_OF_BOOKS_ID, and is complemented by ACCTD_AMOUNT_DR for debits. AMOUNT_DR and AMOUNT_CR represent the entered amounts. Tax-related figures are available through TAXABLE_ENTERED_DR, TAXABLE_ENTERED_CR, TAXABLE_ACCOUNTED_DR, and TAXABLE_ACCOUNTED_CR. Additional columns include LINE_ID and SOURCE_ID for record identity, SOURCE_TABLE and SOURCE_TYPE to identify the originating transaction, CODE_COMBINATION_ID for the accounting flexfield, ORG_ID for multi-org context, and a range of secondary identifiers such as SOURCE_TABLE_SECONDARY, SOURCE_ID_SECONDARY, SOURCE_TYPE_SECONDARY, and REVERSED_SOURCE_ID. Currency conversion is captured through CURRENCY_CODE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_TYPE, and CURRENCY_CONVERSION_DATE. Tax linkage is supported via TAX_LINK_ID, TAX_CODE_ID, TAX_GROUP_CODE_ID, and third-party references through THIRD_PARTY_ID and THIRD_PARTY_SUB_ID.

Common Use Cases and Queries

Typical scenarios include reconciling receipt accounting entries across reporting sets of books, validating accounted credit totals for a reporting currency, and extracting tax distributions for reporting. A representative query aggregating accounted credits by source is:

• SELECT source_type, currency_code, SUM(acctd_amount_cr) FROM ar_distributions_all_mrc_v GROUP BY source_type, currency_code;
• SELECT line_id, source_id, code_combination_id, acctd_amount_dr, acctd_amount_cr FROM ar_distributions_all_mrc_v WHERE set_of_books_id = :p_sob_id AND acctd_amount_cr <> 0;
• SELECT taxable_accounted_dr, taxable_accounted_cr FROM ar_distributions_all_mrc_v WHERE tax_link_id IS NOT NULL;

Because the query filters on SET_OF_BOOKS_ID read from the client information context, callers must ensure that the session context is correctly initialized, otherwise the default value of -99 may suppress all rows. In Oracle EBS 12.2.2 environments migrating toward Subledger Accounting and secondary ledgers, this view remains useful for historical MRC data and for reports that predate the SLA architecture.