Search Results cug_sr_task_attr_vals_b




Overview
Explore in AI Chat

Overview

The CUG_SR_TASK_ATTR_VALS_B table is a core data object within the Oracle E-Business Suite Citizen Interaction Center (CUG) module, specifically in versions 12.1.1 and 12.2.2. It functions as the base table for storing the specific values assigned to task type attributes that are linked to a Service Request (SR) type. This table is essential for configuring and managing the detailed workflow and data capture requirements for tasks generated from service requests. By defining what attribute values are permissible or required for tasks associated with a given SR type, it enables structured and consistent task execution within the Citizen Interaction Center's service management processes.

Key Information Stored

The table's primary purpose is to maintain the relationship between a Service Request Type, a Task Type, and the specific values for that task's attributes. While the full column list is not detailed in the provided metadata, the documented foreign keys and primary key reveal its critical structural components. The primary key column, SR_TASK_ATTR_VAL_ID, uniquely identifies each attribute value record. The TASK_TYPE_ATTR_MAP_ID column links to the CUG_TSK_TYP_ATTR_MAPS_B table, which defines the mapping of an attribute to a task type. The TSK_TYP_ATTR_DEPEND_ID column links to the CUG_TSK_TYP_ATTR_DEPS_B table, potentially governing conditional dependencies or validations for attribute values. The table likely contains columns for the actual attribute VALUE, the associated SR_TYPE_ID, and standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY).

Common Use Cases and Queries

This table is primarily accessed for configuration and reporting related to task templates and service request workflows. A common administrative use case is querying all configured task attribute values for a specific service request type to validate or audit setup. For reporting, it can be joined to task transactional data to analyze the values captured during task execution against their predefined templates. A typical SQL pattern involves joining to the translatable TL table and related mapping tables:

  • Retrieving configured task attribute details for an SR type: SELECT val.SR_TASK_ATTR_VAL_ID, tl.VALUE, map.SR_TYPE_ID FROM CUG_SR_TASK_ATTR_VALS_B val JOIN CUG_SR_TASK_ATTR_VALS_TL tl ON val.SR_TASK_ATTR_VAL_ID = tl.SR_TASK_ATTR_VAL_ID JOIN CUG_TSK_TYP_ATTR_MAPS_B map ON val.TASK_TYPE_ATTR_MAP_ID = map.TASK_TYPE_ATTR_MAP_ID WHERE map.SR_TYPE_ID = :p_sr_type_id AND tl.LANGUAGE = USERENV('LANG');
  • Identifying task attributes with dependency rules: SELECT * FROM CUG_SR_TASK_ATTR_VALS_B WHERE TSK_TYP_ATTR_DEPEND_ID IS NOT NULL;

Related Objects

The table exists within a tightly defined schema with specific foreign key relationships, as documented in the ETRM metadata.

  • Referenced By (Child Table): CUG_SR_TASK_ATTR_VALS_TL references this base table via the column CUG_SR_TASK_ATTR_VALS_TL.SR_TASK_ATTR_VAL_ID to store translated values for the attribute.
  • References To (Parent Tables):
    • CUG_TSK_TYP_ATTR_DEPS_B via column CUG_SR_TASK_ATTR_VALS_B.TSK_TYP_ATTR_DEPEND_ID. This links the attribute value to any conditional dependency rules.
    • CUG_TSK_TYP_ATTR_MAPS_B via column CUG_SR_TASK_ATTR_VALS_B.TASK_TYPE_ATTR_MAP_ID. This is the crucial link to the definition that maps a specific attribute to a task type for a service request type.

These relationships position CUG_SR_TASK_ATTR_VALS_B as a central junction table that materializes the configured attribute values defined in the mapping and dependency structures for SR-based tasks.