Search Results header_payment_terms_id




Overview
Explore in AI Chat

Overview

The APPS.ICX_PO_SUPPL_CATALOG_ITEMS_V view is a supplier catalog items view owned by the APPS schema and delivered as part of the Oracle iProcurement (ICX) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a flattened, denormalized representation of purchasing documents — quotations, blanket purchase agreements, and related sourcing documents — together with their associated lines, vendor information, and pricing attributes. The view is designed to serve the supplier catalog and hosted catalog search functionality within iProcurement, allowing requisitioning users to browse vendor-published agreements without navigating the underlying normalized purchasing tables directly.

Within the EBS reporting and integration landscape, this view functions as a read-only projection layer. It abstracts the joins between PO_HEADERS, PO_LINES, vendor master data, and purchasing lookup tables, exposing a single set of consistently named columns suitable for display regions, Oracle Reports outputs, and interface extracts. Because the view is validated in the data dictionary, it can be referenced by custom concurrent programs, BI Publisher data templates, and Oracle Application Framework (OAF) pages without additional base-table grants. The terms-related columns, in particular, are surfaced for downstream usage in pricing and payment calculations.

Underlying Base Objects

The view is defined over a documented set of base tables and views, all referenced through APPS synonyms or package calls. The core purchasing objects are PO_HEADERS (aliased PH) and PO_LINES (aliased PL), with supporting lookups from PO_DOCUMENT_TYPES, PO_LINE_TYPES, and PO_LOOKUP_CODES. Vendor data is sourced from the PO_VENDORS, PO_VENDOR_SITES, and PO_VENDOR_CONTACTS views. Category and item context come from MTL_CATEGORIES_KFV and MTL_SYSTEM_ITEMS_KFV. Personnel-related columns draw on PER_PEOPLE_F and the HR_PERSON_NAME, HR_GENERAL, and HR_SECURITY packages, while currency and financial context reference GL_SETS_OF_BOOKS, GL_DAILY_CONVERSION_TYPES, and FINANCIALS_SYSTEM_PARAMETERS. Payment terms names are joined from AP_TERMS, and session context is obtained via FND_GLOBAL. This dependency chain confirms the view is intended for operational catalog and requisitioning flows rather than purely financial reporting.

Key Columns

Common Use Cases and Queries

The view is commonly queried to populate iProcurement catalog search results, to extract hosted catalog content for punchout integrations, and to audit blanket agreement terms exposure. A representative query that isolates the payment-terms column searched by the user might read:

  • Retrieve active agreements with payment terms: SELECT DOCUMENT_NUM, VENDOR_NAME, HEADER_PAYMENT_TERMS_ID, HEADER_PAYMENT_TERMS_NAME, CURRENCY_CODE FROM APPS.ICX_PO_SUPPL_CATALOG_ITEMS_V WHERE HEADER_PAYMENT_TERMS_ID IS NOT NULL;
  • List catalog items for a specific vendor by effective date: SELECT PO_HEADER_ID, ITEM_DESCRIPTION, CURRENCY_LINE_PRICE, EFFECTIVE_FROM, EFFECTIVE_TO FROM APPS.ICX_PO_SUPPL_CATALOG_ITEMS_V WHERE VENDOR_ID = :vendor_id AND SYSDATE BETWEEN EFFECTIVE_FROM AND EFFECTIVE_TO;
  • Aggregate agreements by payment terms for analysis: SELECT HEADER_PAYMENT_TERMS_NAME, COUNT(DISTINCT PO_HEADER_ID) FROM APPS.ICX_PO_SUPPL_CATALOG_ITEMS_V GROUP BY HEADER_PAYMENT_TERMS_NAME;

Because the view joins header and line data, queries return one row per catalog line; consumers requiring header-level uniqueness should apply DISTINCT on PO_HEADER_ID. Access should be granted through the APPS schema, and performance is best when filtering on VENDOR_ID, PO_HEADER_ID, or effective-date ranges.