Search Results display_height

Overview

IBE_DSP_ATTACHMENTS_V is an APPS-owned database view that exposes display attachment metadata for the Oracle iStore (IBE) module. Oracle iStore uses media and file attachments to enrich item detail pages, category presentations, and merchandising content in both the customer-facing storefront and the applications administrator UI. This view joins the generic attachment infrastructure of the Application Media Viewer (JTF_AMV) with an iStore-specific mapping table that controls where and how a given attachment is presented across logical and physical sites.

The object is classified as a VIEW with a VALID status in the APPS schema and is documented for Oracle EBS 12.1.1 and 12.2.2. Because it consolidates multilingual item descriptions, file identifiers, display geometry, and site assignment into a single projection, it functions as a reporting and integration access point for attachment-driven content in the iStore catalog. Users searching on the term "default_msite" typically encounter this view because the DEFAULT_MSITE column governs the default mobile site assignment for the attachment record.

Underlying Base Objects

The view is defined over three documented base objects, all resolved through synonyms or views in the APPS schema:

• JTF_AMV_ATTACHMENTS (SYNONYM) — the attachment repository, referenced as V1. Supplies FILE_NAME, FILE_ID, DISPLAY_WIDTH, DISPLAY_HEIGHT, SECURED_FLAG, and the ATTACHMENT_ID used as a join key.
• JTF_AMV_ITEMS_VL (VIEW) — the translated item view, referenced as V2. Supplies DESCRIPTION, ITEM_ID, and ACCESS_NAME, with LANGUAGE_CODE carried through the join.
• IBE_DSP_LGL_PHYS_MAP (SYNONYM) — referenced as A. This iStore mapping table links an ATTACHMENT_ID to an ITEM_ID and records the language, site, and default-site attributes that drive storefront presentation.

The join predicates are A.ATTACHMENT_ID = V1.ATTACHMENT_ID and A.ITEM_ID = V2.ITEM_ID. Both the attachment and item queries are constrained to APPLICATION_ID = 671, which is the application identifier for Oracle iStore. This constraint isolates iStore content from attachments belonging to other JTF_AMV consumers. The view text also selects A.MSITE_ID and A.DEFAULT_SITE, which are exposed to the caller under the column labels referenced in the documentation.

Key Columns

The view projects twelve columns. Noteworthy entries include:

• FILE_NAME — the stored file name of the attachment, useful for locating or linking the underlying media object.
• DESCRIPTION — the language-specific item description from JTF_AMV_ITEMS_VL.
• LANGUAGE_CODE / DEFAULT_LANGUAGE — the language of the item record and the default language flag for the mapped attachment, supporting multilingual storefronts.
• ITEM_ID / LOGICAL_ID — identifiers for the iStore item and the logical entity associated with the mapping record.
• ACCESS_NAME — the access key under which the item content is addressed.
• SITE_ID / DEFAULT_MSITE — the physical site identifier and the default mobile site indicator. DEFAULT_MSITE is the column most directly associated with "default_msite" searches and identifies which mobile site assignment is treated as default for the attachment.
• FILE_ID, DISPLAY_WIDTH, DISPLAY_HEIGHT — the file reference and rendering dimensions used by the storefront UI.
• SECURED_FLAG — indicates whether the attachment is access-controlled.

Common Use Cases and Queries

Typical uses include auditing iStore attachment content, verifying multilingual coverage, and reconciling display geometry or security flags across sites. The following query lists default mobile site attachments with their descriptions:

• SELECT item_id, file_name, description, language_code, default_msite, display_width, display_height FROM apps.ibe_dsp_attachments_v WHERE default_msite IS NOT NULL ORDER BY item_id;
• SELECT file_id, file_name, secured_flag FROM apps.ibe_dsp_attachments_v WHERE item_id = :p_item_id;
• SELECT language_code, COUNT(*) FROM apps.ibe_dsp_attachments_v GROUP BY language_code;

Because the view performs several joins, queries should filter on ITEM_ID or ACCESS_NAME where possible to limit result sets. All access should be performed with the APPS schema or an appropriately privileged reporting responsibility.