Results for “csd_repair_types_tl”

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

Overview

CSD_REPAIR_TYPES_TL is the translation (language-specific) table for the Depot Repair repair type base table, CSD_REPAIR_TYPES_B. It resides in the CSD schema, which owns the Oracle Depot Repair (CSD) product within Oracle E-Business Suite. The table stores the user-facing, translatable attributes of each repair type — primarily the display name and description — one row per language installed in the EBS instance, in accordance with the standard Oracle Applications multilingual architecture.

Under this architecture, transactional and descriptive base columns that are language-independent (for example, primary key and audit attributes) are held in CSD_REPAIR_TYPES_B, while text that must be presented in the session language is held in CSD_REPAIR_TYPES_TL. Oracle Forms and OAF pages join the two tables at runtime using the session language (typically FND_LANGUAGES-based) to resolve the translated values.

From a Data Vault modeling perspective, and based on the mined foreign key and key structure, this object is best classified heuristically as a link — it relates a business entity (repair type, via REPAIR_TYPE_ID) to a language (via LANGUAGE), rather than storing an independent hub entity. The combination of these two columns forms the primary key, which is characteristic of a link construct between a hub and a reference/dimension.

Key Information Stored

The table contains 12 documented columns. The most important for practical purposes are:

• REPAIR_TYPE_ID — the surrogate key identifying the repair type. This is part of the composite primary key and is the foreign key to CSD_REPAIR_TYPES_B.
• LANGUAGE — the NLS language code (foreign key to FND_LANGUAGES) in which the NAME and DESCRIPTION are stored. Also part of the primary key.
• NAME — the translated display name of the repair type shown to users in the given language.
• DESCRIPTION — the translated, longer description of the repair type.
• SOURCE_LANG — indicates the source language from which the row was created (standard EBS translation-tracking column).
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle Applications audit columns tracking who created and last updated the row, and when.
• SECURITY_GROUP_ID — the security group identifier (foreign key to FND_SECURITY_GROUPS), used in multi-organization / data-security contexts.
• ZD_EDITION_NAME — a versioning column appearing in the unique index and often used in Edition-Based Redefinition (EBR) implementations in Release 12.2.x.

The surrogate primary key is CSD_REPAIR_TYPES_TL_PK on (REPAIR_TYPE_ID, LANGUAGE). The documented unique index CSD_REPAIR_TYPES_TL_U1 on (REPAIR_TYPE_ID, LANGUAGE, ZD_EDITION_NAME) represents the business-key candidate under EBR-enabled configurations. The distinction matters: the PK enforces uniqueness of a repair type per language, while the unique index additionally accounts for the edition dimension when EBR is active.

Common Use Cases and Queries

Typical uses of this table involve reporting, list-of-values lookups, and integration scenarios where translated repair type names must be exposed in the operator's session language. A conventional join pattern resolves the translated name as follows:

SELECT b.repair_type_id, tl.name, tl.description
FROM csd_repair_types_b b, csd_repair_types_tl tl
WHERE b.repair_type_id = tl.repair_type_id
AND tl.language = USERENV('LANG');

Because the CSD product relies on the standard language resolution mechanism, applications frequently substitute the session language value for USERENV('LANG'), or use FND_LANGUAGE for more precise control. Reporting extracts often filter LANGUAGE to a specific installed language so that a single translated row per repair type appears, avoiding duplicate rows that arise when multiple languages exist. Data migration and interface loads must insert rows for each language required by the business, populating NAME, DESCRIPTION, and SOURCE_LANG consistently with CSD_REPAIR_TYPES_B creation. Reconciliation queries compare CSD_REPAIR_TYPES_B against this translation table to detect missing translations — a common data integrity check.

Related Objects

The following objects have the most significant relationships to this table, based on the documented foreign keys and EBS architectural conventions:

• CSD_REPAIR_TYPES_B — the base (non-translated) table; joined on REPAIR_TYPE_ID. This is the parent of the translation table.
• FND_LANGUAGES — the reference table defining valid language codes; joined on LANGUAGE.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; constrains access based on security group configuration.
• CSD_REPAIR_TYPES_VL — the standard EBS view that combines the base and translation tables for language-specific presentation (a conventional companion object).
• FND_USER — indirectly related through the audit columns (CREATED_BY, LAST_UPDATED_BY) for user attribution in reporting.
• CSD_REPAIR_ORDERS / Depot Repair entry screens — consume repair type values through the base and translation tables as list-of-values sources.

These relationships follow the standard EBS translation model, where the "_B" and "_TL" suffix convention indicates base and translatable segments of a single logical entity.