Search Results csd_service_codes_tl




Overview
Explore in AI Chat

Overview

CSD_SERVICE_CODES_TL is the translation (language) table for the Depot Repair service code base table CSD_SERVICE_CODES_B. It resides in the CSD schema and is shipped as part of the CSD - Depot Repair product family in Oracle E-Business Suite 12.1.1 and 12.2.2. In the standard EBS MLS (Multi-Language Support) pattern, the _B table holds the language-independent attributes of a service code, while the _TL table stores the translatable descriptive attributes — the service code NAME and DESCRIPTION — for each installed language. Every service code defined in the base table therefore has one _TL row per active language, and the EBS form and report layers resolve the correct row using the session's LANGUAGE value.

The heuristic Data Vault classification mined from the documented foreign-key structure is standalone; that is, the table carries no outbound FK to another hub or link within the documented schema. In Data Vault modeling terms it is best treated as a satellite attached to the service code hub (represented by CSD_SERVICE_CODES_B via SERVICE_CODE_ID), with LANGUAGE acting as the additional descriptive context that qualifies the translated attribute set.

Key Information Stored

The table is documented with 10 columns. The most significant are:

  • SERVICE_CODE_ID — surrogate identifier of the parent service code, inherited from CSD_SERVICE_CODES_B. It forms the first component of the primary key.
  • LANGUAGE — the NLS language code for the translated row; the second component of the primary key.
  • NAME — the language-specific display name of the service code.
  • DESCRIPTION — the language-specific description of the service code's purpose or scope.
  • SOURCE_LANG — the language in which the row was originally authored, used by the MLS translation maintenance tools.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS WHO (Who-Did-It) audit columns tracking insert and update responsibility, user, and timestamp.

The primary key is CSD_SERVICE_CODES_TL_PK1 over (SERVICE_CODE_ID, LANGUAGE). The documented unique index CSD_SERVICE_CODES_TL_U1 also spans (SERVICE_CODE_ID, LANGUAGE), confirming the business key that guarantees exactly one translation row per service code per language.

Common Use Cases and Queries

Typical reporting and inquiry patterns join the translation table to the base table and filter on the session language, or use the EBS FND_LANGUAGES/LANGUAGE constructs to resolve the correct descriptive text. A representative query:

  • SELECT b.service_code_id, t.name, t.description FROM csd_service_codes_b b, csd_service_codes_tl t WHERE b.service_code_id = t.service_code_id AND t.language = USERENV('LANG');
  • Translation maintenance: list all languages that have a row for a given service code with SELECT language FROM csd_service_codes_tl WHERE service_code_id = :id;
  • Missing-translation audit: compare base rows to _TL rows to identify service codes lacking a translation in a required language.
  • Depot Repair inquiry and reporting extracts use this table to render service code names in the operator's language, particularly in repair order and service code list-of-values reporting.

Related Objects

  • CSD_SERVICE_CODES_B — the base table; join on SERVICE_CODE_ID. This is the primary dependent relationship.
  • CSD_SERVICE_CODES_VL — the MLS view that unions base and translation columns for form and query use.
  • FND_LANGUAGES — reference table validating the LANGUAGE value.
  • Depot Repair service code LOVs and forms — consume this table to display translated service code names.
  • Related Depot Repair service/skill entities that reference service codes in their own configuration tables, resolved through the base code identifier.