Results for “ap_system_parameters_mrc_v”

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

Overview

AP_SYSTEM_PARAMETERS_MRC_V is a Multi-Reporting-Currency (MRC) view in the Oracle Payables (AP) module. It is classified as a SINGLE-ORG view and is designed to expose the Payables system-level setup options that govern invoice entry, payment processing, accounting, and settlement behavior, projected across multiple reporting sets of books. In a standard Oracle EBS 12.1.1 or 12.2.2 environment, the primary system parameters are stored once per operating unit in AP_SYSTEM_PARAMETERS, but reporting and integration requirements frequently demand that the same setup be visible in the context of a reporting set of books and its associated reporting currency. This MRC view provides that projection.

The view serves as a read-only reporting surface. Rather than presenting transactional data, it presents configuration metadata — flags, code combinations, and lookup references — that downstream reports, conversions, and reconciliation processes must consult to interpret and validate Payables activity. Because the search term of interest is batch_control_flag, it is worth noting that this column is directly exposed by the view, allowing users to determine whether invoice batch control is enabled for the reporting set of books in question.

Underlying Base Objects

The ETRM metadata documents no referenced base objects for this view and states that it is not implemented in the source database from which the documentation was extracted. Consequently, no authoritative data dictionary relationship can be asserted from the supplied metadata alone. Based on the naming convention and the view text, the view is defined by joining a base system parameters entity (B, corresponding to AP_SYSTEM_PARAMETERS) against a multi-currency / multi-reporting-set intersection entity (MC), which supplies REPORTING_SET_OF_BOOKS_ID and REPORTING_CURRENCY_CODE. The aliases "B" and "MC" in the column list confirm this two-source structure. The view therefore behaves as a reporting-set-level expansion of the single-row operating-unit setup.

Key Columns

The view exposes a broad set of control flags and accounting references. Notable columns include:

• BATCH_CONTROL_FLAG — indicates whether invoice batch control is active, requiring invoices to be created within a batch before validation and payment.
• REPORTING_SET_OF_BOOKS_ID and REPORTING_CURRENCY_CODE — identify the reporting set of books and the currency in which values are reported.
• AP_SECONDARY_SET_OF_BOOKS_ID — links the parameters to the secondary set of books used in MRC processing.
• INVOICE_NET_GROSS_FLAG, INVOICE_CURRENCY_CODE, PAYMENT_CURRENCY_CODE — control invoice and payment currency behavior.
• ALWAYS_TAKE_DISC_FLAG, TERMS_ID, PAY_DATE_BASIS_LOOKUP_CODE — govern payment terms and discount treatment.
• ACCTS_PAY_CODE_COMBINATION_ID, DISC_TAKEN_CODE_COMBINATION_ID, DISC_LOST_CODE_COMBINATION_ID, GAIN_CODE_COMBINATION_ID, LOSS_CODE_COMBINATION_ID — define the accounting flexfield accounts used for liability, discount, and gain/loss postings.
• POST_DATED_PAYMENTS_FLAG, ALLOW_FUTURE_PAY_FLAG, REPLACE_CHECK_FLAG — control payment issuance behavior.
• DATE_FORMAT_LOOKUP_CODE, REQUIRE_TAX_ENTRY_FLAG, AUTO_TAX_CALC_FLAG — influence entry validation and tax defaulting.

Common Use Cases and Queries

Typical scenarios include reporting the Payables setup for each reporting set of books, validating that batch control is consistently configured, and diagnosing payment or accounting defaults during MRC conversions and reconciliations.

SELECT reporting_set_of_books_id,
       reporting_currency_code,
       batch_control_flag,
       invoice_net_gross_flag,
       payment_currency_code,
       accts_pay_code_combination_id
FROM   ap_system_parameters_mrc_v
WHERE  reporting_set_of_books_id = :p_reporting_sob;

To locate reporting sets where batch control is enabled:

SELECT reporting_set_of_books_id,
       reporting_currency_code
FROM   ap_system_parameters_mrc_v
WHERE  batch_control_flag = 'Y';

Because the view is defined as SINGLE-ORG and not implemented in the documented source database, availability should be verified against the target instance before reliance. When present, it is a convenient read-only source for MRC-aware Payables configuration reporting, particularly for the batch control flag and related accounting defaults.