Search Results payment_method_id

Overview

ICX_NONSHIP_DUMMY_LOV_V is a lightweight Oracle E-Business Suite view owned by the APPS schema and registered as VALID at the time of documentation. It belongs to the ICX product family, which underpins Oracle iProcurement and related self-service purchasing functionality. The view is described in the ETRM metadata as the "Non Shippable Item Description View" and is catalogued as an implementation object rather than a base table.

Functionally, the view presents a list of value (LOV) source for items that are not shippable. The name includes "DUMMY_LOV", indicating that it exists to satisfy a dependent LOV field on a form or self-service page rather than to serve as a substantive transactional data source. In the ICX/iProcurement context, non-shippable items are typically services, subscriptions, or intangible goods that do not require shipment or delivery processing. Because no shipping attributes apply, the LOV for such items can be limited to descriptive identification.

The view is defined with a single driving condition, returning rows where the item's shippable flag is set to 'N'. It contributes to requisition, catalog, and purchasing flows that must distinguish shippable items from service-type items.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, ICX_NONSHIP_DUMMY_LOV_V references a single base object: MTL_SYSTEM_ITEMS_KFV, which is exposed as a synonym. MTL_SYSTEM_ITEMS_KFV is the key flexfield view of MTL_SYSTEM_ITEMS, the master item definition table in Oracle Inventory. The "KFV" suffix denotes that this object resolves the item key flexfield (concatenated segments) into a single descriptive value, and it also surfaces the DESCRIPTION column. The view therefore inherits item master attributes, including SHIPPABLE_ITEM_FLAG, without duplicating them.

No other tables, joins, or aggregations are documented. The dependency chain is deliberately simple: MTL_SYSTEM_ITEMS_KFV supplies both the description text and the shippability filter. Because MTL_SYSTEM_ITEMS_KFV is itself built on MTL_SYSTEM_ITEMS and related inventory structures, changes to item master attributes are immediately reflected in this view at query time. As a view, ICX_NONSHIP_DUMMY_LOV_V holds no stored data of its own and performs no materialization.

Key Columns

The metadata records two columns:

• ITEM_ID — The item identifier. Although the column name appears without a table qualifier in the view text, it corresponds to the item primary key from the underlying item inventory structure, used to anchor the LOV selection back to the item being chosen.
• PAYMENT_METHOD_ID — This column is documented as part of the view's column list. It is commonly exposed as a NULL placeholder to support dependent LOV and form binding requirements, where the underlying page expects a payment method identifier. When the LOV is invoked for non-shippable items, no shipping/payment linkage is meaningful, so the value resolves to NULL.

The view text selects MSI.DESCRIPTION along with a literal NULL, which aligns with the documented column layout. Users searching for "payment_method_id" should note that this column does not carry functional payment data in this view; it is a structural placeholder.

Common Use Cases and Queries

This view is used when configuring, testing, or debugging LOV definitions that must return descriptions of non-shippable items. Typical scenarios include iProcurement catalog setup, requisition entry pages requiring service-item selection, and validation of dependent LOV behavior against MTL_SYSTEM_ITEMS_KFV.

A representative query follows:

• SELECT ITEM_ID, PAYMENT_METHOD_ID FROM APPS.ICX_NONSHIP_DUMMY_LOV_V; — Returns the ITEM_ID and the NULL placeholder PAYMENT_METHOD_ID for every non-shippable item.
• SELECT ITEM_ID, PAYMENT_METHOD_ID FROM APPS.ICX_NONSHIP_DUMMY_LOV_V ORDER BY ITEM_ID; — An ordered variant suitable for verifying the LOV result set.

Direct queries against the view via the APPS schema (or a synonym pointing to it) are safe and read-only, since the object performs no DML. Troubleshooting typically involves comparing the returned row count against MTL_SYSTEM_ITEMS_KFV filtered by SHIPPABLE_ITEM_FLAG = 'N' to confirm that LOV behavior matches item master configuration. The view should not be used for payment processing or for retrieving actual payment method values, as that column is not populated with transactional data.