Results for “ibe_dsp_context_b”

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

Overview

IBE_DSP_CONTEXT_B is a base table owned by the IBE (iStore) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the display contexts associated with templates and media attributes used for media rendering within the iStore application. Display contexts define the reusable presentation scopes under which media objects, sections, and related content fragments are organized and rendered to end users. The table therefore acts as a central definition point for the naming and typing of display contexts that other iStore media and template objects reference.

Under the heuristic Data Vault classification mined from the foreign key structure, IBE_DSP_CONTEXT_B is hub-leaning. That is, it behaves as a hub-like entity: it holds a stable business identity (a display context, uniquely named and typed) and is referenced by multiple dependent tables rather than aggregating measures itself. Treating it as a hub in a Data Vault model is a modeling suggestion; the surrounding language-dependent and object-level tables (IBE_DSP_CONTEXT_TL, IBE_DSP_OBJ_LGL_CTNT, IBE_DSP_SECTIONS_B) function as satellites or links that carry descriptive and relationship attributes.

Key Information Stored

The documented physical schema contains 13 columns. The most significant are summarized below.

• CONTEXT_ID — the surrogate primary key, defined by the constraint IBE_DSP_CONTEXT_B_PK. It is the identifier propagated to all child tables that reference a display context.
• ACCESS_NAME — the human-readable business name of the display context; together with CONTEXT_TYPE_CODE and ZD_EDITION_NAME it forms a business-key candidate (unique index IBE_DSP_CONTEXT_B_U2).
• CONTEXT_TYPE_CODE — the classification of the context, distinguishing the kinds of display contexts used for templates and media attributes.
• ITEM_ID — foreign key to JTF_AMV_ITEMS_B, linking the display context to the media item it serves.
• COMPONENT_TYPE_CODE — identifies the component type associated with the context.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-tenant or security-group-scoped access.
• ZD_EDITION_NAME — the edition discriminator introduced for online patching in 12.2.2; it participates in both unique indexes (U1: CONTEXT_ID, ZD_EDITION_NAME; U2: ACCESS_NAME, CONTEXT_TYPE_CODE, ZD_EDITION_NAME).
• OBJECT_VERSION_NUMBER — optimistic locking column used by the framework to detect concurrent updates.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN capture standard who/when audit information.

The distinction between the surrogate key (CONTEXT_ID) and the business-key candidates (ACCESS_NAME + CONTEXT_TYPE_CODE, and CONTEXT_ID + ZD_EDITION_NAME) is important for integration and data-load design.

Common Use Cases and Queries

Typical scenarios include resolving which display contexts a media item uses, enumerating available contexts by type, and joining contexts to their translated names or to the sections that reference them.

• Enumerate contexts by business name and type:
  SELECT context_id, access_name, context_type_code FROM ibe.ibe_dsp_context_b ORDER BY access_name;
• Resolve contexts linked to a media item:
  SELECT c.context_id, c.access_name FROM ibe.ibe_dsp_context_b c JOIN jtf_amv_items_b i ON c.item_id = i.item_id;
• Join to translations for localized display:
  SELECT c.access_name, t.source_lang, t.name FROM ibe.ibe_dsp_context_b c JOIN ibe.ibe_dsp_context_tl t ON c.context_id = t.context_id;
• Find sections that use a given display context:
  SELECT s.section_id FROM ibe.ibe_dsp_sections_b s WHERE s.display_context_id = :context_id;

Reporting use cases include auditing context definitions per security group, verifying edition-scoped data during 12.2.2 online patching, and identifying orphaned contexts with no translations or referenced objects.

Related Objects

The following objects are the most significant dependents and references for IBE_DSP_CONTEXT_B, based on the documented relationships.

• IBE_DSP_CONTEXT_TL — translation (language) table for contexts; joins on IBE_DSP_CONTEXT_TL.CONTEXT_ID = IBE_DSP_CONTEXT_B.CONTEXT_ID.
• IBE_DSP_OBJ_LGL_CTNT — object legal/content association; joins on IBE_DSP_OBJ_LGL_CTNT.CONTEXT_ID = IBE_DSP_CONTEXT_B.CONTEXT_ID.
• IBE_DSP_SECTIONS_B — section definitions; joins on IBE_DSP_SECTIONS_B.DISPLAY_CONTEXT_ID = IBE_DSP_CONTEXT_B.CONTEXT_ID.
• JTF_AMV_ITEMS_B — media item master; referenced via IBE_DSP_CONTEXT_B.ITEM_ID.
• FND_SECURITY_GROUPS — security group master; referenced via IBE_DSP_CONTEXT_B.SECURITY_GROUP_ID.

This relationship pattern confirms the hub-leaning classification: IBE_DSP_CONTEXT_B supplies the stable CONTEXT_ID identity consumed by translation, content, and section satellites.