Results for “store_name”

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

Overview

IBE_STORES_VL is a translatable (TL) view in the Oracle iStore (IBE) module of Oracle E-Business Suite. It presents the language-specific, user-facing attributes of iStore storefronts by joining the base table IBE_STORES_B with its translation table IBE_STORES_TL. The "_VL" suffix indicates that the view returns rows filtered to the current session language, using the standard Oracle EBS multilingual pattern (USERENV('LANG')). This view is the primary reporting and integration interface for storefront names and descriptions, allowing concurrent programs, OBIEE extracts, and custom integrations to retrieve store metadata without manually resolving the base/translation table relationship. In the ETRM documentation, implementation status is listed as "Not implemented in this database," meaning the view is defined by the seed data but was not instantiated in that particular environment; no owner or referenced base objects were separately documented at the 12.2.2 level.

Underlying Base Objects

The view is defined over two physical tables:

• IBE_STORES_B — the base table holding language-independent storefront attributes, identified by STORE_ID and including audit columns, DFF attributes (ATTRIBUTE_CATEGORY through ATTRIBUTE15), and OBJECT_VERSION_NUMBER for optimistic locking.
• IBE_STORES_TL — the translation table holding language-specific text, including STORE_NAME, STORE_DESCRIPTION, LANGUAGE, and SOURCE_LANG.

The defining predicate is S.STORE_ID = L.STORE_ID AND L.LANGUAGE = USERENV('LANG'), with the view exposing each B-table column alongside the translated columns from the TL table. Because the join is inner, only stores with a translation row in the session language are returned.

Key Columns

• ROW_ID — the rowid of the IBE_STORES_B row, useful for direct row addressing.
• STORE_ID — the primary key linking base and translation records; the join key for all dependent objects.
• STORE_NAME — the translated display name of the storefront in the session language.
• STORE_DESCRIPTION — the translated descriptive text for the storefront. This is the column users most frequently search for ("store_description") when building reports on storefront content.
• LANGUAGE / SOURCE_LANG — the language of the returned translation and the language from which it was seeded.
• OBJECT_VERSION_NUMBER — optimistic locking version, important for any DML or integration that writes back.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield columns for customer-specific store attributes.

Common Use Cases and Queries

Typical uses include storefront inventory reports, iStore administration dashboards, and OBIEE/BI Publisher extracts that need localized store names and descriptions.

• List all active stores with their localized names and descriptions:

  SELECT store_id, store_name, store_description
  FROM   ibe_stores_vl
  ORDER BY store_name;

• Retrieve a specific storefront's description by ID:

  SELECT store_id, store_name, store_description
  FROM   ibe_stores_vl
  WHERE  store_id = :p_store_id;

• Join to other iStore objects (e.g., sections or content items) using STORE_ID to attribute content to a named storefront.
• Filter for stores with missing or empty descriptions for content remediation:

  SELECT store_id, store_name
  FROM   ibe_stores_vl
  WHERE  store_description IS NULL;

Because results are filtered by USERENV('LANG'), the same query returns different text depending on the responsibility language; reports intended for a fixed language should set the session language explicitly or join directly to IBE_STORES_TL.