Results for “item_no”

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

Overview

PMI_WHSE_CLS_V is a database view owned by the APPS schema within Oracle E-Business Suite, delivered as part of the Process Manufacturing Intelligence (PMI) product family. Its documented purpose is to expose a consolidated list of warehouse class items — that is, items defined in the inventory item master that participate in warehouse stocking relationships. The view carries a status of VALID in both the 12.1.1 and 12.2.2 releases and is documented in the ETRM repository as a synonym-backed view rather than a standalone table.

The view presents a narrow projection intended for reporting and integration consumption: a distinct set of item identifiers, item numbers, and primary item descriptions. Because it is a view, it introduces no physical storage of its own and inherits the read-consistency and security characteristics of the APPS schema. In practice it functions as a lightweight, denormalized access point for downstream inquiries, concurrent programs, and custom reports that need to resolve a warehouse-linked item to its descriptive text. A user searching on "item_desc1" would typically arrive at this object while attempting to join item identifiers to human-readable descriptions in a process manufacturing context.

Underlying Base Objects

The documented base object is IC_ITEM_MST, referenced through a SYNONYM within the APPS schema. IC_ITEM_MST is the Oracle Process Manufacturing inventory item master, which stores item definitions, stock-keeping attributes, and warehouse associations used across OPM modules.

The view definition applies a correlated subquery filter: it selects rows from IC_ITEM_MST where ITEM_ID appears in the set of WHSE_ITEM_ID values returned from IC_ITEM_MST itself. This self-referential pattern constrains the output to items that are explicitly designated as warehouse items in the same master table, effectively surfacing the warehouse class subset of the item population. The DISTINCT keyword eliminates duplicate combinations of ITEM_ID, ITEM_NO, and ITEM_DESC1 that could otherwise arise where multiple warehouse entries reference the same item identifier.

Because the sole documented base object is a synonym over IC_ITEM_MST, the view carries no additional dependency on warehouse master or organization tables at the definition level. Any organizational context is therefore resolved by the consumer, not by the view.

Key Columns

• ITEM_ID — The surrogate primary key of the inventory item. This is the primary join key used to relate the view to other item-keyed objects such as transaction, lot, or costing tables.
• ITEM_NO — The user-facing item number or code. It serves as the business identifier commonly displayed on reports and entered in inquiry screens.
• ITEM_DESC1 — The first (primary) description segment of the item. This is the column most often sought when users search for "item_desc1", as it supplies the human-readable label associated with an item number.

Common Use Cases and Queries

The view is typically used to enrich item identifiers with descriptive text in reporting queries, to validate that an item qualifies as a warehouse item, and to populate list-of-values or lookup extracts for process manufacturing analytics. A representative query retrieving descriptions for a set of items follows:

• Basic listing: SELECT ITEM_ID, ITEM_NO, ITEM_DESC1 FROM APPS.PMI_WHSE_CLS_V ORDER BY ITEM_NO;
• Targeted lookup: SELECT ITEM_NO, ITEM_DESC1 FROM APPS.PMI_WHSE_CLS_V WHERE ITEM_NO = :item_number;
• Description join: SELECT t.ITEM_ID, v.ITEM_NO, v.ITEM_DESC1 FROM APPS.PMI_WHSE_CLS_V v, some_transaction_table t WHERE t.ITEM_ID = v.ITEM_ID;

Because the view is read-only and defined over a single master object, it is safe for ad hoc querying, though performance depends on the indexing available on IC_ITEM_MST for ITEM_ID and WHSE_ITEM_ID.