Search Results document_num




Overview
Explore in AI Chat

Overview

ICX_PO_SUPPL_CAT_ITEMS_V is an APPS-owned view in Oracle E-Business Suite Release 12.1.1 and 12.2.2, catalogued under the ICX (Oracle iProcurement) product family. ETRM documentation classifies the object as Obsolete, and its status is VALID, meaning the definition persists in the database but Oracle no longer positions it as a supported or forward-development interface. Its purpose was to expose supplier catalog content sourced from Oracle Purchasing documents—quotations, blanket purchase agreements, and related sourcing records—so that iProcurement and dependent reporting layers could present purchasable catalog items alongside vendor, pricing, and agreement attributes in a single flattened row set. The view joins header-level Purchasing data (vendor, terms, currency, effective dates, authorization) with line-level item data (item, category, UOM, quantity, price, vendor product number) and resolves several descriptive values through lookups and HR name utilities.

Because the object is obsolete, it should be treated as a legacy read-only artifact. New development should reference the current iProcurement catalog and Purchasing sourcing views rather than this definition. The user search term "document_num" maps directly to the DOCUMENT_NUM column, which exposes the Purchasing document number (PO_HEADERS.SEGMENT1), the human-readable identifier for the underlying quotation or blanket agreement.

Underlying Base Objects

The documented base objects fall into several functional groups:

PO_HEADERS supplies the header key, vendor, document type, authorization status, terms, currency, and effective dates. PO_LINES supplies line number, item, category, description, UOM, quantity, unit price, and committed quantities. Vendor views resolve names, site codes, contacts, and parent/hold attributes. Key Flexfield views (MTL_SYSTEM_ITEMS_KFV, MTL_CATEGORIES_KFV) render concatenated item and category identifiers. HR packages constrain agent and contact names according to the caller's security profile.

Key Columns

Common Use Cases and Queries

Typical legacy usage centers on retrieving supplier catalog lines for a specific agreement or supplier, or listing all items tied to a blanket agreement identified by document number.

SELECT document_num, vendor_name, item_description,
       currency_line_price, line_uom
FROM   apps.icx_po_suppl_cat_items_v
WHERE  document_num = :p_document_num;

SELECT document_num, type_name, vendor_name,
       effective_from, effective_to, amount_agreed
FROM   apps.icx_po_suppl_cat_items_v
WHERE  vendor_id = :p_vendor_id
AND    effective_to >= SYSDATE;

Additional scenarios include reconciling catalog line prices against PO_LINES, auditing which suppliers expose active blanket agreements, and extracting item/category combinations for downstream punchout or requisition enrichment. Because the view applies HR security and financial system parameters, query results vary with the runtime user context. Given its obsolete status, any implementation relying on this view should plan migration to supported iProcurement catalog interfaces.