Search Results inv_item_description




Overview
Explore in AI Chat

Overview

IBE_DSP_TPL_ITEM_CTG_V is an APPS-owned read-only view within the Oracle E-Business Suite iStore (IBE) module. It presents a denormalized, presentation-ready join between iStore template category definitions and the inventory items assigned to those categories. The view is part of the iStore "Display" (IBE_DSP) family of objects used to render storefront content, category landing pages, and merchandising templates. Because it is defined with WITH READ ONLY, it is intended exclusively for query and reporting purposes and cannot be used as the target of DML within iStore or any downstream integration. In EBS 12.1.1 and 12.2.2 the object remains VALID and is published from the APPS schema for use by storefront pages, personalizations, and custom concurrent or BI Publisher reports that need to correlate iStore template categories with MTL item descriptions.

Underlying Base Objects

The view is defined over five documented base objects. IBE_DSP_TPL_CTG supplies the template category identifier (TPL_CTG_ID) and links the category to a template item (ITEM_ID); it is surfaced as a synonym in the APPS schema. IBE_DSP_AMV_ITEMS_V contributes the display-oriented item attributes: ITEM_NAME, the item-level DESCRIPTION, and FILE_NAME (typically the image or media file associated with the iStore item). MTL_CATEGORIES_VL is the multilingual category view; it is joined on CATEGORY_ID to resolve the category that the template category references. MTL_SYSTEM_ITEMS_VL is the multilingual item master view, joined on INVENTORY_ITEM_ID to return the inventory item description. MTL_ITEM_CATEGORIES is the item-to-category assignment table, joined on CATEGORY_ID and INVENTORY_ITEM_ID, binding items into the categories. The join chain therefore runs template category to category, category to item-category assignment, item-category assignment to item master, and iStore item view to inventory item. Because both MTL_CATEGORIES_VL and MTL_SYSTEM_ITEMS_VL are _VL views, the query is language-sensitive and returns descriptions in the session's current language.

Key Columns

  • TPL_CTG_ID — Identifier of the iStore template category from IBE_DSP_TPL_CTG; the grouping key for storefront templates.
  • ITEM_ID — iStore-side item identifier from IBE_DSP_TPL_CTG / IBE_DSP_AMV_ITEMS_V, distinct from the inventory item key.
  • ITEM_NAME — The iStore display name of the item (JAIV.ITEM_NAME), used on storefront pages.
  • ITEM_DESCRIPTION — The iStore item description (JAIV.DESCRIPTION), aliased to distinguish it from the inventory description.
  • FILE_NAME — The associated media/image file name from the iStore item view, typically the merchandising graphic.
  • INVENTORY_ITEM_ID — The MTL system item identifier, the join key to inventory and order capture.
  • INV_ITEM_DESCRIPTION — The multilingual inventory item description from MTL_SYSTEM_ITEMS_VL.

Common Use Cases and Queries

Typical uses include validating that every iStore template category has at least one item assigned, reconciling storefront display names against inventory descriptions, and driving catalog-rendering reports. A representative query lists items for a given template category:

SELECT tpl_ctg_id, item_id, item_name, file_name, inventory_item_id, inv_item_description FROM apps.ibe_dsp_tpl_item_ctg_v WHERE tpl_ctg_id = :p_tpl_ctg_id;

To find template categories with no items (missing assignments), outer-join the template category source against this view. Because MTL_CATEGORIES_VL was the object returned by the user's search for mtl_categories_vl, a common variation extracts the category context by joining MTL_CATEGORIES_VL on CATEGORY_ID when additional category hierarchy detail is required. Note that duplicate rows can appear when an inventory item belongs to multiple categories referenced by the same template category; DISTINCT or aggregation should be applied as needed.