Results for “ibe_bi_msite_dimn_v”

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

Overview

IBE_BI_MSITE_DIMN_V is a database view owned by the APPS schema in Oracle E-Business Suite, classified under the IBE (iStore) product family and holding a VALID status in both 12.1.1 and 12.2.2. The view is documented as a DBI (Daily Business Intelligence) view whose purpose is to return a list of stores. Its object name and the presence of the "DIMN" token indicate that it functions as a dimension source, supplying a de-duplicated set of store identifiers and display names to DBI and related analytical reporting layers.

Functionally, the view exposes storefronts that the querying user is permitted to see, while filtering out stores whose organization assignments are not covered by the active security profile. This intersection of identity columns and security filtering makes it a convenient, reusable source for LOV-style queries, BI dimension population, and cross-module reporting that needs a validated list of iStore storefronts rather than raw base tables.

Underlying Base Objects

The documented definition references three objects. The ETRM metadata for 12.2.2 records DUAL as a referenced base object within the APPS schema (exposed as a SYNONYM). The view text further identifies the material sources: IBE_BI_MSITEORG_MV, a materialized view that maps storefronts to organization identifiers, and IBE_MSITES_VL, the translatable base view holding the storefront master rows and their names. PER_ORGANIZATION_LIST supplies the organization list visible under the current security profile, and FND_PROFILE.VALUE('XLA_MO_SECURITY_PROFILE_LEVEL') retrieves the profile option that governs multi-org security for the session.

The join logic is significant: it returns distinct storefronts whose organizations are wholly contained within the security profile's organization list, using a NOT EXISTS with MINUS to exclude any storefront carrying an organization outside the permitted set. This is the mechanism that enforces MOAC-style access control at the view level.

Key Columns

• ID — Derived from IBE_MSITES_VL.MSITE_ID, the internal primary key of the storefront. Used as the surrogate key in DBI dimension tables and as the value passed to foreign keys elsewhere.
• VALUE — Derived from IBE_MSITES_VL.MSITE_NAME, the user-facing storefront name. This is the display label in lists of values and BI reporting prompts.

Both columns are aliased from the translatable store view, so the VALUE column respects the language context of the session through the _VL layer.

Common Use Cases and Queries

Typical uses include populating a BI dimension for storefront-level facts, seeding an LOV of accessible stores, and validating a storefront ID before invoking iStore or order-capture APIs.

A basic lookup of accessible stores follows:

• SELECT id, value FROM apps.ibe_bi_msite_dimn_v ORDER BY value;

A targeted lookup resolves a single storefront name:

• SELECT value FROM apps.ibe_bi_msite_dimn_v WHERE id = :p_msite_id;

Because the view already applies security-profile filtering, no additional org predicate is normally required; users with broader profiles see more rows, while restricted users see only their permitted storefronts. This behavior makes the view a dependable, security-aware dimension source for iStore and DBI reporting across releases 12.1.1 and 12.2.2.