Search Results cs_incident_types_tl

Overview

The CS_INCIDENT_TYPES_TL table is a core translation table within the Oracle E-Business Suite (EBS) Service (CS) module. It stores language-specific, translatable descriptions for Service Request type codes. In Oracle EBS, a Service Request (or incident) is a central record for tracking customer-reported issues, and its type categorizes the nature of the request (e.g., "Problem," "Question," "Complaint"). While the base code and non-translatable attributes are stored in a parent table, CS_INCIDENT_TYPES_TL holds the translated names and descriptions, enabling the application to display type information in the language of the user's session. This table is essential for supporting multilingual deployments of Oracle EBS, ensuring consistent service terminology across global operations.

Key Information Stored

The table's primary purpose is to manage translated text for Service Request types. Its structure is defined by a composite primary key consisting of INCIDENT_TYPE_ID and LANGUAGE. The INCIDENT_TYPE_ID is a foreign key that links to the base type definition. The LANGUAGE column holds the ISO language code (e.g., 'US' for American English, 'KO' for Korean). The most critical data columns are NAME and DESCRIPTION, which contain the translated, user-visible label and explanatory text for the incident type in the specified language. Additional standard columns like CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN track row history, while SOURCE_LANG indicates the original language of the translation seed data.

Common Use Cases and Queries

This table is primarily accessed by the application runtime to display localized lists of Service Request types in forms and LOVs. For reporting and data extraction, common queries involve joining it with its base table to produce user-friendly, language-specific output. A typical pattern is to filter by the user's session language using a join condition on LANGUAGE = USERENV('LANG'). For example, to generate a list of all active incident types with their English descriptions, one might use a query such as: SELECT b.INCIDENT_TYPE_ID, t.NAME, t.DESCRIPTION FROM CS_INCIDENT_TYPES_B b, CS_INCIDENT_TYPES_TL t WHERE b.INCIDENT_TYPE_ID = t.INCIDENT_TYPE_ID AND t.LANGUAGE = 'US' AND b.START_DATE_ACTIVE <= SYSDATE AND (b.END_DATE_ACTIVE IS NULL OR b.END_DATE_ACTIVE >= SYSDATE);. Administrators may also query this table to audit or manage translations for new languages.

Related Objects

CS_INCIDENT_TYPES_TL has a direct and mandatory relationship with its base table, which holds the non-translatable attributes. Based on the provided primary key metadata, the following key relationship is documented:

• Parent Table (Base Table): The table CS_INCIDENT_TYPES_B. The column INCIDENT_TYPE_ID in CS_INCIDENT_TYPES_TL is a foreign key referencing the primary key of CS_INCIDENT_TYPES_B. This relationship is fundamental, as every translation row must correspond to a valid base incident type definition.

In practice, Service Request transactional data in tables like CS_INCIDENT_SUMMARY_B or CS_INCIDENTS_ALL_B will store an INCIDENT_TYPE_ID, which can be traced back to its descriptive translations via CS_INCIDENT_TYPES_B and then CS_INCIDENT_TYPES_TL. The table is also a source for various service-related views that present localized data.