Results for “cs_sr_event_codes_tl”

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

Overview

CS_SR_EVENT_CODES_TL is the translation table for all service request event definitions within the Oracle E-Business Suite Service (CS) module. It stores the language-specific, user-facing text associated with each service request event code, allowing event definitions to be presented in multiple installed languages. In Oracle EBS 12.1.1 and 12.2.2, the table resides in the CS schema and is classified as VALID in the ETRM repository.

Because a single event definition can be translated into many languages, this object operates logically as a child of the base event definitions table, most likely CS_SR_EVENT_CODES_B. From a Data Vault modeling perspective, the metadata's heuristic classification is standalone, meaning no foreign key relationships were mined from the schema. That classification is a suggestion rather than a strict rule; functionally, the table behaves as a satellite-like structure, carrying descriptive attributes (NAME, DESCRIPTION) keyed by a business code (EVENT_CODE) plus a LANGUAGE discriminator, which parallels the hub-plus-satellite idiom common in Data Vault designs.

Key Information Stored

The documented physical schema contains 11 columns. The most important are:

• EVENT_CODE — The business identifier of the service request event. It is part of the primary key and the unique index, serving as the link back to the untranslated event definition.
• LANGUAGE — The language code of the translation. Combined with EVENT_CODE, it forms the primary key CS_SR_EVENT_CODES_TL_PK, so each event is stored once per language.
• ZD_EDITION_NAME — The edition indicator supporting Edition-Based Redefinition (EBR), which is significant in Oracle EBS 12.2.2. It is the third column in the unique business-key candidate CS_SR_EVENT_CODES_TL_U1 (EVENT_CODE, LANGUAGE, ZD_EDITION_NAME).
• NAME — The translated display name of the event shown to users in the service request workflow.
• DESCRIPTION — The translated descriptive text for the event, used on forms, reports, and notifications.
• SOURCE_LANG — The source language from which the translation was derived, typically the base language of the installation.
• CREATION_DATE, CREATED_BY — Standard audit columns recording when and by whom the translation row was inserted.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification.

The primary key is a composite surrogate over EVENT_CODE and LANGUAGE. The unique index CS_SR_EVENT_CODES_TL_U1 additionally includes ZD_EDITION_NAME, which reflects the EBR-aware uniqueness enforced in 12.2.

Common Use Cases and Queries

Typical scenarios include building multilingual reference lists of service request events, troubleshooting missing or incorrect event labels, and validating that every event code has a translation for each active language. A common query joins translations to the base event table by EVENT_CODE and filters by language:

• Retrieve translated labels: SELECT EVENT_CODE, NAME, DESCRIPTION FROM CS_SR_EVENT_CODES_TL WHERE LANGUAGE = 'US';
• Detect missing translations by comparing base events to this table for a target language.
• Audit recent changes using LAST_UPDATE_DATE, CREATED_BY, and LAST_UPDATED_BY.
• Reporting on event definitions across languages for user documentation or UI review.

Related Objects

The most significant related objects are the base, untranslated event definition table and the standard language and audit reference structures accessed through the columns above:

• CS_SR_EVENT_CODES_B — Base table holding event definitions; join on EVENT_CODE.
• CS_SR_EVENT_CODES_VL — The language view that unions base and translated rows.
• FND_LANGUAGES — Reference table for LANGUAGE values.
• CS_SR_EVENT_CODES_TL_PK and CS_SR_EVENT_CODES_TL_U1 — Primary key and unique indexes enforcing integrity.
• FND_USER — Resolves CREATED_BY and LAST_UPDATED_BY to user names for auditing.

Because the metadata classified this object as standalone, no enforced foreign keys were mined; relationships to the base table are logical and should be verified against the actual data model before relying on them in joins.