Search Results cs_incidents_all_tl

Overview

The CS_INCIDENTS_ALL_TL table is a core data object within the Oracle E-Business Suite (EBS) Service (CS) module, specifically for versions 12.1.1 and 12.2.2. It functions as a translation table, storing multilingual text for service request records. Its primary role is to support global deployments by enabling the storage of user-entered, language-specific information for service incidents, such as summaries and problem descriptions. This table works in conjunction with its base table, CS_INCIDENTS_ALL_B, which holds the non-translatable, transactional data. The existence of this TL (Translation) table is a standard Oracle EBS architectural pattern for achieving localization, ensuring that service representatives and customers can view and interact with incident details in their preferred language.

Key Information Stored

The table stores the language-specific textual attributes for a service incident. Its structure is defined by a composite primary key consisting of INCIDENT_ID and LANGUAGE. The INCIDENT_ID column is a foreign key that links each translated row to a unique record in the CS_INCIDENTS_ALL_B base table. The LANGUAGE column holds the language code (e.g., 'US' for American English) for the translation. The most critical data columns typically include SUMMARY and PROBLEM_DESCRIPTION, which contain the translated text for the incident's title and detailed issue narrative. Other common translatable attributes may include resolution notes or internal comments. The table employs Oracle's Multi-Lingual Table (MLS) architecture, where each translated version of an incident's text occupies a separate row.

Common Use Cases and Queries

The primary use case is retrieving service request information in a user's session language for display in forms, reports, and service portals. A standard query involves joining this table with the base incident table and filtering by the user's language preference. For example, to fetch the translated summary and description for a specific incident, a common SQL pattern is:

• SELECT tl.summary, tl.problem_description
• FROM cs_incidents_all_b b, cs_incidents_all_tl tl
• WHERE b.incident_id = tl.incident_id
• AND tl.language = USERENV('LANG')
• AND b.incident_number = 'SR-12345';

Reporting use cases include generating service request history or customer communication logs in multiple languages. Data migration and integration scenarios also frequently interact with this table to populate or extract localized content.

Related Objects

CS_INCIDENTS_ALL_TL has a direct and essential relationship with several key Service module objects. Its primary foreign key relationship is with the base table CS_INCIDENTS_ALL_B via the INCIDENT_ID column. This is the most critical join for any transactional query. The table is also the source for corresponding translatable views, such as CS_INCIDENTS_ALL_VL. For data manipulation, standard Oracle APIs like the CS_ServiceRequest_PUB package are the recommended interface, which handle the complexity of maintaining both the base and translation tables. Other related tables may include CS_INCIDENT_INTERACTIONS for logged communications and CS_INCIDENT_SEVERITIES for priority data, though these typically join through the INCIDENT_ID in the base table.