Results for “ar_system_parameters_mrc_v”

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

Overview

AR_SYSTEM_PARAMETERS_MRC_V is a multi-reporting-currency (MRC) view owned by the APPS schema in Oracle E-Business Suite Receivables. It exposes the Receivables system parameters that govern default accounting, tax, and customer setup behavior, presented in a form suitable for multi-organization and MRC-aware reporting. The view carries the status VALID and is described in the ETRM metadata as "Retrofitted," indicating it was carried forward or reconstructed to preserve compatibility across releases rather than newly authored. The "MRC" suffix signals that the view is intended to surface the system-parameters row tied to the reporting context, typically through the ORG_ID and CLIENT_INFO mechanism used to identify the current operating unit and reporting set of books. Because it is a view rather than a table, it performs no data storage of its own; all values are derived from the underlying system-parameters record at query time.

Underlying Base Objects

Per the documented view metadata for 12.2.2, the only referenced base object is AR_SYSTEM_PARAMETERS_ALL, accessed through a synonym. AR_SYSTEM_PARAMETERS_ALL is the Receivables system-parameters table, keyed by ORG_ID, which stores one parameter record per operating unit. The view selects from this table and applies a number of column derivations and expression-based projections. Notably, several columns are selected with an NVL/SUBSTRB/USERENV('CLIENT_INFO') construct, which derives the current organization context dynamically from the session's client information string. This design allows the MRC view to filter or annotate the parameters according to the active reporting context without requiring the caller to supply the ORG_ID explicitly. Because the view text references only the single base object, its behavior is deterministic: it inherits the row-level content of AR_SYSTEM_PARAMETERS_ALL and adds context-driven computed columns.

Key Columns

The view projects a broad set of Receivables system-parameter columns. Among the most significant:

• ORG_ID — operating unit identifier that scopes each parameter record.
• ACCOUNTING_METHOD — the accounting method (for example, accrual or cash basis) applied to Receivables transactions.
• TAX_METHOD, TAX_CODE, TAX_CURRENCY_CODE, and the TAX_USE_* exempt/rate flags — the tax engine configuration governing defaulting and tax calculation.
• SALESREP_REQUIRED_FLAG, SITE_REQUIRED_FLAG, GENERATE_CUSTOMER_NUMBER, AUTO_SITE_NUMBERING — customer and salesperson setup defaults.
• CREATE_RECIPROCAL_FLAG, CHANGE_PRINTED_INVOICE_FLAG, INVOICE_DELETION_FLAG — invoice control behavior.
• UNALLOCATED_REVENUE_CCID, CODE_COMBINATION_ID_GAIN, CODE_COMBINATION_ID_LOSS, LOCATION_TAX_ACCOUNT — accounting flexfield references for revenue, gain/loss, and tax postings.
• CASH_BASIS_SET_OF_BOOKS_ID, POSTING_DAYS_PER_CYCLE, RUN_GL_JOURNAL_IMPORT_FLAG — period and General Ledger posting controls.
• The CLIENT_INFO-derived expression — supplies the current session organization context, defaulting to -99 when unavailable.

Common Use Cases and Queries

This view is typically queried by reports, interfaces, and extensions that need Receivables system parameters in an MRC-aware context, or wherever a read-only projection of AR_SYSTEM_PARAMETERS_ALL is preferred over direct table access. A representative query retrieves the accounting method and tax configuration for a specific operating unit:

• SELECT org_id, accounting_method, tax_method, tax_code, cash_basis_set_of_books_id FROM ar_system_parameters_mrc_v WHERE org_id = :p_org_id;
• SELECT org_id, salesrep_required_flag, site_required_flag, generate_customer_number FROM ar_system_parameters_mrc_v;
• SELECT org_id, unallocated_revenue_ccid, code_combination_id_gain, code_combination_id_loss FROM ar_system_parameters_mrc_v WHERE org_id = :p_org_id;

Because the view derives session context from CLIENT_INFO, applications should ensure the correct organization context is initialized before querying. All access is read-only, and privilege is controlled through the standard APPS synonym grants.