Search Results header_fob_lookup_code




Overview
Explore in AI Chat

Overview

ICX_PO_SUPPL_SEARCH_ITEMS_V is an Oracle E-Business Suite seeded view owned by the APPS schema and defined in the ICX (Oracle iProcurement) product. Its documented description is "Web Requisitions Context Search View." In EBS 12.1.1 and 12.2.2 the view serves the iProcurement requisition-entry search flow, where a buyer or requester searches prior purchasing documents through Oracle Text and the results are presented as selectable item or document lines. The view flattens header-level and line-level purchasing attributes — sourced from purchase orders, quotations, blanket agreements, lines, vendors, sites, contacts, and lookup display values — into a single wide row. Because it is registered as a VALID view in the APPS schema, it can be queried directly by custom reports and integrations, though Oracle's primary consumer is the iProcurement context search region. The user's search term, header_fob_lookup_code, corresponds to the view's HEADER_FOB_LOOKUP_CODE column, which is projected from PO_HEADERS.FOB_LOOKUP_CODE.

Underlying Base Objects

The view text joins ICX_CONTEXT_RESULTS_TEMP (the Oracle Text scoring and context results table, which supplies ICRT.CONID and ICRT.SCORE) to PO_HEADERS and PO_LINES, and then to supporting setup and descriptive objects. The documented referenced objects include PO_HEADERS, PO_LINES, PO_LINE_TYPES, PO_DOCUMENT_TYPES, PO_LOOKUP_CODES (a view used to resolve displayed lookup values such as document status), PO_VENDORS, PO_VENDOR_SITES, and PO_VENDOR_CONTACTS, which are the vendor-facing views over supplier data. Additional joins include MTL_CATEGORIES_KFV for the concatenated category name, MTL_SYSTEM_ITEMS_KFV for item flexfield display, AP_TERMS for payment terms, GL_SETS_OF_BOOKS, GL_DAILY_CONVERSION_TYPES, and FINANCIALS_SYSTEM_PARAMETERS for currency and ledger context. Security and formatting are handled through the FND_GLOBAL, HR_SECURITY, HR_GENERAL, and HR_PERSON_NAME packages and the PER_PEOPLE_F view, which resolve the agent name and enforce HR security. The DISTINCT keyword suppresses duplicate search hits originating from the context results table.

Key Columns

Common Use Cases and Queries

Typical uses include auditing FOB, freight, and shipping terms across active agreements, reproducing iProcurement search results for verification, and building custom sourcing reports. The following example returns blanket agreements and quotations with their FOB and freight terms for a supplier:

SELECT document_num,
       type_name,
       vendor_name,
       header_fob_lookup_code,
       header_freight_terms_code,
       header_ship_via_lookup_code
  FROM apps.icx_po_suppl_search_items_v
 WHERE vendor_id = :p_vendor_id
   AND type_lookup_code IN ('BLANKET','QUOTATION');

To resolve the FOB code into a display value, join FND_LOOKUPS using the FOB lookup type. When a relevance-ranked listing is required, filter against SCORE and order the result set accordingly. Because the view is founded on Oracle Text context results, queries outside the iProcurement search flow may return no rows unless scored values exist in ICX_CONTEXT_RESULTS_TEMP; this behavior should be considered when reusing the view in standalone reporting.