Results for “cug_tsk_typ_attr_deps_tl”

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

Overview

CUG_TSK_TYP_ATTR_DEPS_TL is the translation table associated with CUG_TSK_TYP_ATTR_DEPS_B, the base table that defines task type attribute dependencies within the Citizen Interaction Center (CUG) module of Oracle E-Business Suite. In the standard EBS multilanguage architecture, an object of this kind holds the language-specific, translatable text columns for its base counterpart, allowing a single business definition to be rendered in multiple installed languages. The _TL suffix and the presence of LANGUAGE as part of the primary key identify it unambiguously as a translation entity rather than a transactional or setup entity.

From a dimensional modeling perspective, the metadata suggests a satellite-leaning classification. The table carries descriptive, language-dependent attributes keyed to the base record in CUG_TSK_TYP_ATTR_DEPS_B, which is consistent with the satellite role in a Data Vault model — a dependent, historically descriptive structure that extends a hub-like base entity rather than defining new business relationships. This is a heuristic observation derived from the foreign key topology, not a prescribed implementation pattern.

Key Information Stored

The table contains ten documented columns. The most significant are described below.

• TSK_TYP_ATTR_DEP_ID — The surrogate identifier of the parent dependency record. Together with LANGUAGE it forms the composite primary key CUG_TSK_TYP_ATTR_DEP_ID + LANGUAGE.
• LANGUAGE — The NLS language code identifying the locale in which the translated text is stored. It is the second component of the primary key.
• SR_ATTRIBUTE_VALUE — The translated, displayable value associated with the attribute dependency. This is the principal business payload of the translation row and the column most commonly read by application and reporting queries.
• SOURCE_LANG — The language of the source or base record from which the translation was derived, used by the translation framework to track origin language.
• SECURITY_GROUP_ID — A foreign key to FND_SECURITY_GROUPS, enforcing the multi-tenant data isolation model used throughout EBS.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard EBS who-column audit trail, recording row creation and modification identity and timestamps.

The surrogate composite key is TSK_TYP_ATTR_DEP_ID + LANGUAGE. The documented metadata does not expose an alternate unique index, so no separate business-key candidate is asserted here; the parent identifier from CUG_TSK_TYP_ATTR_DEPS_B serves as the effective business reference.

Common Use Cases and Queries

The typical access pattern is an outer join from the base table to its translation, filtered by the session language, so that every dependency record is returned with its localized attribute value.

• Retrieving translated attribute dependency values for a specific base record or set of records in the current user language.
• Auditing translation coverage to identify base rows that lack a translation for one or more installed languages.
• Reporting and extract routines that require the display value (SR_ATTRIBUTE_VALUE) rather than the internal identifier.

A representative query pattern is:

SELECT b.tsk_typ_attr_dep_id, t.sr_attribute_value FROM cug_tsk_typ_attr_deps_b b, cug_tsk_typ_attr_deps_tl t WHERE b.tsk_typ_attr_dep_id = t.tsk_typ_attr_dep_id AND t.language = USERENV('LANG') AND t.security_group_id = :security_group_id;

Translation-gap detection typically reverses the join, selecting base rows for which no matching translation row exists for a given LANGUAGE code.

Related Objects

• CUG_TSK_TYP_ATTR_DEPS_B — The base table for this translation; joined on TSK_TYP_ATTR_DEP_ID. This is the primary parent and the mandatory join target.
• FND_SECURITY_GROUPS — Referenced through SECURITY_GROUP_ID; governs data visibility across security groups.
• FND_LANGUAGES — Provides the valid installed language codes that populate the LANGUAGE column.
• FND_APPLICATION / FND_PRODUCT_INSTALLATIONS — Define the CUG application context under which the table is owned and patched.
• CUG_TSK_TYP_ATTR_DEPS_TL_PK — The primary key constraint, defining uniqueness on TSK_TYP_ATTR_DEP_ID and LANGUAGE and enforcing one translation per language per dependency.

Because CUG is a localized module, any query against the dependency structure should resolve text through this translation table rather than reading base-table columns directly.