Results for “cs_sr_status_groups_tl”

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

Overview

CS_SR_STATUS_GROUPS_TL is the translation (language) table for service request status groups in the Oracle Service (CS) module. It stores the language-dependent descriptive attributes of status groups, which are rules used to govern how service requests transition between statuses within Oracle EBS Service. While the base table CS_SR_STATUS_GROUPS_B holds language-independent columns and the defining logic for a status group, this _TL companion table holds only the human-readable, translatable text associated with each group.

From a dimensional and Data Vault modeling perspective, the metadata's FK structure classifies this object as satellite-leaning. In practice this means it should be treated as a dependent descriptive satellite attached to the base entity CS_SR_STATUS_GROUPS_B. It does not represent an independent business entity (hub) nor a relationship between entities (link); it extends the base status group record with language-specific descriptive data keyed by language.

The table is owned by the CS schema and is marked VALID in the documented ETRM 12.2.2 metadata. It is present in both Oracle EBS 12.1.1 and 12.2.2, as Service status group functionality spans both releases.

Key Information Stored

The table contains ten documented columns. The most important are:

• STATUS_GROUP_ID — Surrogate identifier linking each translation row back to its parent record in CS_SR_STATUS_GROUPS_B. It is part of the composite primary key (CS_SR_STATUS_GROUPS_TL_PK) together with LANGUAGE.
• LANGUAGE — The NLS language code identifying the language of the translated text. Together with STATUS_GROUP_ID it forms the primary key, ensuring one translation row per group per language.
• GROUP_NAME — The translated display name of the status group. This is the primary business-facing label used in Service request configuration and user interfaces.
• DESCRIPTION — The translated long description explaining the purpose or scope of the status group.
• SOURCE_LANG — The language in which the source record was originally created; used by the translation/MLS framework to track origin language.
• 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 and the session that performed it.

The primary key is the surrogate composite CS_SR_STATUS_GROUPS_TL_PK (LANGUAGE, STATUS_GROUP_ID). The unique index CS_SR_STATUS_GROUPS_TL_U1 (STATUS_GROUP_ID, LANGUAGE) is the documented business-key candidate, enforcing uniqueness of each group/language combination. Note that the two keys differ only in column order.

Common Use Cases and Queries

This table is queried primarily for multilingual reporting, configuration validation, and translation maintenance. Typical scenarios include listing all status groups in a specific language, identifying groups missing translations, and joining to the base table for complete rule attributes.

• Retrieve translated group names for a language:

  SELECT t.status_group_id, t.group_name, t.description
  FROM   cs.cs_sr_status_groups_tl t
  WHERE  t.language = USERENV('LANG');

• Find groups lacking a translation:

  SELECT b.status_group_id
  FROM   cs.cs_sr_status_groups_b b
  WHERE  NOT EXISTS
         (SELECT 1 FROM cs.cs_sr_status_groups_tl t
          WHERE t.status_group_id = b.status_group_id
          AND   t.language = 'US');

• Join base and translation for full detail:

  SELECT b.status_group_id, t.group_name, t.description
  FROM   cs.cs_sr_status_groups_b b,
         cs.cs_sr_status_groups_tl t
  WHERE  b.status_group_id = t.status_group_id
  AND    t.language = 'US';

Reporting uses include Service configuration audits, user-facing picklist population, and localization verification during multi-language deployments.

Related Objects

The most significant related object is the base table, referenced via a foreign key from STATUS_GROUP_ID. Relevant related objects include:

• CS_SR_STATUS_GROUPS_B — Parent base table; CS_SR_STATUS_GROUPS_TL.STATUS_GROUP_ID → CS_SR_STATUS_GROUPS_B.STATUS_GROUP_ID. Holds the language-independent definition.
• CS_SR_STATUSES / status configuration tables — Status groups organize related statuses used in the service request lifecycle.
• CS_SR_STATUS_GROUPS_TL_PK and CS_SR_STATUS_GROUPS_TL_U1 — Primary key and unique indexes enforcing translation integrity.
• MLS translation framework objects (e.g., FND_LANGUAGES) — Supply the LANGUAGE and SOURCE_LANG values and support the multi-lingual schema pattern.
• Service Request workflow/status APIs — Consume status group definitions to drive permitted service request transitions and validations.