Search Results cug_tsk_typ_attr_maps_tl




Overview
Explore in AI Chat

Overview

The CUG_TSK_TYP_ATTR_MAPS_TL table is a core translation (TL) table within the Oracle E-Business Suite (EBS) Citizen Interaction Center (CUG) module. Its primary role is to store multilingual data for the base transactional table, CUG_TSK_TYP_ATTR_MAPS_B. This structure is a standard Oracle EBS design pattern, separating language-specific descriptive content from the base entity to support global deployments. The table is critical for enabling the Citizen Interaction Center application to present task type attribute mapping information in a user's preferred language, ensuring accessibility and usability across diverse geographic regions in versions 12.1.1 and 12.2.2.

Key Information Stored

The table stores translated text for attributes associated with task type mappings. Its structure is defined by a composite primary key that uniquely identifies each translated record. The most significant columns include TSK_TYP_ATTR_MAP_ID, which is the foreign key linking the translation to its corresponding base record in the CUG_TSK_TYP_ATTR_MAPS_B table. The LANGUAGE column holds the ISO code for the translation language (e.g., 'US' for American English). While the specific descriptive column names are not detailed in the provided metadata, translation tables in EBS typically contain columns such as SOURCE_LANG, DESCRIPTION, and potentially other user-facing text fields that require localization. The presence of the SOURCE_LANG column is a common feature, used to identify the original language of the data.

Common Use Cases and Queries

The primary use case is retrieving task type attribute mapping descriptions in a session-specific or specified language for UI rendering and reporting. A common SQL pattern involves joining the translation table with its base table while filtering by the desired language. For example, to fetch all active mappings with their English descriptions, a query would join on TSK_TYP_ATTR_MAP_ID and filter where LANGUAGE = 'US'. Application logic typically uses the FND_GLOBAL.APPS_INITIALIZE package to determine the user's session language, automatically retrieving the correct translation. Reporting on multilingual support or auditing translated content for specific mappings also relies on queries against this table. Developers must ensure joins account for the LANGUAGE column to avoid Cartesian products.

Related Objects

The table has a direct and essential relationship with its base table, as documented in the provided metadata.

  • CUG_TSK_TYP_ATTR_MAPS_B: This is the base table for the entity. The foreign key relationship is defined as CUG_TSK_TYP_ATTR_MAPS_TL.TSK_TYP_ATTR_MAP_ID references CUG_TSK_TYP_ATTR_MAPS_B. All translations are child records of a single parent record in this base table.

As a translation table, it is also intrinsically linked to the application's language and localization setup, interacting with standard Oracle EBS objects like FND_LANGUAGES. The table's primary key, CUG_TSK_TYP_ATTR_MAPS_TL_PK, is defined on the columns (TSK_TYP_ATTR_MAP_ID, LANGUAGE), enforcing data integrity for multilingual entries.