Results for “payment_number”

50+ results




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

Overview

ICX_AP_INVOICES_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite, classified as a "Received Invoices View" within the iProcurement (ICX) product family. It presents a consolidated, user-facing snapshot of payables invoices that have been received against purchase orders, exposing header-level invoice information together with derived payment, vendor, and purchase order attributes. In Oracle EBS 12.1.1 and 12.2.2 the view serves as a query layer that shields iProcurement and related self-service pages from the complexity of joining the underlying Payables and Purchasing base tables directly. Because it returns formatted currency amounts, translated lookup descriptions, and computed withheld and payment figures, it is well suited to reporting, notification, and integration scenarios that require invoice data in a presentation-ready form rather than a normalized transactional format.

Underlying Base Objects

The view is defined over a join of several Payables and Purchasing objects. Documented base objects include AP_INVOICES, AP_INVOICE_DISTRIBUTIONS, AP_PAYMENT_SCHEDULES, AP_LOOKUP_CODES, PO_HEADERS, PO_DISTRIBUTIONS_AP_V, PO_VENDORS, and PO_VENDOR_SITES, together with the packages FND_CURRENCY, FND_GLOBAL, ICX_AP_INVOICES_PKG, and ICX_AP_INVOICE_PAYMENTS_PKG. The primary join links AP_INVOICES to AP_PAYMENT_SCHEDULES on INVOICE_ID and to AP_INVOICE_DISTRIBUTIONS on INVOICE_ID, with the distribution further linked to PO_DISTRIBUTIONS_AP_V via PO_DISTRIBUTION_ID and to PO_HEADERS via PO_HEADER_ID. Vendor identity is resolved through PO_VENDORS and PO_VENDOR_SITES. AP_LOOKUP_CODES is outer-joined twice to translate the invoice type and payment status flags. The DISTINCT keyword suppresses duplication introduced by the multi-line distribution join, and the package functions supply formatted currency masks and calculated amounts. Several referenced objects, such as PO_VENDORS and PO_VENDOR_SITES, are themselves views.

Key Columns

Common Use Cases and Queries

The view is typically queried to present received invoices to procurement users or to feed downstream reporting. A representative query filters by vendor site and orders by invoice date: SELECT po_number, invoice_num, invoice_amount, invoice_currency_code, payment_status FROM apps.icx_ap_invoices_v WHERE vendor_site_id = :site_id ORDER BY invoice_date DESC; Another common pattern groups by PO number to summarize invoiced value: SELECT po_number, COUNT(*) invoice_count, SUM(...) FROM apps.icx_ap_invoices_v GROUP BY po_number; Because amounts are already formatted as character strings, arithmetic aggregation requires care, and consumers should be aware that the DISTINCT and outer joins may affect row counts where invoices span multiple distributions. Filters on invoice_type or payment_status leverage the translated display values, making the view convenient for end-user search pages and notification content in iProcurement.