Results for “jtf_dsp_context_tl”

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

Overview

JTF_DSP_CONTEXT_TL is a translation (TL) table in the JTF — CRM Foundation product of Oracle E-Business Suite, present and valid in both release 12.1.1 and 12.2.2. It stores the language-specific, translatable attributes for records defined in the base table JTF_DSP_CONTEXT_B. In the Oracle EBS multi-language architecture, a base (or "_B") table holds language-independent columns and a single row per entity, while the corresponding "_TL" table holds the translatable text — typically name and description — with one row per installed language. JTF_DSP_CONTEXT_TL therefore provides the localized display text for the display context definitions used by the CRM Foundation display and personalization framework.

From a dimensional modeling perspective, the FK/PK structure suggests a satellite-leaning classification. The table carries descriptive, language-dependent attributes that augment the parent context entity rather than serving as an independent hub or a pure association link. Under a Data Vault heuristic the CONTEXT_ID points back to JTF_DSP_CONTEXT_B as a hub-like parent, and the translation rows behave as satelite data keyed to that hub plus a language discriminator.

Key Information Stored

The table contains 12 documented columns. The most significant are:

• CONTEXT_ID — Surrogate identifier for the parent display context. Part of the composite primary key and a foreign key to JTF_DSP_CONTEXT_B.CONTEXT_ID.
• LANGUAGE — The language code of the translated row. Combined with CONTEXT_ID it forms the primary key JTF_DSP_CONTEXT_TL_PK.
• SOURCE_LANG — The language of the source text from which the translation originates, used by the translation framework.
• NAME — The translated, language-specific display name of the context.
• DESCRIPTION — The translated descriptive text for the context.
• OBJECT_VERSION_NUMBER — Optimistic locking column used for concurrent-update control.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant / data-security partitioning.
• CREATED_BY, CREATION_DATE — Standard who-columns recording row creation audit.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard who-columns recording the last modification audit trail.

The composite primary key (CONTEXT_ID, LANGUAGE) is the true unique business-and-technical key. CONTEXT_ID alone is the surrogate reference to the base entity; LANGUAGE is the discriminator that makes each row unique. No separate single-column unique index is documented beyond this primary key.

Common Use Cases and Queries

Typical uses include retrieving localized context names for UI rendering, auditing translation completeness across languages, and reporting on untranslated contexts. A common join retrieves the base row with its translation:

• SELECT b.context_id, t.language, t.name, t.description FROM jtf_dsp_context_b b, jtf_dsp_context_tl t WHERE b.context_id = t.context_id AND t.language = USERENV('LANG');
• Translation-gap analysis: SELECT b.context_id FROM jtf_dsp_context_b b WHERE NOT EXISTS (SELECT 1 FROM jtf_dsp_context_tl t WHERE t.context_id = b.context_id AND t.language = 'US');
• Security-scoped lookups joining FND_SECURITY_GROUPS on SECURITY_GROUP_ID for multi-org reporting.

Related Objects

• JTF_DSP_CONTEXT_B — Base table; joined on CONTEXT_ID. The TL row supplies the translatable NAME and DESCRIPTION.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID for data-security partitioning.
• JTF_DSP_CONTEXT_TL_PK — The composite primary key constraint (CONTEXT_ID, LANGUAGE).
• FND_LANGUAGES — The framework table that validates the LANGUAGE and SOURCE_LANG values.
• FND_APPLICATION / JTF display framework APIs — Consume translated context definitions when rendering CRM contexts.