Results for “cs_kb_elements_tl”

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

Overview

CS_KB_ELEMENTS_TL is the translation (TL) table for knowledge base elements within the Oracle E-Business Suite Service (CS) module. Knowledge base elements represent the discrete, reusable content units that make up the Service knowledge base — the repository of solutions, symptoms, causes, resolutions, and related information presented to agents and, in some deployments, to self-service users. Because Oracle EBS is a multilingual application, every translatable attribute of a knowledge base element is stored twice: the base definition resides in CS_KB_ELEMENTS_B, and the language-specific text resides in CS_KB_ELEMENTS_TL. This TL table holds the translated NAME and DESCRIPTION values for each element, keyed by language, so that the same logical knowledge element can be surfaced in the user's session language.

In EBS 12.1.1 and 12.2.2 the table is owned by the CS schema and is marked VALID in the ETRM repository, with twelve documented columns. The heuristic Data Vault classification mined from its foreign-key structure is link. From a modeling perspective, this is appropriate: the table resolves the many-to-many relationship between knowledge base elements and languages, and is not an independent business entity (hub) nor a purely descriptive attribute table (satellite) in the classic sense, since it carries its own dependent attributes and composite key.

Key Information Stored

The composite primary key is CS_KB_ELEMENTS_TL_PK, consisting of ELEMENT_ID and LANGUAGE. A unique index, CS_KB_ELEMENTS_TL_U1, enforces the same (ELEMENT_ID, LANGUAGE) combination and serves as the business-key candidate, guaranteeing at most one translation row per element per language.

• ELEMENT_ID — surrogate foreign key to CS_KB_ELEMENTS_B; identifies the parent knowledge base element.
• LANGUAGE — the language of this translation row, validated against FND_LANGUAGES; part of the composite key.
• SOURCE_LANG — the source language from which the translation derives, also validated against FND_LANGUAGES; supports the translation workflow.
• NAME — the translated, language-specific short name of the knowledge element.
• DESCRIPTION — the translated descriptive text of the element; typically the largest text column.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns capturing who created and last modified the row and when.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant / operating-unit data segregation.
• COMPOSITE_TEXT_INDEX — a stored index column that supports text searching across the translatable content.

Common Use Cases and Queries

The primary use case is retrieving element content in the caller's language, with fallback to the base record or the source language when no translation exists. A typical query joins the TL table to the base table and filters by language:

• Localized content retrieval: SELECT b.element_id, t.name, t.description FROM cs_kb_elements_b b, cs_kb_elements_tl t WHERE b.element_id = t.element_id AND t.language = :session_lang;
• Translation gap analysis: compare row counts per LANGUAGE to find elements missing a translation for a target locale.
• Multilingual reporting: concatenate translations across languages for a chosen element to audit terminology consistency.
• Text search: query COMPOSITE_TEXT_INDEX to locate elements whose translated text matches agent search terms.

Related Objects

The table sits at the center of the knowledge base translation model and is joined to the following significant objects:

• CS_KB_ELEMENTS_B — the base (non-translated) table; join on ELEMENT_ID; provides the language-independent element definition.
• FND_LANGUAGES — provides validation for both LANGUAGE and SOURCE_LANG; join on the respective language codes.
• FND_SECURITY_GROUPS — validates SECURITY_GROUP_ID and governs data access by security group.
• CS_KB_CONTENT and related knowledge base content tables — associate elements with their published knowledge content.
• CS_KB_* dictionary and category tables — classify and organize elements for agent navigation and search.

Because the table is a TL companion, all application access is driven through the CS knowledge base forms and the Service knowledge management APIs, which supply the LANGUAGE bind variable from the user's session.