Results for “cug_sr_task_attr_vals_tl”

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

Overview

CUG_SR_TASK_ATTR_VALS_TL is the translation table for the CUG_SR_TASK_ATTR_VALS_B base table within the CUG – Citizen Interaction Center product module of Oracle E-Business Suite. In Oracle EBS, translation (_TL) tables store language-specific, user-facing text for a corresponding base (_B) table. The base table holds language-independent attributes and keys, while the _TL table carries the translatable descriptive content keyed by the same primary identifier plus a LANGUAGE code. This design is the standard Multilingual Application Toolkit (MLS/MLS-lite) pattern used throughout EBS 12.1.1 and 12.2.2, allowing the same functional record to present different attribute text to users operating in different language settings.

The object is documented with ten physical columns in the CUG schema and is marked VALID. Following the heuristic Data Vault classification mined from its foreign key structure, this table is satellite-leaning: it hangs off the CUG_SR_TASK_ATTR_VALS_B parent and carries descriptive, possibly time-variant attributes rather than defining new hubs or links. This classification is a modeling suggestion only; in EBS terms the table functions as the translation satellite for service-request task attribute values.

Key Information Stored

Its purpose is to hold the language-dependent text describing a service request task attribute value. The primary key, CUG_SR_TASK_ATTR_VALS_TL_PK, is composite over SR_TASK_ATTR_VAL_ID and LANGUAGE, meaning a single attribute value exists once per language.

• SR_TASK_ATTR_VAL_ID – Surrogate foreign key to CUG_SR_TASK_ATTR_VALS_B; the language-independent identity of the attribute value.
• LANGUAGE – Two-character language code, the second half of the primary key, defining which locale's text is stored.
• TASK_TYPE_ATTR_VALUE – The actual translatable business text: the attribute value as presented to the user for the given language.
• SOURCE_LANG – The language in which the row was originally authored, used during translation and MLS refresh processing.
• SECURITY_GROUP_ID – Foreign key to FND_SECURITY_GROUPS, supporting multi-tenant, security-group-constrained access to records.
• CREATED_BY, CREATION_DATE – Standard audit columns recording row creation.
• LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE – Standard audit columns tracking the most recent modification.

The surrogate primary key is thus the composite (SR_TASK_ATTR_VAL_ID, LANGUAGE). The business-key candidate for a specific language is SR_TASK_ATTR_VAL_ID combined with LANGUAGE.

Common Use Cases and Queries

Typical use cases include retrieving localized labels and values for service-request task attributes, generating multilingual reports, and auditing translation coverage. Because only one language row is normally returned per identifier, queries filter on LANGUAGE or use the EBS LANGUAGE environment. A representative pattern:

• SELECT tl.task_type_attr_value FROM cug_sr_task_attr_vals_tl tl WHERE tl.sr_task_attr_val_id = :id AND tl.language = USERENV('LANG');
• Joining translations to the base table for bilingual listings: SELECT b.sr_task_attr_val_id, tl.language, tl.task_type_attr_value FROM cug_sr_task_attr_vals_b b, cug_sr_task_attr_vals_tl tl WHERE b.sr_task_attr_val_id = tl.sr_task_attr_val_id.
• Detecting attributes lacking a translation in a target language by comparing base rows against _TL rows restricted to that LANGUAGE.
• Security-group-scoped extracts filtering on SECURITY_GROUP_ID for tenant-isolated reporting.

Related Objects

The table participates in a small, well-defined relationship set:

• CUG_SR_TASK_ATTR_VALS_B – The base table; joined on SR_TASK_ATTR_VAL_ID. This is the parent carrying language-independent data.
• FND_SECURITY_GROUPS – Referenced by SECURITY_GROUP_ID, constraining record visibility.
• FND_LANGUAGES – Provides the valid values for the LANGUAGE column in the EBS multilingual framework.
• FND_APPLICATION / CUG product metadata – Defines the owning application context.

Any inbound view or API built over CUG_SR_TASK_ATTR_VALS_B that exposes localized values will depend on this table as its translation source.