Search Results cug_sr_type_dup_chk_info




Overview
Explore in AI Chat

Overview

The CUG_SR_TYPE_DUP_CHK_INFO table is a core data object within the Oracle E-Business Suite Citizen Interaction Center (CUG) module. Its primary function is to store configurable business rules that the application uses to identify and flag potential duplicate Service Requests (SRs). By defining specific criteria at the Service Request Type level, this table enables organizations to reduce redundant case entries, improve data quality, and enhance operational efficiency within the service management process. It acts as a configuration repository that drives the duplicate-checking logic, a critical feature for managing high volumes of citizen or customer interactions in versions 12.1.1 and 12.2.2 of Oracle EBS.

Key Information Stored

The table's structure is designed to link duplicate-checking rules to specific Service Request Types and resources. The most critical columns include the primary key, SR_TYPE_DUP_CHK_INFO_ID, which uniquely identifies each rule configuration. The INCIDENT_TYPE_ID column is a foreign key that links the rule to a specific Service Request Type defined in the CS_INCIDENT_TYPES_B table. Another significant column is RESOURCE_ID, which references the JTF_RS_RESOURCE_EXTNS table to associate the rule with a specific agent or resource group. While the exact business rule criteria columns are not detailed in the provided metadata, the table's description confirms it stores the rule definitions themselves, which likely specify the matching fields (e.g., contact details, problem summary) and thresholds for determining a duplicate.

Common Use Cases and Queries

The primary use case is the real-time validation performed when a user creates or updates a Service Request. The application queries this table to retrieve the active duplicate-checking rules for the given incident type and resource, then executes logic to search for existing SRs matching the defined criteria. Administrators use backend setups to maintain these rules. Common reporting and diagnostic queries include listing all configured rules and identifying rules for a specific Service Request Type.

  • Sample Query: List all duplicate check rules:
    SELECT sr_type_dup_chk_info_id, incident_type_id, resource_id FROM cug.cug_sr_type_dup_chk_info ORDER BY incident_type_id;
  • Sample Query: Find rules for a specific Service Request Type:
    SELECT c.* FROM cug.cug_sr_type_dup_chk_info c, cs.cs_incident_types_b t WHERE c.incident_type_id = t.incident_type_id AND t.name = '<SR_TYPE_NAME>';

Related Objects

The table is centrally connected to other EBS entities through defined foreign key relationships, ensuring referential integrity and enabling joins for data retrieval.

  • CS_INCIDENT_TYPES_B: This is the core Oracle Service table defining Service Request Types. The relationship is via CUG_SR_TYPE_DUP_CHK_INFO.INCIDENT_TYPE_ID → CS_INCIDENT_TYPES_B.INCIDENT_TYPE_ID. This link ensures rules are applied to valid, existing SR types.
  • JTF_RS_RESOURCE_EXTNS: This table from the Resource Manager module stores information about agents and resources. The relationship is via CUG_SR_TYPE_DUP_CHK_INFO.RESOURCE_ID → JTF_RS_RESOURCE_EXTNS.RESOURCE_ID. This allows for granular assignment of duplicate-checking rules, potentially varying rules by agent or team.