Search Results cs_kb_attrs_tl




Overview
Explore in AI Chat

Overview

The CS_KB_ATTRS_TL table is a translation table within the Oracle E-Business Suite (EBS) Service (CS) module. Its core function is to store multilingual translations for descriptive attributes of knowledge base entities, enabling the support of a global user base. As a translation (TL) table, it works in conjunction with a corresponding base table, CS_KB_ATTRS_B, which holds the language-independent data. A critical piece of information from the official ETRM documentation is that this table is marked as "Not used since before 11.5.8." This status indicates that while the table structure exists in schemas for releases 12.1.1 and 12.2.2, its functional purpose was deprecated in a much earlier version of the application. Consequently, it is highly likely to contain no active transactional data in modern EBS implementations, serving primarily as a legacy artifact for potential upgrade compatibility.

Key Information Stored

The table's structure is designed to manage translated text. The primary key is a composite of ATTRIBUTE_ID and LANGUAGE, ensuring a unique entry for each attribute in each language. The ATTRIBUTE_ID column is a foreign key that links the translation record to its corresponding master record in the CS_KB_ATTRS_B table. The LANGUAGE column stores the language code (e.g., 'US', 'DE') and is a foreign key to the FND_LANGUAGES table, which validates and describes installed languages. Another significant column is SOURCE_LANG, which records the original language code in which the data was entered; this is also a foreign key to FND_LANGUAGES and is used by the Oracle translation architecture to identify seed data. The table would typically contain descriptive columns like ATTRIBUTE_NAME or DESCRIPTION to hold the translated text itself, though the specific column list is not detailed in the provided metadata.

Common Use Cases and Queries

Given its deprecated status, there are no active business or reporting use cases for this table in standard EBS operations post-11.5.8. Technical activities are limited to data cleanup, schema analysis, or historical audits. A database administrator might query to confirm the absence of data. A sample query to check for any existing records would be:

  • SELECT COUNT(*) FROM apps.CS_KB_ATTRS_TL;

For schema analysis, a developer might examine its structure and relationships:

  • SELECT column_name, data_type FROM all_tab_columns WHERE table_name = 'CS_KB_ATTRS_TL' ORDER BY column_id;

Any custom code or reports referencing this table in a 12.x environment should be reviewed, as they are likely obsolete and may be based on outdated application logic.

Related Objects

The CS_KB_ATTRS_TL table has defined relationships with several core EBS objects, as per the foreign key constraints documented. Its primary relationship is with the base table CS_KB_ATTRS_B, from which it derives the ATTRIBUTE_ID. This establishes the standard base/translation table pattern. Furthermore, it has two foreign key dependencies on the application foundation table FND_LANGUAGES: one for the LANGUAGE column and another for the SOURCE_LANG column. This ensures all language codes referenced are valid within the EBS instance. As a component of the Knowledge Base (KB) sub-module within Service, it may historically relate to other CS_KB% objects, but its deprecated nature means it is not referenced by active application APIs or public interfaces in contemporary releases.