Search Results invoice_due_date




Overview
Explore in AI Chat

Overview

ICX_PO_SUP_ORDER_INVOICES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the ICX (Oracle iProcurement) product. Its declared purpose is to present purchase order related invoice information to the supplier-facing and internal iProcurement pages, consolidating invoice header, payment schedule, supplier, and purchasing distribution data into a single denormalized projection. The view is documented as VALID in ETRM for both 12.1.1 and 12.2.2, and its column list is identical across those releases.

The view's most distinctive characteristic is that several of its columns are not stored values at all, but the results of server-side function calls and formatting logic. Invoice amounts are passed through FND_CURRENCY.SAFE_GET_FORMAT_MASK, withheld amounts are produced by ICX_AP_INVOICES_PKG.GET_AMOUNT_WITHHELD, the PO number list is generated by ICX_AP_INVOICES_PKG.GET_PO_NUMBER_LIST, and payment details come from ICX_AP_INVOICE_PAYMENTS_PKG.GET_PAID_BY_LIST. For consumers searching on the column name discount_amount_available, this is the field that exposes the early-payment discount still obtainable on an invoice's payment schedule.

Underlying Base Objects

The view is defined over a seven-table join with two outer-joined lookup resolutions. The documented referenced base objects are AP_INVOICES, AP_INVOICE_DISTRIBUTIONS, AP_LOOKUP_CODES, AP_PAYMENT_SCHEDULES, PO_DISTRIBUTIONS, PO_VENDORS, and PO_VENDOR_SITES, together with the FND_CURRENCY, FND_GLOBAL, ICX_AP_INVOICES_PKG, and ICX_AP_INVOICE_PAYMENTS_PKG packages.

The DISTINCT keyword in the SELECT list indicates the join can produce row multiplication, particularly where an invoice carries multiple distributions; consumers should expect one row per qualifying combination rather than strictly one row per invoice.

Key Columns

  • INVOICE_ID / INVOICE_NUM / INVOICE_DATE — invoice identity and accounting date.
  • INVOICE_AMOUNT / INVOICE_CURRENCY_CODE — the invoice total, formatted using the currency's format mask.
  • DISCOUNT_AMOUNT_AVAILABLE — the discount still available on the payment schedule, sourced directly from AP_PAYMENT_SCHEDULES.DISCOUNT_AMOUNT_AVAILABLE.
  • DISCOUNT_DATE — the date through which the available discount may be taken.
  • GROSS_AMOUNT / AMOUNT_REMAINING — schedule-level gross and outstanding balances, currency-formatted.
  • WITHHELD_AMOUNT_CURRENCY_CODE — a concatenated string combining the withheld amount and currency code.
  • INVOICE_TYPE / PAYMENT_STATUS — decoded lookup display text rather than codes.
  • PO_NUMBER / PO_HEADER_ID / PO_RELEASE_ID — purchasing document context for the invoice.
  • PAYMENT_NUMBER, VENDOR_SITE_CODE, VENDOR_SITE_ID, VENDOR_ID, EMPLOYEE_ID — payment and supplier attribution.

Common Use Cases and Queries

Typical usage includes iProcurement supplier invoice displays, early-payment discount aging reports, and reconciliations that tie invoices back to purchase orders. Because DISCOUNT_AMOUNT_AVAILABLE is a schedule-level value, reports commonly filter on it to isolate invoices where a discount remains claimable before DISCOUNT_DATE.

SELECT invoice_num,
       discount_amount_available,
       discount_date,
       amount_remaining,
       invoice_currency_code
FROM   apps.icx_po_sup_order_invoices_v
WHERE  discount_amount_available IS NOT NULL
AND    discount_date >= SYSDATE
ORDER  BY discount_date;

For PO-centric analysis, the PO_NUMBER and PO_HEADER_ID columns allow grouping invoices by purchasing document. Note that since PO_NUMBER is derived through a package function, it is relatively expensive; restricting the driving set with predicates on INVOICE_DATE, VENDOR_ID, or PO_HEADER_ID before projecting it materially improves performance. As with all ICX views, queries should be issued with APPS-level or read-only reporting privileges, and the view should be treated as a read-only reporting surface rather than an integration target.