Results for “reversal_comments”

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

Overview

AR_CASH_RECEIPTS_MRC_V is a multi-reporting-currency (MRC) view owned by the APPS schema in Oracle E-Business Suite Receivables. It presents cash receipt data alongside the corresponding reporting-currency equivalent amounts and exchange attributes, allowing receipts entered in a primary functional currency to be viewed per reporting set of books. The view is a join between the base transaction table AR_CASH_RECEIPTS and the MRC table AR_MC_CASH_RECEIPTS, keyed on CASH_RECEIPT_ID and constrained by SET_OF_BOOKS_ID. Because Oracle EBS supports multiple reporting currencies within the same operating unit, this view is the standard mechanism by which subledger data — such as remittance banking, factoring, reversal, and confirmation activity — is queried from a given reporting ledger's perspective. It appears in Receivables inquiry, receipt reversal and remittance-batch reports, and in custom integrations that require reporting-currency receipt amounts. The column SELECTED_REMITTANCE_BATCH_ID, exposed by this view, identifies the remittance batch to which a receipt has been assigned, and is a common search criterion in remittance reconciliation and batch-release queries.

Underlying Base Objects

Per the documented 12.2.2 metadata, the view is defined over two referenced base objects, both exposed as synonyms in APPS:

• AR_CASH_RECEIPTS — the primary (ALIAS: PRIMARY) receipt entity, storing the transaction in the receipt's own currency and ledger context.
• AR_MC_CASH_RECEIPTS — the multi-reporting-currency shadow table, storing the converted amounts, exchange rate, exchange rate type, and exchange date for each reporting set of books (ALIAS: MC).

The join condition is PRIMARY.CASH_RECEIPT_ID = MC.CASH_RECEIPT_ID AND MC.SET_OF_BOOKS_ID = NV, where NV is the session's reporting set of books context (typically populated through an MRC profile or a bind variable in the view definition). Because the view is a straight equi-join on a single primary key with a set-of-books filter, it behaves as a one-row-per-receipt-per-reporting-ledger projection. The SELECT list projected from PRIMARY.CASH_RECEIPT_ID supplies the surrogate key, while MC.CASH_RECEIPT_ID is implied by the join; genuine receipt attributes flow from the primary table and converted values from the MRC table.

Key Columns

• CASH_RECEIPT_ID — primary receipt identifier, shared by both base tables.
• SET_OF_BOOKS_ID — the reporting ledger for which the MRC row is valid.
• AMOUNT, CURRENCY_CODE — converted receipt amount and its currency for that ledger.
• EXCHANGE_RATE_TYPE, EXCHANGE_RATE, EXCHANGE_DATE — conversion attributes applied by the MRC layer.
• RECEIPT_NUMBER, RECEIPT_DATE, TYPE, STATUS, CONFIRMED_FLAG — receipt identity, lifecycle status, and confirmation state.
• RECEIPT_METHOD_ID, REMITTANCE_BANK_ACCOUNT_ID, CUSTOMER_BANK_ACCOUNT_ID — payment method and remittance account associations.
• REVERSAL_DATE, REVERSAL_CATEGORY, REVERSAL_REASON_CODE — reversal detail for receipts that have been reversed.
• SELECTED_REMITTANCE_BATCH_ID — the remittance batch to which the receipt is assigned; NULL when the receipt is unbatched.
• SELECTED_FOR_FACTORING_FLAG, FACTOR_DISCOUNT_AMOUNT — factoring designation and discount.
• ORG_ID — operating unit, supporting multi-org security at query time.
• USSGL_TRANSACTION_CODE, DOC_SEQUENCE_VALUE, VAT_TAX_ID, REFERENCE_TYPE/REFERENCE_ID — accounting, document sequencing, tax, and cross-reference attributes.

Common Use Cases and Queries

Typical usages include reporting-currency receipt registers, remittance-batch membership lookups, factoring candidate selection, and reversal analysis across ledgers. A representative query for the user's search term follows:

SELECT cash_receipt_id, receipt_number, receipt_date,
       amount, currency_code, set_of_books_id,
       selected_remittance_batch_id, org_id
FROM   apps.ar_cash_receipts_mrc_v
WHERE  selected_remittance_batch_id = :batch_id
AND    org_id = :org_id;

Receipts can be listed by reporting ledger and status, joined to AR_CASH_RECEIPT_HISTORY for audit trails, or grouped by CURRENCY_CODE to reconcile MRC converted totals against the primary ledger. Because ORG_ID is exposed, queries should apply MO: Operating Unit security, and binds should always supply a concrete SET_OF_BOOKS_ID context if the deployed view text uses a bind rather than a fixed NV substitution.