Results for “item_no”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PMI_WHSE_CLS_LOV_V is a database view owned by the APPS schema in Oracle E-Business Suite, documented under the Process Manufacturing Intelligence (PMI) product family and classified as obsolete in the ETRM reference. Its stated purpose is to expose warehouse class list-of-values (LOV) data. The view presents a deliberately narrow projection of item information, restricted to three columns, and is intended to feed selection screens, concurrent reporting, or integration routines that require a lightweight, distinct list of item identifiers and descriptions rather than the full item master record.

Because the object is marked obsolete, it should be treated as a legacy artifact. In 12.1.1 and 12.2.2 environments it may still exist in a VALID state in the database, particularly where historical PMI components were retained, but Oracle no longer actively maintains or supports the object. Any new development should avoid a hard dependency on this view; existing reports that reference it should be reviewed against supported alternatives such as the inventory item master views.

Underlying Base Objects

The view text documented in the ETRM metadata is:

• SELECT DISTINCT ITEM_ID, ITEM_NO, ITEM_DESC1 FROM IC_ITEM_MST WHERE ITEM_ID IN (SELECT WHSE_ITEM_ID FROM IC_ITEM_MST)

The only referenced base object is IC_ITEM_MST (synonym), the Process Manufacturing item master table. The view therefore depends on a single underlying source. The outer query selects item identity and description fields, while the inner correlated subquery filters the result set to those ITEM_ID values that also appear in the WHSE_ITEM_ID column. In effect, the view returns items that are referenced as warehouse items within the same table.

The DISTINCT keyword collapses duplicate rows produced by the self-referencing predicate, ensuring each qualifying item appears once in the result set. No joins to auxiliary tables are documented, so the view remains a thin, single-table projection with a self-filter.

Key Columns

• ITEM_ID — The internal numeric primary key for the item. This is the value used to establish foreign-key relationships with other application tables and is the column most commonly used for programmatic lookups.
• ITEM_NO — The user-facing item number (the flexible or concatenated item identifier). This is the value users typically type or select in an LOV.
• ITEM_DESC1 — The first (primary) description segment of the item. This is the descriptive text displayed alongside the item number. The user search term "item_desc1" maps directly to this column, indicating the view is frequently queried to retrieve or filter on item description text.

Because only these three columns are exposed, the view does not carry item status, organization, UOM, or category information. Consumers requiring those attributes must query the item master directly.

Common Use Cases and Queries

The view is typically used to populate a warehouse class LOV or to resolve an item description from an item identifier. A basic lookup by item number is:

• SELECT ITEM_ID, ITEM_NO, ITEM_DESC1 FROM APPS.PMI_WHSE_CLS_LOV_V WHERE ITEM_NO = :item_no;

Filtering on the description column is common when partial descriptions are known:

• SELECT ITEM_ID, ITEM_NO, ITEM_DESC1 FROM APPS.PMI_WHSE_CLS_LOV_V WHERE UPPER(ITEM_DESC1) LIKE UPPER(:fragment || '%');

To resolve a description from a stored ITEM_ID in a custom report:

• SELECT l.ITEM_NO, l.ITEM_DESC1 FROM APPS.PMI_WHSE_CLS_LOV_V l WHERE l.ITEM_ID = :stored_item_id;

Given the obsolete status, queries should be wrapped in validation logic or redirected to supported item master views where feasible. Performance is generally acceptable because the view operates over a single table with a distinct projection, but the self-referencing IN predicate can be costly on large item masters; indexing on ITEM_ID and WHSE_ITEM_ID mitigates this.