Results for “ibe_bis_list_msites_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IBE_BIS_LIST_MSITES_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite iStore (IBE) product module. It is classified as a DBI (Daily Business Intelligence) view whose stated purpose is to return a list of stores, or multistore sites, defined in the iStore application. The view exposes a simple two-column lookup structure consisting of an identifier and a display value, which is the conventional pattern for list-of-values (LOV) drivers and DBI dashboard prompts.

In Oracle EBS 12.1.1 and 12.2.2, this object supports the iStore store-selection infrastructure used by DBI dashboards and reporting pages, where a user or a program must resolve the set of multistore sites to which the current responsibility has visibility. Because the view is defined over a materialized view (IBE_BI_MSITEORG_MV) and an organizational security mechanism, its output is implicitly filtered by the site-level data access defined for the session. Unlike transactional iStore views, this object is intended for read-only metadata and prompt resolution rather than for order capture or catalog processing. Its status is VALID, indicating the compiled definition is present and usable in the database.

Underlying Base Objects

The view is defined over two principal iStore objects: IBE_BI_MSITEORG_MV, a DBI materialized view that maps multistore sites (MSITE_ID) to organizations (ORGANIZATION_ID), and IBE_MSITES_VL, the multilingual (translated) multistore site view that supplies the site name. The join between these two objects on MSITE_ID links the organization mapping to the descriptive site name. A third referenced object, PER_ORGANIZATION_LIST, participates through a MINUS subquery that enforces organization-level security filtering against the FND_PROFILE value XLA_MO_SECURITY_PROFILE_LEVEL.

The view text applies a NOT EXISTS construct that subtracts, for each multistore site, the set of organizations available through the active security profile. Sites are retained only where they are not left with an unmatched organization once the security-filtered organization list is removed. The ETRM metadata further records DUAL as a referenced base object, consistent with the profile value resolution performed at query time. Because IBE_BI_MSITEORG_MV is a materialized view, the freshness of the returned store list depends on the refresh schedule of the underlying DBI collection.

Key Columns

• ID — The multistore site identifier (MSITE_ID). This is the unique key passed to downstream queries, functions, or dashboard parameters when a specific store must be selected.
• VALUE — The multistore site name (MSITE_NAME), sourced from the translated view IBE_MSITES_VL, suitable for display in prompts and list-of-values regions.

The DISTINCT operator ensures each site appears once in the result set even where multiple organization mappings exist, so the view behaves as a clean picklist of stores rather than a mapping table.

Common Use Cases and Queries

The primary use case is populating a store selection prompt in an iStore DBI dashboard or an Oracle Reports/BI Publisher parameter list. A typical query returns the available stores for the current responsibility's security profile:

• SELECT ID, VALUE FROM APPS.IBE_BIS_LIST_MSITES_V ORDER BY VALUE; — retrieves the full list of accessible stores in display order.
• SELECT VALUE FROM APPS.IBE_BIS_LIST_MSITES_V WHERE ID = :p_msite_id; — resolves the store name for a known identifier in a report or concurrent program.

Administrators may also use the view to validate which multistore sites remain visible under a given security profile, which is useful when troubleshooting why a store is missing from an iStore reporting page. Because the filtering derives from XLA_MO_SECURITY_PROFILE_LEVEL, verifying that profile setting is the standard first step when results are unexpectedly empty. Query performance is generally acceptable for prompt use because the DISTINCT result set over multistore sites is small relative to transactional volumes.