Search Results ap_mc_invoice_payments




Overview
Explore in AI Chat

Overview

AP_MC_INVOICE_PAYMENTS is a Payables (AP) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores invoice payment records expressed in the MRC (Multiple Reporting Currencies) defined reporting currency. The Multiple Reporting Currencies feature allows a single primary ledger to be maintained alongside one or more reporting ledgers, each operating in a different functional currency. This table persists the payment-side accounting amounts converted into those reporting currencies, capturing the exchange rate, rate type, and realized gain or loss accounting that results when an invoice is settled in a currency other than the reporting currency's functional currency. It works in parallel with the primary ledger payment records, providing the reporting-currency equivalent of the amounts recorded in the primary set of books.

From a data modeling perspective, the ETRM metadata classifies this object as standalone based on its foreign-key structure, meaning it does not participate in a clean parent/child hierarchy detectable from its constraints. The heuristic Data Vault classification is correspondingly hub-like with respect to its own key, but functionally it behaves as a satellite of the primary invoice payment entity, storing currency-conversion attributes that describe the payment event under a specific reporting ledger. Modeling it as a satellite attached to an invoice-payment hub keyed by INVOICE_PAYMENT_ID and a ledger hub keyed by SET_OF_BOOKS_ID is a reasonable suggestion.

Key Information Stored

The table contains nine documented columns. The primary key is defined by the index AP_MC_INVOICE_PAYMENTS_PK on the composite of INVOICE_PAYMENT_ID and SET_OF_BOOKS_ID. A separate unique index, AP_MC_INVOICE_PAYMENTS_U1, covers the same two columns (INVOICE_PAYMENT_ID, SET_OF_BOOKS_ID), confirming that the combination is the business-key candidate ensuring one reporting-currency record per payment per ledger.

  • INVOICE_PAYMENT_ID — surrogate identifier linking the MRC record to its primary-ledger payment entry.
  • SET_OF_BOOKS_ID — the reporting set of books (ledger) in whose currency the amounts are expressed.
  • EXCHANGE_DATE — the date used to determine the conversion rate applied to the payment.
  • EXCHANGE_RATE — the rate used to convert the payment into the reporting currency.
  • EXCHANGE_RATE_TYPE — the rate type (e.g., spot, corporate) selected for conversion.
  • GAIN_CODE_COMBINATION_ID — the accounting flexfield combination to which realized exchange gain is posted.
  • LOSS_CODE_COMBINATION_ID — the accounting flexfield combination to which realized exchange loss is posted.
  • INVOICE_BASE_AMOUNT — the invoice amount converted into the reporting currency's base amount.
  • PAYMENT_BASE_AMOUNT — the payment amount converted into the reporting currency's base amount.

Common Use Cases and Queries

Typical uses include reporting-currency reconciliation, realized gain/loss analysis on foreign-currency settlements, and audit of MRC conversion rates. A common query joins this table to the primary payment table by INVOICE_PAYMENT_ID and filters by SET_OF_BOOKS_ID for a given reporting ledger.

Sample pattern: select INVOICE_PAYMENT_ID, SET_OF_BOOKS_ID, EXCHANGE_RATE, INVOICE_BASE_AMOUNT, PAYMENT_BASE_AMOUNT from AP_MC_INVOICE_PAYMENTS where SET_OF_BOOKS_ID = :ledger_id and EXCHANGE_DATE between :from_date and :to_date. Analysts reconcile GAIN_CODE_COMBINATION_ID and LOSS_CODE_COMBINATION_ID balances against GL realized gain/loss accounts, and compare INVOICE_BASE_AMOUNT against PAYMENT_BASE_AMOUNT to detect residual differences arising from rate fluctuation between invoice and payment dates.

Related Objects

Although the table is classified standalone with no mined foreign keys, it logically references the following objects by documented join columns: