Search Results ibe_dsp_lgl_phys_map_v




Overview
Explore in AI Chat

Overview

IBE_DSP_LGL_PHYS_MAP_V is an Oracle E-Business Suite (EBS) read-only view owned by the APPS schema. It belongs to the IBE (iStore) product family and is classified as a valid reporting object in both Oracle EBS 12.1.1 and 12.2.2. The view exists to present a denormalized, human-readable projection of the physical site translation mappings that iStore uses to associate content items with a legal (language) and physical site combination. Rather than requiring report authors and integration developers to join the underlying mapping, site, and language tables manually, the view supplies a single, already-joined result set.

The name of the object reflects its function: it maps legal/phys/ical site relationships for display and content localization in an iStore context. Because the view is defined WITH READ ONLY, it cannot be used to insert, update, or delete data and is intended exclusively for query, reporting, and integration extraction.

Underlying Base Objects

The ETRM metadata documents three referenced base objects for this view:

  • IBE_DSP_LGL_PHYS_MAP (SYNONYM) – the driving mapping object that holds the legal/physical site to language and item associations.
  • IBE_MSITES_VL (VIEW) – the multilingual, language-aware view of iStore physical sites, which provides the site name and its active date range.
  • FND_LANGUAGES_VL (VIEW) – the Oracle Foundation multilingual language view, from which the translated language description is obtained.

Joins are constructed as follows. The physical site identifier JDLPM.MSITE_ID is equated to JMV.MSITE_ID, and the site record is restricted by date so that only sites where START_DATE_ACTIVE <= SYSDATE and NVL(END_DATE_ACTIVE, SYSDATE) >= SYSDATE are returned. The language lookup on FND_LANGUAGES_VL is an outer join (FLV.LANGUAGE_CODE(+) = JDLPM.LANGUAGE_CODE), so rows are preserved even when no language description matches.

Key Columns

  • LGL_PHYS_MAP_ID – primary identifier of the legal/physical site mapping record.
  • ATTACHMENT_ID – identifier of the attachment associated with the mapping.
  • ITEM_ID – the inventory/content item identifier referenced by the mapping.
  • MSITE_ID – unique identifier of the iStore physical site.
  • MSITE_NAME – the translated display name of the physical site.
  • DEFAULT_SITE – flag indicating whether the mapping represents the default site.
  • LANGUAGE_CODE – the language code associated with the mapping.
  • LANGUAGE_DESCRIPTION – the human-readable description of the language, sourced from FND_LANGUAGES_VL; this is the column most relevant to the user's search term.
  • DEFAULT_LANGUAGE – flag indicating whether the language is the default for the mapping.
  • CONTENT_ITEM_KEY – key that ties the mapping to a specific content item.

Common Use Cases and Queries

Typical scenarios include validating the language coverage of iStore sites, reporting which content items are published per language and site, and populating integration extracts where a readable language description is required.

  • Listing all active sites with their mapped languages.
  • Identifying content items that lack a default language assignment.
  • Reporting duplicate or missing language mappings per item and site.

Sample query:

SELECT msite_name,
       language_code,
       language_description,
       content_item_key
FROM   apps.ibe_dsp_lgl_phys_map_v
WHERE  default_language = 'Y'
ORDER  BY msite_name, language_description;

Because the view is read-only and sources only current site records, it is well suited to runtime reporting and integration extraction without additional date filtering.