Results for “po_vendor_name”

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

Overview

ICX_PO_MATCHED_INVOICES_V is an Oracle E-Business Suite view owned by the APPS schema and catalogued under the ICX product family (Oracle iProcurement). It exposes the association between payables invoices and the purchase orders against which they were matched, thereby presenting a consolidated picture of supplier obligations and their corresponding invoice activity. The ETRM documentation classifies the object as Obsolete, and its status is recorded as VALID, meaning the compiled definition remains present in the data dictionary even though Oracle no longer positions it as a supported integration point.

The view was originally used by iProcurement and related self-service purchasing flows to display invoice details alongside the purchase order to which the invoice had been matched. It derives its data entirely from other views and packages rather than from base tables directly, functioning as a presentation-layer join. Because the object is marked obsolete in both 12.1.1 and 12.2.2, it should be treated as a read-only historical artifact; new development should not depend upon it.

Underlying Base Objects

The view text joins ICX_AP_INVOICES_V (aliased API) to ICX_PO_SUPPLIER_ORDERS_V (aliased PSO). The driving predicate correlates PO_DISTRIBUTIONS and AP_INVOICE_DISTRIBUTIONS through PO_DISTRIBUTION_ID, constrained further by PO_HEADER_ID, INVOICE_ID, and NVL(PO_RELEASE_ID, -1). This distribution-level match is what establishes the invoice-to-purchase-order relationship.

The documented referenced objects include AP_INVOICE_DISTRIBUTIONS and PO_DISTRIBUTIONS (both exposed as synonyms), the FND_CURRENCY and FND_GLOBAL packages, ICX_AP_INVOICES_PKG, ICX_AP_INVOICES_V, ICX_AP_INVOICE_PAYMENTS_PKG, ICX_PO_SUPPLIER_ORDERS_V, PO_INQ_SV, and PO_TOTALS_PO_SV. FND_CURRENCY.SAFE_GET_FORMAT_MASK is invoked to apply currency-aware formatting masks to monetary columns, while the remaining packages and views supply the invoice, payment, and supplier-order attributes.

Key Columns

• INVOICE_ID, INVOICE_NUM, INVOICE_DATE, INVOICE_DUE_DATE — invoice identity and dating from the payables side.
• GROSS_AMOUNT, DISCOUNT_AMOUNT_AVAILABLE, AMOUNT_REMAINING — monetary values formatted through FND_CURRENCY; the first two are presented as strings.
• INVOICE_CURRENCY_CODE — currency of the invoice, used to drive the formatting mask.
• PAYMENT_STATUS, PAYMENT_NUMBER — payment lifecycle indicators sourced via the payables package.
• PO_DOCUMENT_NUM, PO_TOTAL, PO_CURRENCY_CODE — purchase order document number and total, formatted per PO currency.
• BUYER_ID, BUYER_NAME — the purchasing agent associated with the order.
• PO_VENDOR_ID, PO_VENDOR_NAME, PO_VENDOR_SITE_ID, PO_VENDOR_SITE_CODE, PO_VENDOR_CONTACT_ID, PO_VENDOR_CONTACT — supplier and contact attributes.
• PO_HEADER_ID, PO_RELEASE_ID — keys linking the record to the purchase order header and release.
• SUPPLIER_URL — the supplier-facing link supplied by the iProcurement order view.

Common Use Cases and Queries

A representative query retrieves matched invoices for a given purchase order header:

• SELECT invoice_num, invoice_date, gross_amount, po_document_num, po_total, payment_status FROM apps.icx_po_matched_invoices_v WHERE po_header_id = :p_po_header_id;
• SELECT invoice_id, invoice_num, amount_remaining, payment_status FROM apps.icx_po_matched_invoices_v WHERE payment_status <> 'PAID';
• SELECT po_vendor_name, po_vendor_site_code, invoice_num, supplier_url FROM apps.icx_po_matched_invoices_v WHERE po_release_id IS NOT NULL;

Given the obsolete designation, these patterns are best reserved for historical reporting or analysis of legacy iProcurement data. For current development, the equivalent information should be sourced directly from the underlying payables and purchasing tables, or from the supported views that Oracle maintains in later releases.