Search Results cug_tsk_typ_attr_maps_b




Overview

The table CUG_TSK_TYP_ATTR_MAPS_B is a core data entity within the Oracle E-Business Suite Citizen Interaction Center (CUG) module. It functions as a mapping or junction table that formally defines the association between a Task Type and its permissible Task Attributes. This table is essential for configuring the task management framework, enabling administrators to define which custom attributes are available for specific types of service requests or interactions. It provides the structural metadata that dictates data capture and validation rules for tasks within the CUG application, ensuring data integrity and consistency across task-related transactions in both EBS 12.1.1 and 12.2.2 environments.

Key Information Stored

The table's primary purpose is to store unique mappings, enforced by its primary and unique key constraints. The key columns are:

  • TSK_TYP_ATTR_MAP_ID: The primary key (PK) surrogate identifier for each unique mapping record.
  • TASK_TYPE_ID: A foreign key column referencing the JTF_TASK_TYPES_B table. This identifies the specific task type (e.g., "Site Inspection," "Complaint Investigation") to which attributes are assigned.
  • TASK_TYPE_ATTRIBUTE_CODE: A code identifying the specific attribute (e.g., "PRIORITY_LEVEL," "ESTIMATED_DURATION") associated with the task type. Together with TASK_TYPE_ID, this forms a unique key (UK1), preventing duplicate attribute assignments for the same task type.

These columns collectively establish a controlled, many-to-many relationship between task types and their extended attributes.

Common Use Cases and Queries

This table is central to setup, reporting, and data validation. A common administrative use case is querying all attributes configured for a given task type to verify setup or troubleshoot data entry screens. For example:

SELECT map.task_type_attr_map_id, map.task_type_id, map.task_type_attribute_code, tl.meaning
FROM cug_tsk_typ_attr_maps_b map,
cug_tsk_typ_attr_maps_tl tl
WHERE map.task_type_id = :p_task_type_id
AND map.tsk_typ_attr_map_id = tl.tsk_typ_attr_map_id
AND tl.language = USERENV('LANG');

Another critical use case involves data integrity validation for custom reporting. Analysts often join this table to the transactional table CUG_SR_TASK_ATTR_VALS_B to report on captured attribute values, ensuring they only report on valid, configured attribute mappings. Performance tuning may also require analyzing the volume of mappings or identifying task types with a high number of associated attributes.

Related Objects

CUG_TSK_TYP_ATTR_MAPS_B sits at the center of a defined relational model within the CUG module:

  • Parent Reference (Foreign Key):
    • JTF_TASK_TYPES_B: The table CUG_TSK_TYP_ATTR_MAPS_B references this core EBS task type definition table via the column TASK_TYPE_ID. This ensures a task type must exist before attributes can be mapped to it.
  • Child Dependencies (Referenced by Foreign Keys):
    • CUG_SR_TASK_ATTR_VALS_B: This transactional table stores the actual values entered for task attributes. It references CUG_TSK_TYP_ATTR_MAPS_B via the column TASK_TYPE_ATTR_MAP_ID, ensuring every stored value corresponds to a valid, pre-defined attribute mapping.
    • CUG_TSK_TYP_ATTR_MAPS_TL: This is the Translation table for CUG_TSK_TYP_ATTR_MAPS_B. It holds multilingual descriptions for the attribute mappings and references the base table via the column TSK_TYP_ATTR_MAP_ID.