Search Results formatted_list_price




Overview

ICX_FMT_STORE_ITEMS_V is a reporting view in the Oracle iProcurement (ICX) module of Oracle E-Business Suite, present in the 12.1.1 and 12.2.2 code lines. Its name denotes a "formatted" store items view: it projects the contents of the iProcurement web store item catalog while applying a formatted, currency-aware representation of the list price. The view is documented as "Retrofitted," meaning its definition was carried forward from an earlier release to preserve compatibility for downstream consumers rather than being newly authored in 12.2.2. ETRM additionally records "Not implemented in this database" for the environment in which the metadata was captured, indicating the object exists in the product definition but had no physical instantiation in that specific instance. The view's principal role is to expose purchasable store items together with pricing, unit of measure, categorization, and customer-specific item attributes, so that iProcurement pages and external catalog or punchout integrations can resolve item and price context in a single query. Because it exposes CUSTOMER_ADDRESS_ID, it is also directly relevant to searches involving customer ship-to or bill-to address context for customer-specific pricing.

Underlying Base Objects

The view text defines ICX_FMT_STORE_ITEMS_V over two documented sources. The primary source is ICX_WEBSTORE_ITEMS_V, aliased ICX, which supplies the store catalog, pricing, categorization, and customer-specific columns. The secondary source is MTL_UNITS_OF_MEASURE, aliased UOM, joined on the equality of the two unit-of-measure columns: ICX.UNIT_OF_MEASURE = UOM.UNIT_OF_MEASURE. This join enriches each row with the canonical UOM_CODE from the inventory unit-of-measure table. ETRM lists no separately documented base tables for the view; ICX_WEBSTORE_ITEMS_V is itself a view that in turn resolves to inventory, price list, and customer item base tables. The view therefore acts as a light presentation and formatting layer rather than a stored entity. No materialized or indexed storage is implied.

h4>Key Columns

Common Use Cases and Queries

Typical uses include catalog price display, punchout/extract feeds, and customer-specific item lookups. A representative query resolving items for a given customer address is:

  • SELECT INVENTORY_ITEM_ID, ITEM_NAME, LIST_PRICE, FORMATTED_LIST_PRICE, CURRENCY_CODE, UOM_CODE FROM ICX_FMT_STORE_ITEMS_V WHERE CUSTOMER_ID = :customer_id AND CUSTOMER_ADDRESS_ID = :ship_to_id ORDER BY ITEM_NAME;
  • SELECT INVENTORY_ITEM_ID, ITEM_NAME, CUSTOMER_ITEM_NAME, LIST_PRICE FROM ICX_FMT_STORE_ITEMS_V WHERE PRICE_LIST_ID = :price_list_id AND SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE);

Note that ETRM documents referenced base objects as none beyond the two view/table sources above, and the object may not be implemented in every environment; consumers should verify presence before relying on it in custom code.