Results for “ibe_dsp_context_tl”

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

Overview

IBE_DSP_CONTEXT_TL is the translation (language-dependent) table for the iStore display context base table, IBE_DSP_CONTEXT_B. It resides in the IBE schema and forms part of the Oracle iStore (IBE) module used in Oracle E-Business Suite releases 12.1.1 and 12.2.2. The table stores multilingual name and description text associated with each display context record defined in the base table, allowing translated content to be presented to users based on their session language.

Within a Data Vault modeling approach, the mined foreign-key structure suggests classifying this object as satellite-leaning. It does not introduce independent business entities; instead, it hangs off the IBE_DSP_CONTEXT_B parent through CONTEXT_ID and carries descriptive, language-scoped attributes. In EBS terms, the object behaves as a dependent translation entity rather than a hub or a link.

Key Information Stored

The table’s surrogate key is defined by the primary key constraint IBE_DSP_CONTEXT_TL_PK, which spans CONTEXT_ID and LANGUAGE. A second uniqueness rule, IBE_DSP_CONTEXT_TL_U1, covers CONTEXT_ID, LANGUAGE, and ZD_EDITION_NAME, representing the business-key candidate that also accommodates edition-aware (ZD) data.

• CONTEXT_ID — Foreign key to IBE_DSP_CONTEXT_B, identifying the parent display context whose translation is held in this row.
• LANGUAGE — The language code for the translated text; combined with CONTEXT_ID it forms the primary key.
• SOURCE_LANG — Indicates the language in which the source record was originally authored.
• NAME — The translated display name of the context, presented to end users.
• DESCRIPTION — The translated description text for the context.
• OBJECT_VERSION_NUMBER — Concurrency-control column used to detect conflicting updates.
• ZD_EDITION_NAME — Edition identifier supporting the edition-based redefinition model in 12.2.x.
• SECURITY_GROUP_ID — References FND_SECURITY_GROUPS and enforces multi-tenant data access.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS auditing columns recording creation and modification history.

Common Use Cases and Queries

Typical usage centers on resolving translated display context labels for a given session language. A common reporting pattern joins the translation table to the base table on CONTEXT_ID and filters by LANGUAGE:

• Retrieving translated context names for a specific language:

  SELECT b.context_id, t.name, t.description FROM ibe.ibe_dsp_context_b b, ibe.ibe_dsp_context_tl t WHERE b.context_id = t.context_id AND t.language = :p_lang;

• Auditing translations that exist for some languages but not others, using an outer join against the base table.
• Extracting all translated descriptions for a localization or content-management review.
• Checking security-group scoping for multi-org or multi-tenant deployments via SECURITY_GROUP_ID.

Related Objects

The most significant related objects derive from the documented foreign-key structure and the translation model:

• IBE_DSP_CONTEXT_B — The base table; joined on CONTEXT_ID, holding language-independent context data.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID to scope data access.
• IBE_DSP_CONTEXT_TL_PK — Primary key constraint on CONTEXT_ID and LANGUAGE.
• IBE_DSP_CONTEXT_TL_U1 — Unique index on CONTEXT_ID, LANGUAGE, and ZD_EDITION_NAME.

In practice, the translation table is queried together with the base context table and any iStore display or merchandising objects that reference display contexts, ensuring user-visible labels honor the configured language and edition.