Search Results party_access_code




Overview

IBE_MSITES_VL is a seeded, read-only view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the IBE (iStore) product family and exposes the definition of iStore merchant sites — the storefront records that drive Oracle iStore navigation, catalog presentation, and customer-facing shopping behavior. Because consumer-facing storefront attributes are translatable, the view follows Oracle's standard "_VL" (view with language) convention: it joins the non-translatable base table to its translation table and filters the translation row by the session's runtime language, so that each query returns exactly one row per merchant site in the language appropriate to the calling user.

The view is marked VALID and is intended for reporting, diagnostics, and integration rather than for direct DML. Application code and concurrent programs that need to read or display merchant site configuration typically select from this view instead of joining the underlying tables manually, since the view already resolves the language join and surfaces a stable, denormalized column list.

Underlying Base Objects

The documented ETRM metadata lists two referenced base objects, both accessed through APPS synonyms:

  • IBE_MSITES_B — the base ("_B") table holding the non-translatable merchant site attributes, including primary key, WHO columns, site type, domain, store reference, profile, theme, and the descriptive flexfield attribute columns.
  • IBE_MSITES_TL — the translation ("_TL") table holding MSITE_NAME and MSITE_DESCRIPTION in each installed language.

The view text confirms an inner join on MSITE_ID between the two tables, combined with the predicate L.LANGUAGE = USERENV('LANG'). The ROW_ID column is derived from the base table ROWID rather than stored physically. Because the join is driven by the session language, a site with no translation row for the current language will not appear in the result set.

Key Columns

Common Use Cases and Queries

A typical use is to resolve the root section of a storefront given a site name or ID, for example when diagnosing navigation or catalog publishing problems:

  • Retrieve the root section for all active sites: SELECT msite_id, msite_name, msite_root_section_id FROM ibe_msites_vl WHERE sysdate BETWEEN start_date_active AND NVL(end_date_active, sysdate + 1);
  • Look up a site by name: SELECT msite_id, msite_root_section_id FROM ibe_msites_vl WHERE msite_name = :p_name;
  • List the master site: SELECT msite_id, msite_name FROM ibe_msites_vl WHERE master_msite_flag = 'Y';

Because the view filters by USERENV('LANG'), reports that must show all languages should query IBE_MSITES_TL directly rather than this view.