Search Results customer_item




Overview
Explore in AI Chat

Overview

MSC_X_ITEMS_LOV_V is a database view owned by the APPS schema within the Oracle E-Business Suite environment (documented for 12.1.1 and 12.2.2). It belongs to the MSC product family, Advanced Supply Chain Planning, and its status is VALID in the ETRM repository. The view is designed to serve as a List of Values (LOV) source, presenting a simplified, presentation-oriented projection of item data held in the MSC_ITEMS synonym. Rather than exposing the full planning item master, it flattens the record into a stable set of columns suitable for value-list pickers, concurrent report parameters, and lightweight integration queries.

The view is notable for the presence of dedicated attribute columns — CHANNEL_MASTER_ITEM, CUSTOMER_ITEM, and SUPPLIER_ITEM — that are exposed as part of the column list. In the documented view text these three columns are returned as literal NULL values, so the LOV effectively behaves as a single unified item list covering the standard item definition, while preserving the column signature that downstream consumers may reference.

Underlying Base Objects

The documented metadata records a single referenced base object: MSC_ITEMS, which is present in the environment as a SYNONYM. The view text confirms that all returned data originate from MSC_ITEMS, aliased as CM in the defining query. Consequently, the view is a relatively thin wrapper: it performs no joins, unions, or aggregations in the documented definition. Any filtering, security, or organizational scoping applied by the planning item master is inherited directly, and the view adds only column aliasing plus the three NULL placeholder expressions that shape the LOV interface. Because the base is a synonym rather than a physical table, the ultimate source object is resolved through the APPS synonym chain at runtime.

Key Columns

  • INVENTORY_ITEM_ID — the surrogate primary key of the item, mapped from CM.INVENTORY_ITEM_ID; the value normally returned by an LOV hidden key.
  • ITEM_NAME — the user-facing item identifier, mapped from CM.ITEM_NAME; this is the descriptive value displayed to users in the list of values.
  • CHANNEL_MASTER_ITEM — exposed as NULL; a reserved placeholder for channel-master item associations.
  • CUSTOMER_ITEM — exposed as NULL; a placeholder aligned to customer-specific item numbering, relevant to the "customer_item" search context.
  • SUPPLIER_ITEM — exposed as NULL; a placeholder for supplier item references.
  • DESCRIPTION — the item description, mapped from CM.DESCRIPTION, used for additional context in pickers and reports.
  • CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS audit columns carried through from MSC_ITEMS for traceability.

Common Use Cases and Queries

The primary use case is driving LOV pickers for planning and supply chain forms and reports, where the developer needs an item identifier plus a display name and description without the overhead of the full planning item entity. A typical selection returns the key, name, and description:

  • SELECT INVENTORY_ITEM_ID, ITEM_NAME FROM APPS.MSC_X_ITEMS_LOV_V WHERE UPPER(ITEM_NAME) LIKE :p_name ORDER BY ITEM_NAME;
  • SELECT INVENTORY_ITEM_ID, ITEM_NAME, DESCRIPTION FROM APPS.MSC_X_ITEMS_LOV_V WHERE INVENTORY_ITEM_ID = :p_item_id;

Because CUSTOMER_ITEM, SUPPLIER_ITEM, and CHANNEL_MASTER_ITEM resolve to NULL, queries that filter on those columns will return no rows; consumers must join to the appropriate customer- or supplier-item source tables to obtain those values. Date-bounded extracts and incremental integration feeds can use the audit columns:

  • SELECT INVENTORY_ITEM_ID, ITEM_NAME, LAST_UPDATE_DATE FROM APPS.MSC_X_ITEMS_LOV_V WHERE LAST_UPDATE_DATE >= :p_since;

In all cases the view should be accessed through the APPS synonym with appropriate grants, and its simplicity makes it a reliable, low-cost source for item value lists across the MSC module.