Search Results qty_rcv_exception_code




Overview
Explore in AI Chat

Overview

The view ICX_PO_VENDORS_V belongs to the Oracle iProcurement (ICX) product family within Oracle E-Business Suite. In the ETRM reference for releases 12.1.1 and 12.2.2, this object is catalogued with the description "Obsolete" and is explicitly flagged as "Not implemented in this database." This designation is significant: it indicates that the view is a legacy artifact retained in the data dictionary documentation for historical and backward-compatibility reference, but it is not created or maintained in a standard, current installation of the E-Business Suite.

The view was originally intended to expose supplier (vendor) master information together with the purchasing and payables control attributes required by iProcurement and related self-service purchasing flows. Its stated purpose was to present a consolidated, query-friendly projection of vendor records — including payment terms, hold flags, receiving controls, and purchasing hold reasons — so that iProcurement pages and integration programs could retrieve supplier attributes without joining the full set of underlying AP and PO tables directly.

Because the object is documented as obsolete, it should not be relied upon in new development. Any custom report, concurrent program, or integration that references ICX_PO_VENDORS_V should be reviewed and re-pointed to a supported replacement view or to the base tables.

Underlying Base Objects

The documented ETRM metadata for ICX_PO_VENDORS_V lists no referenced base objects ("none documented"). The view text, however, is a straightforward projection composed almost entirely of column names that originate from the Oracle Payables supplier tables — primarily PO_VENDORS (and its synonym AP_SUPPLIERS in later releases) and, for the site-level attributes, PO_VENDOR_SITES_ALL. The presence of columns such as VENDOR_ID, SEGMENT1, VENDOR_NAME, and the many LOOKUP_CODE columns confirms that the view was defined as a simple SELECT over supplier header records rather than a complex join.

In 12.2.2 the underlying supplier data model was reorganized under the AP_SUPPLIERS, AP_SUPPLIER_SITES_ALL, and related TCA (Trading Community Architecture) tables. This restructuring is one reason the older ICX view is marked obsolete: it references a supplier structure that no longer exists in the same physical form. Because the object is not implemented, no dependency chain is actively maintained.

Key Columns

The columns exposed by the view fall into several functional groups:

The column directly relevant to the search term "purchasing_hold_reason" is PURCHASING_HOLD_REASON, which stores the reason a supplier is placed on purchasing hold, paired with HOLD_FLAG, HOLD_BY, and HOLD_DATE.

Common Use Cases and Queries

A historical query to retrieve suppliers on purchasing hold, including the hold reason, would resemble the following:

  • SELECT vendor_id, vendor_name, hold_flag, purchasing_hold_reason, hold_by, hold_date FROM icx_po_vendors_v WHERE hold_flag = 'Y';

Other likely scenarios included populating iProcurement supplier selection pages, filtering enabled suppliers for requisition entry, and reading payment or receiving defaults during checkout. Because the view is documented as obsolete and not implemented, these queries will fail with an "object does not exist" error in a current 12.1.1 or 12.2.2 environment. The supported alternative is to query the base supplier tables (AP_SUPPLIERS, AP_SUPPLIER_SITES_ALL) or a currently maintained supplier view. Developers should treat the presence of ICX_PO_VENDORS_V in legacy code as a migration item and validate any reference against the live data dictionary before use.