Search Results check_currency_code




Overview
Explore in AI Chat

Overview

The ICX_AP_INVOICE_PAYMENTS_V view is a public APPS-owned database object residing in the Oracle E-Business Suite. Although its owning product is identified as ICX (Oracle iProcurement), the view is a retrofitted construct that exposes Oracle Payables invoice payment information in a flattened, formatted, and self-service-friendly manner. Its primary role is to present invoice-to-payment relationships — linking an invoice to the check or payment that settled it — without requiring the calling application or report to join multiple Payables base tables directly.

Because it is a view rather than a table, it provides no independent data storage. Instead it presents a read-only, real-time projection of the underlying Payables transactions. The view is registered in ETRM with a status of VALID, confirming it is a supported, compiled object in both 12.1.1 and 12.2.2 environments. The view is characteristically used by iProcurement self-service pages, by reporting and reconciliation extracts, and by any integration that requires a simple, denormalized source of invoice payment and discount information.

Underlying Base Objects

The view definition references four documented base objects in the APPS schema:

The joins are equijoins on AIP.INVOICE_ID = AI.INVOICE_ID and AIP.CHECK_ID = AC.CHECK_ID, producing one row per invoice payment (payment distribution) record.

Key Columns

  • INVOICE_NUM / INVOICE_ID — the human-readable invoice number and its internal identifier, useful for lookups and joins to AP_INVOICES.
  • INVOICE_CURRENCY_CODE — the currency of the invoice, which may differ from the payment currency.
  • CHECK_NUMBER / CHECK_ID — the payment document number and its internal key from AP_CHECKS. "Check" is used generically for all payment methods (checks, EFT, wire, etc.).
  • CHECK_CURRENCY_CODE — the currency in which the payment was issued and the currency used to format the AMOUNT and DISCOUNT_TAKEN columns.
  • VENDOR_SITE_ID — identifies the supplier site associated with the payment document.
  • AMOUNT — the payment amount, converted to a character string via TO_CHAR using FND_CURRENCY.SAFE_GET_FORMAT_MASK. This formatting makes the value display-ready for reports and self-service pages.
  • DISCOUNT_TAKEN — the discount amount captured against the invoice payment. It is wrapped in NVL to substitute 0 and then formatted as a string in the payment currency. This is the column most frequently targeted by users searching the term "discount_taken," as it isolates the early-payment discount realized on each payment.
  • ACCOUNTING_DATE — the GL accounting date of the payment distribution.
  • INVOICE_PAYMENT_ID — the primary key of the AP_INVOICE_PAYMENTS record, providing a unique row identifier.

Common Use Cases and Queries

The view is typically used to report payments and discounts against invoices, to reconcile supplier activity, or to feed downstream self-service and analytics processes. Note that AMOUNT and DISCOUNT_TAKEN are returned as formatted character strings, so consumers requiring numeric aggregation should query AP_INVOICE_PAYMENTS directly rather than converting these strings.

A representative query isolating discounts taken on a given invoice:

  • SELECT check_number, check_currency_code, amount, discount_taken, accounting_date FROM apps.icx_ap_invoice_payments_v WHERE invoice_num = :p_invoice_num;

A broader reconciliation query aggregating discount activity by payment currency (using a numeric cast where required):

  • SELECT check_currency_code, COUNT(*) payment_count, SUM(TO_NUMBER(REPLACE(discount_taken, ','))) total_discount FROM apps.icx_ap_invoice_payments_v GROUP BY check_currency_code;

Because the view joins three large Payables tables, queries should always be filtered by INVOICE_ID, CHECK_ID, or ACCOUNTING_DATE to avoid full scans. The object remains a stable, supported component of the Payables reporting surface across both 12.1.1 and 12.2.2.