Results for “ibe_dsp_context_vl”

42 results




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

Overview

IBE_DSP_CONTEXT_VL is a read-only, language-aware (VL suffix, "view with translation") database view owned by the APPS schema in Oracle E-Business Suite. It is part of the IBE (iStore / Oracle iStore) product family, which supports the storefront, catalog browsing, and personalized display capabilities of Oracle's E-Business Suite. The view exposes the definition of display contexts — reusable framework constructs that determine how product, item, and merchandising content is rendered and grouped on an iStore storefront — together with the translated (language-specific) name and description of each context.

Because the "_VL" view resolves the current session language through USERENV('LANG'), it is suitable for both reporting queries executed from a locale-specific session and integration or personalization logic that must present localized context labels. In the context of the user search term "component_type_code", the view is notable for exposing COMPONENT_TYPE_CODE alongside the context definition, allowing developers and report authors to identify, filter, or group display contexts by the type of component (for example, section, template, or display element) they govern.

The view is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2, and appears in the ETRM (E-Business Suite Technical Reference Manual) as a documented APPS view. Its accessibility as a standard APPS object makes it a common reference point for custom reports, OAF/Forms personalization queries, and diagnostics of iStore merchandising configuration.

Underlying Base Objects

Per the documented ETRM metadata, IBE_DSP_CONTEXT_VL is defined over two base objects:

  • IBE_DSP_CONTEXT_B — the base table (referenced via a synonym) holding the non-translated, language-independent attributes of a display context, including identifiers, audit columns, the access name, the context type code, the item reference, and the component type code.
  • IBE_DSP_CONTEXT_TL — the translation table (referenced via a synonym) holding the language-specific text, specifically NAME and DESCRIPTION, keyed by CONTEXT_ID and LANGUAGE.

The view joins these on CONTEXT_ID and restricts the translation row to the session language via T.LANGUAGE = USERENV('LANG'). This is the classic Oracle "_B / _TL / _VL" pattern: the _B table stores the description-flexible or code-related data, the _TL table stores translatable text, and the _VL view presents the joined, localized result. Because the join is an inner join, contexts lacking a translation row for the current language would not appear, which is a consideration when writing diagnostic queries.

Key Columns

The view exposes the following columns as documented in the ETRM metadata:

  • ROW_ID — the ROWID of the base (_B) row, useful for row identification and debugging.
  • CONTEXT_ID — primary key of the display context; the join key between the base and translation tables.
  • OBJECT_VERSION_NUMBER — optimistic locking / concurrency version indicator maintained by the underlying entity.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard "WHO" audit columns, useful for change tracking and data lineage reporting.
  • ACCESS_NAME — the internal access or identification name for the context, typically the value referenced in application code and configuration.
  • CONTEXT_TYPE_CODE — the classification of the context (the type of display context, or its role in the iStore framework).
  • ITEM_ID — the inventory item associated with the context, allowing linkage to the item master for product-level personalization and reporting.
  • NAME — the translated, language-specific name of the context.
  • DESCRIPTION — the translated, language-specific description.
  • COMPONENT_TYPE_CODE — the code denoting the type of component associated with the context. This is the column most directly relevant to the user's search. It allows queries to isolate display contexts that drive a specific component type within the iStore rendering stack.

Common Use Cases and Queries

Typical uses include iStore setup verification, troubleshooting display or personalization issues, and reporting on context configuration by type or component type. Because it is localized, it is well suited to multi-language storefront analysis.

Example 1 — list contexts of a given component type:

SELECT context_id,
       access_name,
       context_type_code,
       component_type_code,
       name,
       item_id
FROM   apps.ibe_dsp_context_vl
WHERE  component_type_code = :p_component_type_code
ORDER  BY access_name;

Example 2 — inventory of contexts by type and component:

SELECT context_type_code,
       component_type_code,
       COUNT(*) context_count
FROM   apps.ibe_dsp_context_vl
GROUP  BY context_type_code, component_type_code
ORDER  BY 1, 2;

Example 3 — recently modified contexts with item linkage:

SELECT c.context_id,
       c.access_name,
       c.name,
       c.last_updated_by,
       c.last_update_date,
       c.item_id
FROM   apps.ibe_dsp_context_vl c
WHERE  c.last_update_date >= SYSDATE - 30
ORDER  BY c.last_update_date DESC;

These queries reflect the documented column set and are safe to run under the current session language, since the view already enforces the USERENV('LANG') join. Because the metadata provided lists IBE_DSP_CONTEXT_B and IBE_DSP_CONTEXT_TL as the only referenced base objects, no further joins are required to obtain the localized context attributes.