Search Results auto_rec_invoices_per_commit




Overview
Explore in AI Chat

Overview

AR_SYSTEM_PARAMETERS_ALL_MRC_V is a multi-reporting-currency (MRC) view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Receivables (AR) product family and presents the system-wide Receivables setup options defined for the operating unit, but with an MRC-aware lens. The view is flagged as "Retrofitted," meaning it was created or regenerated during the R12 upgrade process to preserve backward compatibility for customizations, reports, and integrations that reference the legacy MRC naming convention.

In EBS, Receivables system parameters govern global behavior such as accounting method, tax defaults, AutoInvoice controls, AutoCash rules, customer and site numbering, discount handling, and gain/loss accounts. The MRC variant exposes the same parameter set while resolving the reporting context through the session's client information, allowing reporting tools to read parameters in the context of a secondary (reporting) set of books rather than only the primary ledger. This makes the view relevant to cross-ledger reporting, reconciliation, and any integration that must respect the MRC framework established in R12.

Underlying Base Objects

The documented base object referenced by AR_SYSTEM_PARAMETERS_ALL_MRC_V is the synonym AR_SYSTEM_PARAMETERS_ALL. In the physical data model this synonym resolves to the AR_SYSTEM_PARAMETERS_ALL table, which stores one row of Receivables system parameters per operating unit (keyed in part by ORG_ID). The MRC view is defined as a SELECT over that base, projecting the full column list of the parameters table.

A defining characteristic of the view is its first expression: NVL(TO_NUMBER(SUBSTRB(USERENV('CLIENT_INFO'), 45, 10)), -99). This extracts a numeric value from the CLIENT_INFO session context and represents the reporting set of books (ledger) identifier used by the MRC architecture. Because it derives from USERENV rather than the base table, the effective reporting context is determined at runtime by the connected session — a behavior inherited from the MRC design and retained for backward compatibility after the R12 multiple-ledger enhancements.

Key Columns

Common Use Cases and Queries

The view is typically queried to confirm Receivables configuration for an operating unit during audits, reconciliations, or integration testing. Because ORG_ID is exposed, queries commonly filter on the operating unit to isolate the correct parameter row.

Retrieve the core accounting and tax parameters for one operating unit:

SELECT org_id, accounting_method, tax_method, tax_rounding_rule
FROM   apps.ar_system_parameters_all_mrc_v
WHERE  org_id = :p_org_id;

Identify the default gain and loss accounts for posting rules:

SELECT org_id, code_combination_id_gain, code_combination_id_loss
FROM   apps.ar_system_parameters_all_mrc_v
WHERE  org_id = :p_org_id;

Review AutoInvoice and commit controls that affect interface performance:

SELECT org_id, auto_rec_invoices_per_commit, ai_log_file_message_level,
       ai_purge_interface_tables_flag
FROM   apps.ar_system_parameters_all_mrc_v
WHERE  org_id = :p_org_id;

Note: the user's search term "min_refund_amount" does not correspond to any column documented for this view in the ETRM metadata. Minimum refund amounts are typically associated with Receivables refund and payment setup, not with system parameters. Analysts seeking a minimum refund setting should examine the appropriate refund/payment configuration objects rather than AR_SYSTEM_PARAMETERS_ALL_MRC_V.

As with all retrofitted MRC views in R12, AR_SYSTEM_PARAMETERS_ALL_MRC_V should be treated primarily as a compatibility construct. New development should generally reference the non-MRC system parameters object unless an existing MRC-dependent component requires this view.