Search Results payment_amount_total




Overview
Explore in AI Chat

Overview

AP_INVOICES_MRC_V is a single-organization reporting view in the Oracle Payables (AP) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes invoice header information across multiple reporting currencies (MRC), combining the operational invoice record with its associated set of books context. In a multi-organization, multi-currency implementation, invoices are stored once in the primary set of books but must be reported in any enabled reporting currency. This view provides the flattened, single-org projection that lets reporting tools and integrations read invoice amounts, payment figures, and currency conversion attributes without joining the underlying MRC schema manually.

For users who search on payment_amount_total, this view is the relevant object: that column is exposed directly here, making AP_INVOICES_MRC_V the natural access point for extracting invoice-level payment totals alongside invoice amounts and currencies. The view is documented as "not implemented in this database," meaning the ETRM metadata reflects the definition rather than a live, populated instance in the reference environment.

Underlying Base Objects

The ETRM metadata for this view lists no explicitly documented referenced base objects, and the owner is not identified. The view text, however, reveals its lineage. It is defined over an alias MC — the MRC invoice table (the multi-currency counterpart of AP_INVOICES_ALL) — and joins or references a second alias B to obtain POSTING_STATUS from the invoice accounting/posting source. Columns such as SET_OF_BOOKS_ID, EXCHANGE_RATE, EXCHANGE_RATE_TYPE, EXCHANGE_DATE, and BASE_AMOUNT are drawn from the MRC table because they are currency-specific. Standard descriptive and control columns (vendor, invoice number, terms, dates, flags, descriptive flexfields, and global attributes) are inherited from the same source and passed through unmodified.

The "SINGLE-ORG" designation confirms the view filters to one operating unit/organization context via ORG_ID, in contrast to "ALL-ORG" views. This makes it suitable for organization-scoped reporting.

Key Columns

Common Use Cases and Queries

Typical uses include payment reconciliation, aged payables reporting, and feeding downstream analytics. A frequent request is retrieving invoices with their payment totals for a given period:

SELECT invoice_id, invoice_num, invoice_currency_code,
       invoice_amount, amount_paid, payment_amount_total
FROM   ap_invoices_mrc_v
WHERE  set_of_books_id = :p_sob
AND    org_id = :p_org
AND    invoice_date BETWEEN :p_from AND :p_to;

For reporting-currency reconciliation, query base versus entered amounts using EXCHANGE_RATE. Because the view is not implemented in the reference database, confirm existence and granted synonyms in the target instance before deployment.