Results for “ibe_bi_msites_v”

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

Overview

IBE_BI_MSITES_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IBE (iStore) product family and validated as VALID in both Release 12.1.1 and 12.2.2. In the ETRM metadata it is classified as a DBI (Daily Business Intelligence) view whose stated purpose is to return a list of stores — that is, the set of merchant sites (MSITE) defined within the iStore application. Rather than exposing the full attribute set of a storefront, the view projects a single identifier column named ID, which corresponds to MSITE_ID on the iStore storefront entity.

The view exists primarily to support DBI reporting and dashboard queries that must reconcile iStore storefronts against the operating units a user is permitted to see. Because Oracle's DBI layer relies on security-aware, pre-filtered row sources, IBE_BI_MSITES_V encapsulates the business rule of "stores whose associated organizations are all within the viewer's security profile" into a reusable object. This makes it a natural candidate for inclusion in inline views, dashboard page regions, and custom concurrent programs that require a secured list of storefronts without directly manipulating materialized views or organization security tables.

Underlying Base Objects

The documented view text defines IBE_BI_MSITES_V over the materialized view IBE_BI_MSITEORG_MV, referenced twice under the aliases A and B. That materialized view holds the association between merchant site identifiers (MSITE_ID) and organization identifiers (ORG_ID). The second half of the MINUS set operation references PER_ORGANIZATION_LIST, the Oracle HRMS security view, filtered by SECURITY_PROFILE_ID equal to the value of the FND profile option XLA_MO_SECURITY_PROFILE_LEVEL. The ETRM metadata additionally records DUAL as a referenced base object (via a synonym), which reflects the FND_PROFILE.VALUE lookup embedded in the predicate.

The logic is a correlated NOT EXISTS with a nested MINUS: for each distinct MSITE_ID in the materialized view, the view confirms that no organization attached to that site falls outside the organization list accessible to the current security profile. Equivalently, a store is returned only when the set of organizations linked to it is a subset of the organizations the user may access. Stores mapped to organizations outside the profile are suppressed entirely.

Key Columns

• ID — The sole column exposed. It is the MSITE_ID of an iStore merchant site, aliased to ID for DBI consumption. In iStore data model terms this identifies a storefront record used by the store setup and publishing flows.

No storefront name, URL, currency, or organization column is exposed, so consumers requiring descriptive attributes must join back to the base iStore tables on MSITE_ID.

Common Use Cases and Queries

Typical usage is security-filtered enumeration of stores for DBI dashboards, LOV definitions, and validation logic. A representative query joining back to the store master is:

• List stores visible to the current user: SELECT id FROM apps.ibe_bi_msites_v ORDER BY id;
• Resolve store names: SELECT s.id, m.msite_name FROM apps.ibe_bi_msites_v s, apps.ibe_msites_vl m WHERE m.msite_id = s.id;
• Count accessible storefronts: SELECT COUNT(*) FROM apps.ibe_bi_msites_v;

Because the predicate depends on FND_PROFILE.VALUE('XLA_MO_SECURITY_PROFILE_LEVEL'), results vary by the responsibility and security profile of the session. In 12.2.2 the object remains a view over the same materialized view and organization security structures, so refresh timing of IBE_BI_MSITEORG_MV directly affects the freshness of returned store lists. The user-supplied search terms concerning backlinks and marketing strategy are unrelated to this database object and have no bearing on its definition or use.