Search Results header_payment_terms_id




Overview
Explore in AI Chat

Overview

APPS.ICX_PO_SUPPL_SEARCH_ITEMS_V is a VALID Oracle E-Business Suite view owned by the APPS schema and registered in FND Design Data under ICX.ICX_PO_SUPPL_SEARCH_ITEMS_V. It is an internal view of type "View Type Internal," exposed to support the Oracle iProcurement / iSupplier supplier search infrastructure. The view denormalizes sourcing detail from purchase orders, quotations, vendor records, and item masters into a single flattened result set, allowing applications to present catalog and supplier-item search results without issuing complex multi-table joins. Oracle classifies the object as Internal Use Only and does not support direct customer access except through standard Oracle Applications programs; it should therefore be treated as a read-only integration surface rather than a supported API.

Because the view carries both header-level and line-level attributes (PO_HEADER_ID, PO_LINE_ID, ITEM_ID, and so on), it is primarily useful for reference lookups and diagnostic reporting where a flattened purchasing picture is needed across header, line, vendor, and category dimensions.

Underlying Base Objects

The documented dependency list indicates the view is defined over a broad set of purchasing, payables, and HR objects. Core purchasing sources include PO_HEADERS, PO_LINES, PO_LINE_TYPES, PO_DOCUMENT_TYPES, PO_LOOKUP_CODES, PO_VENDORS, PO_VENDOR_SITES, and PO_VENDOR_CONTACTS. Item and category descriptions are sourced from MTL_SYSTEM_ITEMS_KFV and MTL_CATEGORIES_KFV. Payment terms come from AP_TERMS, while GL_SETS_OF_BOOKS, GL_DAILY_CONVERSION_TYPES, and FINANCIALS_SYSTEM_PARAMETERS supply set-of-books and currency conversion context.

Personnel-related data is drawn through PER_PEOPLE_F and the HR_PERSON_NAME, HR_GENERAL, and HR_SECURITY packages. FND_GLOBAL supplies session context such as the current user and responsibility. A temporary synonym, ICX_CONTEXT_RESULTS_TEMP, is referenced in the search flow. These dependencies confirm that the view spans synchronized synonyms, views, and packaged PL/SQL, and that its result set is filtered by HR security rules at runtime.

Key Columns

The view exposes identifiers and descriptive attributes for both header and line levels. Notable groups include:

Common Use Cases and Queries

Typical uses include validating document status on sourcing documents, reconciling supplier item catalogs, and confirming that HR security filtering returns the expected buyers. Because the object is Internal Use Only, queries should be confined to diagnostics and non-production reporting.

Retrieve approved purchase orders with supplier and status display values:

  • SELECT document_num, document_status_code, document_status_dsp, vendor_name, agent_name, currency_code, price FROM apps.icx_po_suppl_search_items_v WHERE document_status_code IN ('APPROVED','OPEN') ORDER BY document_num;

Inspect quotations by item and vendor:

  • SELECT po_header_id, po_line_id, vendor_name, item_id, item_description, line_quantity, vendor_quote_num, effective_from, effective_to FROM apps.icx_po_suppl_search_items_v WHERE vendor_quote_num IS NOT NULL AND item_id = :item_id;

List document status codes currently present in the result set, which is useful when the view is queried for the DOCUMENT_STATUS_CODE column:

  • SELECT document_status_code, COUNT(*) FROM apps.icx_po_suppl_search_items_v GROUP BY document_status_code ORDER BY 1;

These queries should be executed against a cloned environment or with an Oracle-approved support script, given the view's unsupported-access warning.