Search Results mrc_gain_code_combination_id

Overview

The AP_INVOICE_PAYMENTS_ALL_MRC_V view is a Multiple Reporting Currencies (MRC) view within the Oracle Payables (AP) module. It is described in the ETRM metadata as a "MULTI-ORG MRC view," a designation that places it within the family of objects that expose invoice payment records translated into a reporting set of books in addition to the primary set of books. This view answers the reporting requirement of organizations operating under more than one functional currency, where a single transaction must be reported in both the primary and reporting currencies.

The object is defined over the join of two base objects and exposes both the primary functional-currency columns and their reporting-currency counterparts. Users searching on "mrc_exchange_rate" typically encounter this view because it surfaces both EXCHANGE_RATE (the primary set of books rate) and MRC_EXCHANGE_RATE (the reporting set of books rate), together with their corresponding exchange rate type, exchange date, base amounts, and gain/loss code combinations. The presence of parallel column pairs makes the view a natural access point for reconciling currencies across sets of books.

Underlying Base Objects

The view is defined with the following SELECT statement, joining AP_INVOICE_PAYMENTS_ALL (aliased B) and AP_MC_INVOICE_PAYMENTS (aliased MC):

• AP_INVOICE_PAYMENTS_ALL — the primary base table holding invoice payment records in the functional currency of the primary set of books, including posting flags, amounts, check identifier, invoice identifier, period name, and bank account details.
• AP_MC_INVOICE_PAYMENTS — the MRC companion table that stores the reporting-currency equivalents, including the MRC exchange rate and MRC base amounts.

Join condition: B.INVOICE_PAYMENT_ID = MC.INVOICE_PAYMENT_ID AND MC.SET_OF_BOOKS_ID = NVL(TO_NUMBER(SUBSTRB(USERENV('CLIENT_INFO'), 45, 10)), -99). The SET_OF_BOOKS_ID predicate is derived from the CLIENT_INFO environment string, meaning the view returns data only for the reporting set of books currently selected by the session. The ETRM metadata notes "Referenced base objects: none documented," reflecting the limited cataloguing available for this object in the source repository.

Key Columns

• INVOICE_PAYMENT_ID — primary key linking the primary and MRC records.
• EXCHANGE_RATE / MRC_EXCHANGE_RATE — the rate applied in the primary versus reporting set of books; the column central to the user's search.
• EXCHANGE_RATE_TYPE / MRC_EXCHANGE_RATE_TYPE — the rate type (e.g., Spot, Corporate) used for each set of books.
• EXCHANGE_DATE / MRC_EXCHANGE_DATE — the date on which each rate was effective.
• INVOICE_BASE_AMOUNT / MRC_INVOICE_BASE_AMOUNT and PAYMENT_BASE_AMOUNT / MRC_PAYMENT_BASE_AMOUNT — the converted invoice and payment amounts for the primary and reporting currency respectively.
• GAIN_CODE_COMBINATION_ID / MRC_GAIN_CODE_COMBINATION_ID and LOSS_CODE_COMBINATION_ID / MRC_LOSS_CODE_COMBINATION_ID — accounting flexfield combinations for exchange gain and loss.
• SET_OF_BOOKS_ID — the reporting set of books identifier, driven by client-info.
• Supporting columns include ACCOUNTING_DATE, ACCOUNTING_EVENT_ID, PAYMENT_NUM, PERIOD_NAME, POSTED_FLAG, CASH_POSTED_FLAG, ACCRUAL_POSTED_FLAG, and the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN).

Common Use Cases and Queries

The view is used to report invoice payment activity across multiple currencies, to audit exchange rate application, and to reconcile exchange gain/loss postings between primary and reporting sets of books. A typical query to retrieve payment records with both rate values is:

SELECT invoice_payment_id,
       payment_num,
       exchange_rate,
       mrc_exchange_rate,
       exchange_rate_type,
       mrc_exchange_rate_type,
       exchange_date,
       mrc_exchange_date,
       invoice_base_amount,
       mrc_invoice_base_amount,
       payment_base_amount,
       mrc_payment_base_amount
  FROM ap_invoice_payments_all_mrc_v
 WHERE invoice_id = :invoice_id;

Because the view filters by the reporting set of books embedded in CLIENT_INFO, consumers must ensure the correct reporting set of books is initialized in the session before querying. Given the ETRM remark that the view is "Not implemented in this database," availability must be verified per environment before use. Where reporting-currency detail is required, this view remains the appropriate access path from the Payables schema.