Search Results csd_service_codes_tl_u1

Overview

CSD.CSD_SERVICE_CODES_TL is the translation (TL) table for the service code base table CSD_SERVICE_CODES_B within the CSD schema of Oracle E-Business Suite 12.1.1 / 12.2.2. It belongs to the Enterprise Asset Management / Field Service (CSD = Service Depot) product family and stores the language-dependent attributes — primarily NAME and DESCRIPTION — for each service code defined in the base table. Each service code definition is therefore held once in CSD_SERVICE_CODES_B and reproduced once per installed or enabled language in this table.

In the standard EBS multilingual (MLS) pattern, the _TL synonym exposed in APPS (APPS.CSD_SERVICE_CODES_TL) is what application code and reports query; the underlying object remains CSD.CSD_SERVICE_CODES_TL. From a dimensional or Data Vault modeling perspective, the mined metadata classifies this object heuristically as a standalone structure, which suggests treating it as a satellite-like entity attached to the service code key rather than a hub or link in its own right. The classification is a modeling suggestion only and reflects the absence of a strong multi-parent FK profile in the documented schema.

Key Information Stored

The table is physically stored in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and the unique index CSD_SERVICE_CODES_TL_U1 is created in APPS_TS_TX_IDX. Its ten documented columns break down as follows:

• SERVICE_CODE_ID (NUMBER 15) — the identifier of the service code; it is the foreign key back to the base table and forms part of both the PK (CSD_SERVICE_CODES_TL_PK1) and the unique index CSD_SERVICE_CODES_TL_U1.
• LANGUAGE (VARCHAR2) — the language into which the text is translated. Together with SERVICE_CODE_ID this constitutes the composite primary key and the business-key candidate exposed by the U1 index.
• NAME (VARCHAR2 80) — the translated service code name presented to users in list of values and reports.
• DESCRIPTION (VARCHAR2 240) — the translated description of the service code.
• SOURCE_LANG (VARCHAR2) — the language from which the text was originally translated, enabling the MLS layer to identify the seed record.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO columns, with CREATED_BY and LAST_UPDATED_BY keyed to FND_USER.USER_ID and LAST_UPDATE_LOGIN keyed to FND_LOGINS.LOGIN_ID.

The surrogate key for the translation row is the composite (SERVICE_CODE_ID, LANGUAGE); the only documented unique index, CSD_SERVICE_CODES_TL_U1, covers exactly these two columns, making it the effective business-key candidate.

Common Use Cases and Queries

Typical uses include language-specific lookups in Service Depot transactions, building bilingual or multi-lingual reference reports, and diagnosing why a service code appears with a missing or unexpected name. A standard retrieval for one language follows:

• SELECT SERVICE_CODE_ID, NAME, DESCRIPTION FROM CSD.CSD_SERVICE_CODES_TL WHERE LANGUAGE = 'US' AND SERVICE_CODE_ID = :id;

To report service codes with their seed language, join back to the base table on SERVICE_CODE_ID and filter on SOURCE_LANG = LANGUAGE. Administrators verifying translation completeness can compare row counts per language across CSD_SERVICE_CODES_B and CSD_SERVICE_CODES_TL, or query the U1-keyed columns directly when troubleshooting duplicate-name errors raised during setup.

Related Objects

The most significant related objects are:

• CSD.CSD_SERVICE_CODES_B — the base table; join on SERVICE_CODE_ID.
• APPS.CSD_SERVICE_CODES_TL — the APPS synonym layer used by application logic; it references CSD.CSD_SERVICE_CODES_TL.
• CSD_SERVICE_CODES_TL_U1 — the unique index on (SERVICE_CODE_ID, LANGUAGE) and the object users typically inspect after a duplicate key or translation search.
• FND_USER — referenced via CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — referenced via LAST_UPDATE_LOGIN.