Search Results icx_webstore_items_v




Overview
Explore in AI Chat

Overview

ICX_WEBSTORE_ITEMS_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, classified under the ICX (Oracle iProcurement) product family. It exposes the catalog of purchasable store items that iProcurement presents to end users, combining item master attributes, price list pricing, unit of measure, item category, and customer-specific item cross-references into a single denormalized projection. The ETRM record carries the note "- Retrofitted", indicating the object was reintroduced or re-registered during an upgrade cycle rather than created as a fresh design artifact. Its status is VALID in both 12.1.1 and 12.2.2.

The view is a reporting and integration surface. iProcurement store pages, punchout-style catalog queries, and custom extensions typically reference it when a flat, query-friendly representation of item-plus-price is required without joining the underlying transactional tables directly. Because the view text filters aggressively on date ranges and profile options, it returns only currently active, order-enabled items for the operating unit implied by the profile context.

Underlying Base Objects

The documented base objects are synonyms to MTL_SYSTEM_ITEMS_KFV, MTL_ITEM_CATEGORIES, MTL_PARAMETERS, MTL_UNITS_OF_MEASURE, MTL_CUSTOMER_ITEMS, MTL_CUSTOMER_ITEM_XREFS, SO_PRICE_LISTS, SO_PRICE_LIST_LINES, FND_PROFILE_OPTIONS, and FND_PROFILE_OPTION_VALUES, together with the QP_PRICE_LIST_PVT and QP_UTIL packages. The view text joins price list lines to items through INVENTORY_ITEM_ID and to units of measure through UNIT_CODE, then attaches category membership via MTL_ITEM_CATEGORIES and organization context via MTL_PARAMETERS.

Joins to MTL_CUSTOMER_ITEMS and MTL_CUSTOMER_ITEM_XREFS are outer (indicated by the (+) operator in the extracted text), so items without customer-specific cross-references still appear. Profile option values drive organization filtering, restricting results to the inventory organization identified by the active profile. Item eligibility is limited to BOM_ITEM_TYPE values of 4 and 1, and price list lines are constrained to the current SYSDATE window.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing negotiated pricing per customer, validating that store items are correctly categorized, and extracting a price catalog for external or punchout integrations.

  • Retrieve active items for a price list: 
    SELECT INVENTORY_ITEM_ID, CONCATENATED_SEGMENTS, DESCRIPTION, LIST_PRICE, CURRENCY_CODE
FROM   APPS.ICX_WEBSTORE_ITEMS_V
WHERE  PRICE_LIST_ID = :p_price_list_id;
  • Find customer-specific items: 
    SELECT CUSTOMER_ITEM_NUMBER, CONCATENATED_SEGMENTS, LIST_PRICE
FROM   APPS.ICX_WEBSTORE_ITEMS_V
WHERE  CUSTOMER_ID IS NOT NULL;
  • Category-level catalog review: 
    SELECT CATEGORY_ID, COUNT(*) item_count
FROM   APPS.ICX_WEBSTORE_ITEMS_V
GROUP  BY CATEGORY_ID;

Because the view already enforces organization and date filters, queries should avoid redundant predicates on those columns unless auditing historical rows is intended.