Search Results cs_kb_used_sum_defs_tl




Overview
Explore in AI Chat

Overview

The CS_KB_USED_SUM_DEFS_TL table is a core translation (TL) table within the Oracle E-Business Suite Service (CS) module. It functions as the multilingual repository for user-defined summary definitions utilized by the knowledge base (KB) functionality. Its primary role is to store translated text for summary labels or descriptions, enabling the support of multiple languages within the EBS application. This table works in conjunction with its base table, CS_KB_USED_SUM_DEFS_B, which holds the language-independent structural data. The existence of this translation table is a standard Oracle EBS architecture pattern, ensuring that summary definitions presented in the user interface are dynamically served in the user's session language, a critical feature for global deployments of versions 12.1.1 and 12.2.2.

Key Information Stored

The table stores translated attributes for knowledge base summary definitions. The primary key is a composite of DEF_ID and LANGUAGE, which uniquely identifies a single translation for a specific definition. The DEF_ID column is a foreign key linking the record to its corresponding entity in the base table. The LANGUAGE column holds the language code (e.g., 'US', 'FR') and is a foreign key to FND_LANGUAGES. The SOURCE_LANG column, also a foreign key to FND_LANGUAGES, indicates the original language in which the data was entered, serving as the source for any subsequent translations. The most critical translated data column, typically named DESCRIPTION or a similar attribute (implied by the table's purpose though not explicitly listed in the brief metadata), would hold the actual translated text for the summary definition as seen by end-users.

Common Use Cases and Queries

This table is primarily accessed by the application's internal localization engine to render translated content. From a reporting or data extraction standpoint, common use cases involve generating multilingual lists of KB summary definitions or auditing translation completeness. A typical query joins the translation table with its base table and the languages table to retrieve human-readable information.

  • Sample Query for Translated Definitions:
    SELECT b.DEF_ID, tl.LANGUAGE, tl.DESCRIPTION, l.NLS_LANGUAGE
    FROM CS_KB_USED_SUM_DEFS_B b,
         CS_KB_USED_SUM_DEFS_TL tl,
         FND_LANGUAGES l
    WHERE b.DEF_ID = tl.DEF_ID
    AND tl.LANGUAGE = l.LANGUAGE_CODE
    AND tl.LANGUAGE = USERENV('LANG'); -- For session language
  • Auditing Translation Coverage: Queries can identify definitions missing translations for specific installed languages by comparing records against the FND_LANGUAGES table where the INSTALLED_FLAG is 'Y'.

Related Objects

The table maintains defined foreign key relationships with several core objects, as documented in the ETRM metadata.

  • CS_KB_USED_SUM_DEFS_B: This is the primary related base table. The TL table is a child of the B table via the DEF_ID column (CS_KB_USED_SUM_DEFS_TL.DEF_ID references CS_KB_USED_SUM_DEFS_B). All summary definition entities must exist in the base table before translations can be created.
  • FND_LANGUAGES: The table has two distinct foreign key relationships to the FND_LANGUAGES table. The LANGUAGE column references FND_LANGUAGES to validate the translation language code. The SOURCE_LANG column also references FND_LANGUAGES to identify the source language of the original data.