Search Results update_ra_rec_cash_diff

Overview

AR_MRC_ENGINE3 is a PL/SQL package body in the Oracle E-Business Suite Receivables (AR) module, owned by APPS and classified as an OTHER API. Its role is to support Multiple Reporting Currencies (MRC) processing for receivable applications and cash receipts. In an MRC-enabled environment, a single transaction is captured in the functional (primary) ledger and must be replicated and converted into one or more reporting ledgers. AR_MRC_ENGINE3 is the engine that performs the currency conversion and insertion logic for those replicated rows when receipt application, on-account application, and related receivable application events occur in Receivables.

The package was created on 09/03/2002 by Debbie Sue Jancis, as recorded in the package header modification history. The shipped source reflects a NOSHIP version and, in the documented excerpt, the procedure bodies are largely stubbed with NULL and commented-out debug statements, indicating the header and interface definitions are the primary documented surface of this object.

Key Procedures and Functions

ETRM documents fifteen procedures/functions within AR_MRC_ENGINE3. Each corresponds to a distinct receivable-application scenario that must be propagated to reporting sets of books:

• INSERT_RA_REC_CASH — Processes MRC data for insertion when a receipt is applied to a transaction with cash; called from ARP_PROC_RCT_UTIL for the insert path of receipt applications.
• RECEIPT_APPLICATION — Handles conversion and replication for general receipt-application activity.
• ON_ACCOUNT_RECEIPTS — Processes receipts applied on account (unapplied/on-account) in reporting currency.
• OTHER_ACCOUNT_APPLICATION — Supports "other account" application events, an application type associated with the search term the user queried. It governs the MRC handling of applications to accounts other than the standard transaction and on-account types.
• REVERSAL_INSERT_OPPOS_RA_RECS — Creates the opposite (reversing) rows for MRC receivable application records during reversal processing.
• REVERSE_RA_RECS — Performs the reversal of receivable application MRC records.
• CONFIRM_RA_REC_UPDATE — Confirms and commits updates to receivable application MRC records.
• UPDATE_CM_APPLICATION — Handles updates when a credit memo is applied in a reporting currency.
• UPDATE_RA_REC_QUICKCASH — Updates receivable application records created through the QuickCash flow.
• INSERT_RA_REC_QUICKCASH — Inserts receivable application records generated by the QuickCash flow.
• UPDATE_SELECTED_TRANSACTION — Updates the selected transaction linkage for MRC application records.
• ACTIVITY_APPLICATION — Processes application activity events for propagation to reporting ledgers.
• RATE_ADJ_INSERT_REC — Inserts MRC receivable records resulting from exchange-rate adjustments.
• CONFIRM_RA_REC_CREATE — Confirms and finalizes creation of receivable application MRC records.
• UPDATE_RA_REC_CASH_DIFF — Handles updates where a cash difference exists on a receipt application.

Tables Accessed

The package operates against three core Receivables tables, accessed through APPS synonyms:

• AR_CASH_RECEIPTS — Provides receipt identifiers and amounts that anchor the cash side of MRC application processing.
• AR_PAYMENT_SCHEDULES — Supplies the payment schedule (installment) context for the transaction being applied.
• AR_RECEIVABLE_APPLICATIONS — The primary table for reading and writing application records, including the reporting-currency rows in the MRC set of books.

Usage Notes

AR_MRC_ENGINE3 is an internal engine rather than a user-invoked API. ETRM indicates it is referenced by five other packages, and the documented excerpt confirms that INSERT_RA_REC_CASH is called from ARP_PROC_RCT_UTIL, Oracle's shared receipt-processing utility. It is therefore triggered indirectly when users perform receipt application, on-account application, QuickCash, credit memo application, reversal, and rate-adjustment operations through Receivables forms and concurrent programs, provided MRC is enabled. Custom code should not call these procedures directly; developers extending MRC behavior should treat the package as a private implementation detail. The NOSHIP designation and the stubbed bodies in the shipped source mean that the documented interface, not the visible logic, is the authoritative reference for version 12.1.1 and 12.2.2.