Results for “cs_incident_types_tl”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CS_INCIDENT_TYPES_TL is the translation table for Service Request (incident) type codes within the Oracle E-Business Suite Service (CS) module. In Oracle EBS, Service Request types classify incoming customer incidents—such as technical faults, billing inquiries, or field service requests—and drive routing, escalation, and reporting behavior. Because EBS is deployed in multilingual environments, the descriptive text of these type codes is stored separately from the base definition in a language-specific table. CS_INCIDENT_TYPES_TL holds the translated NAME and DESCRIPTION values for each incident type, keyed by language, while the untranslated definitional attributes reside in the base table CS_INCIDENT_TYPES_B. This separation follows the standard EBS MLS (Multi-Lingual Support) pattern, where a _B table stores language-independent rows and a _TL table stores one row per installed language.

The table resides in the CS schema and carries a VALID status in the ETRM 12.2.2 documentation. Under the heuristic Data Vault classification supplied in the metadata, this object is treated as standalone. From a pure modeling perspective, translation tables such as this are generally better understood as satellites, since they hold descriptive, time-variant attributes attached to a business key (the incident type plus language) rather than acting as hubs or links. The standalone classification reflects the mined foreign-key structure rather than a definitive Data Vault assignment, and should be regarded as a modeling suggestion only.

Key Information Stored

The table contains twelve documented columns. The most significant are:

• INCIDENT_TYPE_ID — Surrogate identifier of the incident type; part of the composite primary key.
• LANGUAGE — The installed language code for the translated row; the second component of the primary key.
• NAME — The translated display name of the Service Request type, shown to users in the current session language.
• DESCRIPTION — The translated long description of the type code.
• SOURCE_LANG — The language of the source (base) row from which the translation was derived.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, used for multi-tenant data segregation within a shared EBS instance.
• ZD_EDITION_NAME — Editioning column supporting Online Patching in EBS 12.2.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing who created and last modified each translation row and when.

The primary key is CS_INCIDENT_TYPES_TL_PK, defined on (INCIDENT_TYPE_ID, LANGUAGE). A second unique index, CS_INCIDENT_TYPE_TL_U1, spans (INCIDENT_TYPE_ID, LANGUAGE, ZD_EDITION_NAME) and serves as the business-key candidate that guarantees uniqueness of a translation per type, language, and edition.

Common Use Cases and Queries

The most common access pattern joins the translation table to the base table to retrieve a localized type name for a Service Request. A typical query is:

• 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 = USERENV('LANG');
• Reporting on incident volumes grouped by translated type name, using the LANGUAGE predicate to align with the reporting user's session language.
• Validating translation completeness by comparing row counts between CS_INCIDENT_TYPES_B and CS_INCIDENT_TYPES_TL per language, to detect untranslated type codes.
• Extracting the DESCRIPTION values to populate external knowledge bases or service catalogs.

Because the table is language-specific, queries that omit the LANGUAGE predicate return multiple rows per type and must be filtered accordingly.

Related Objects

• CS_INCIDENT_TYPES_B — The base table holding language-independent incident type definitions; joins on INCIDENT_TYPE_ID.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID for data segregation.
• CS_INCIDENTS_ALL / CS_INCIDENTS — Service Request transaction tables referencing incident type identifiers.
• FND_LANGUAGES — Provides valid values for the LANGUAGE column.
• FND_APPLICATION / FND_TERRITORIES — Supporting setup objects for the CS Service module configuration.