Search Results cs_kb_histories_tl




Overview
Explore in AI Chat

Overview

The CS_KB_HISTORIES_TL table is a translation table within the Oracle E-Business Suite Service (CS) module. Its primary role is to store multilingual content for knowledge base history records, enabling the support of multiple languages in a global deployment. This table operates in conjunction with its base table, CS_KB_HISTORIES_B, which holds the language-independent data. The TL (Translation) table structure is a standard Oracle EBS design pattern for implementing multilingual capabilities, allowing the same core entity—in this case, a knowledge base history entry—to have descriptive text in numerous languages as defined in the FND_LANGUAGES table.

Key Information Stored

The table stores translated text for knowledge base history attributes. Based on its structure as a translation table and standard EBS conventions, its critical columns include HISTORY_ID, which is the foreign key linking to the base table's primary key, and LANGUAGE, which identifies the language code (e.g., 'US', 'DE'). Another essential column is SOURCE_LANG, which denotes the original language in which the data was entered. The table likely contains one or more descriptive columns, such as HISTORY_TEXT or DESCRIPTION, which hold the actual translated content. The primary key constraint, CS_KB_HISTORIES_TL_PK, is defined on the combination of HISTORY_ID and LANGUAGE, ensuring a unique translation per language for each history record.

Common Use Cases and Queries

This table is primarily accessed by the application's user interface to display knowledge base history information in a user's session language. Common operational and reporting scenarios include retrieving all translations for a specific knowledge base history entry or generating audit reports of changes made to knowledge articles in a specific language. A typical query would join this table to its base table and the FND_LANGUAGES table to present a complete, language-specific view. For example, to fetch the English description for a set of histories, one might use: SELECT b.history_id, tl.history_text FROM cs_kb_histories_b b, cs_kb_histories_tl tl WHERE b.history_id = tl.history_id AND tl.language = 'US' AND tl.source_lang = 'US'; Data maintenance is typically performed via the application's translation forms or dedicated APIs, not via direct SQL updates.

Related Objects

The table maintains documented foreign key relationships with several core objects, defining its integration within the EBS data model:

  • CS_KB_HISTORIES_B: The primary base table. The foreign key from CS_KB_HISTORIES_TL.HISTORY_ID references CS_KB_HISTORIES_B, linking each translation row to its core entity.
  • FND_LANGUAGES: The table is linked to FND_LANGUAGES twice. The foreign key on CS_KB_HISTORIES_TL.LANGUAGE validates the language code of the translation. A separate foreign key on CS_KB_HISTORIES_TL.SOURCE_LANG validates the original source language code.
This structure ensures data integrity, guaranteeing that all translation records reference valid base records and are associated with application-supported languages.