Results for “ap_invoice_payments_mrc_v”

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

Overview

AP_INVOICE_PAYMENTS_MRC_V is a single-organization Multiple Reporting Currencies (MRC) view within the Oracle Payables (AP) module. It exposes invoice payment records alongside their corresponding reporting-currency (MRC) counterparts, allowing reporting and integration processes to reconcile a payment's transactional amounts in the functional currency with the equivalent values carried in one or more reporting sets of books. In the Oracle EBS 12.1.1 and 12.2.2 architectures, MRC views of this type are used when an installation maintains secondary or reporting ledgers and requires a consistent, single-source projection of payment data across those ledgers. The view filters rows by the reporting set of books derived from the session's CLIENT_INFO, ensuring the caller sees only the MRC context relevant to the active responsibility.

Underlying Base Objects

The ETRM metadata documents that this view is not implemented in the reference database and lists no separately documented base objects. The view text, however, is definitive: it is defined over two joined objects — AP_INVOICE_PAYMENTS_ALL (aliased B) and AP_MC_INVOICE_PAYMENTS (aliased MC). The join is performed on INVOICE_PAYMENT_ID, restricting the MRC rows to the correct set of books through the predicate on MC.SET_OF_BOOKS_ID, which compares against the client-info context via SUBSTRB(USERENV('CLIENT_INFO'), 45, 10). This single-org construct restricts results to the organization context of the active session, unlike the corresponding _ALL multi-org variants.

Key Columns

Two categories of payment attributes are exposed and are central to the user's interest in the IBAN_NUMBER column:

• IBAN_NUMBER and bank identifiers — IBAN_NUMBER, BANK_ACCOUNT_NUM, BANK_ACCOUNT_TYPE, BANK_NUM, and EXTERNAL_BANK_ACCOUNT_ID identify the disbursement bank account and its institution, supporting bank reconciliation and payment-format reporting.
• Functional-currency amounts — AMOUNT, INVOICE_BASE_AMOUNT, PAYMENT_BASE_AMOUNT, DISCOUNT_TAKEN, and DISCOUNT_LOST represent the primary-ledger figures.
• MRC reporting amounts — MRC_INVOICE_BASE_AMOUNT, MRC_PAYMENT_BASE_AMOUNT, MRC_GAIN_CODE_COMBINATION_ID, MRC_LOSS_CODE_COMBINATION_ID, and the MRC_EXCHANGE_* columns carry the reporting-currency equivalents.
• Posting and control flags — ACCRUAL_POSTED_FLAG, CASH_POSTED_FLAG, POSTED_FLAG, FUTURE_PAY_POSTED_FLAG, REVERSAL_FLAG, and their JE batch identifiers (CASH_JE_BATCH_ID, JE_BATCH_ID) track accounting status.
• Context and audit columns — SET_OF_BOOKS_ID, ORG_ID, INVOICE_PAYMENT_TYPE, PAYMENT_NUM, ACCOUNTING_DATE, PERIOD_NAME, plus standard WHO audit columns.

Common Use Cases and Queries

The view is typically consumed to reconcile payment records across reporting currencies and to extract bank-account and IBAN details for treasury or payment-format reports. A representative query returning the IBAN and MRC amounts for a given reporting ledger is:

SELECT invoice_payment_id, payment_num, iban_number, bank_account_num, amount, mrc_payment_base_amount, mrc_exchange_rate, set_of_books_id FROM ap_invoice_payments_mrc_v WHERE set_of_books_id = :p_reporting_sob AND accounting_date BETWEEN :p_from AND :p_to;

Because the view limits rows through CLIENT_INFO, callers must ensure the correct reporting set of books is set in the session context before querying. The view is also useful as a source for custom Oracle Reports, OAF pages, or third-party integrations that need a unified payment picture spanning functional and reporting currencies, including IBAN-level detail absent from the daily cash-focused AP views.