Search Results so_price_list_lines




Overview
Explore in AI Chat

Overview

APPS.ICX_NONSHIP_ITEMS_V is a reporting view in the Oracle E-Business Suite Internet Commerce (iStore/ICX) schema. Its purpose is to expose the intersection of non-shippable inventory items and the price lists on which those items are defined. In Oracle Order Management and Advanced Pricing, a shippable item is one that can be placed on a delivery and shipped to a customer. Items flagged as non-shippable (SHIPPABLE_ITEM_FLAG = 'N') are typically services, warranties, subscriptions, or other charge lines that accompany a physical shipment but are not themselves fulfilled through shipping. This view allows reporting and integration processes to identify those items together with the price list and price list line that carry their pricing definitions.

The view is relevant to the search term so_price_list_lines because it is defined directly over the SO_PRICE_LIST_LINES table. It provides a convenient, pre-joined perspective that links the item master, the price list header, and the price list line in a single queryable object.

Underlying Base Objects

Per the documented view text, ICX_NONSHIP_ITEMS_V is defined over three objects joined in a single SELECT DISTINCT statement:

  • MTL_SYSTEM_ITEMS_KFV — the key-flexfield variant of the item master, supplying the inventory item identifier, description, organization, and the shippable flag. It is referenced via a SYNONYM in the APPS schema.
  • SO_PRICE_LIST_LINES — the price list line entity, supplying the price list line identifier and the foreign key to the price list header. Also referenced via a SYNONYM.
  • SO_PRICE_LISTS — the price list header, supplying the price list name and price list identifier. Referenced via a SYNONYM.

The documented metadata also records the base objects QP_PRICE_LIST_PVT and QP_UTIL as packages referenced in the context of this object. These belong to the Advanced Pricing (QP) module and provide the pricing engine logic that governs how price list lines are interpreted and expanded. The join conditions are: the item flag must equal 'N', the item must match the price list line on INVENTORY_ITEM_ID, and the price list line must match the header on PRICE_LIST_ID. The DISTINCT keyword eliminates duplication that can arise when an item appears on multiple price list lines.

Key Columns

  • INVENTORY_ITEM_ID — the unique identifier of the non-shippable item.
  • DESCRIPTION — the item description from the item master.
  • ORGANIZATION_ID — the inventory organization in which the item is defined.
  • SHIPPABLE_ITEM_FLAG — filtered to 'N'; confirms the item is non-shippable.
  • NAME — the price list name.
  • PRICE_LIST_ID — the identifier of the price list header.
  • PRICE_LIST_LINE_ID — the identifier of the specific price list line carrying the item.

Common Use Cases and Queries

Typical uses include auditing which non-shippable items are priced, validating that service and warranty items exist on the correct price lists, and driving integration extracts that synchronize pricing data.

A basic query lists all non-shippable items with their price list context:

  • SELECT inventory_item_id, description, organization_id, name, price_list_id, price_list_line_id FROM apps.icx_nonship_items_v;

To restrict to a specific price list:

  • SELECT inventory_item_id, description, price_list_line_id FROM apps.icx_nonship_items_v WHERE price_list_id = :p_price_list_id;

To find a single item across price lists:

  • SELECT name, price_list_id, price_list_line_id FROM apps.icx_nonship_items_v WHERE inventory_item_id = :p_item_id;