Search Results sum_grp_cls_id

Overview

The BIX_SUM_GRP_CLS table is a core data warehouse table within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Interaction Center Intelligence (BIX) module. It functions as a summary or aggregate fact table designed to support high-performance analytical reporting on customer interactions. Its primary role is to store pre-aggregated metrics from the detailed interaction data in the BIX_INTERACTIONS table, summarized along key business dimensions including time, agent groups, call centers, campaigns, and—critically for the user's search—interaction classification. This aggregation to the day level optimizes query performance for operational and historical reporting on contact center performance and customer engagement patterns.

Key Information Stored

The table stores summarized interaction metrics (e.g., count, duration, handle time) linked to dimensional keys. Key columns defining the aggregation grain and storing data include:

• SUM_GRP_CLS_ID: The primary surrogate key for each unique summary record.
• HOUR: Represents the day-level time dimension for the aggregation, typically storing a truncated date or a foreign key to a time dimension table.
• RESOURCE_GROUP_ID: Foreign key to the agent or resource group involved in the interactions.
• INTERACTION_CENTER_ID: Foreign key identifying the specific call or interaction center.
• CAMPAIGN_ID: Foreign key linking the summarized interactions to a marketing or telephony campaign.
• INTERACTION_CLASSIFICATION: A critical field that categorizes the type or purpose of the summarized interactions (e.g., inquiry, complaint, sales). This is the primary column of interest for classification-based analysis.

Common Use Cases and Queries

This table is central to generating performance reports for contact center management. Common use cases involve analyzing volume and efficiency by interaction type, tracking campaign effectiveness, and monitoring group performance. A typical analytical query might retrieve daily interaction counts by classification for a specific agent group:

SELECT hour,
       interaction_classification,
       SUM(interaction_count) AS total_interactions
FROM bix.bix_sum_grp_cls
WHERE resource_group_id = 1000
AND hour BETWEEN TRUNC(SYSDATE - 30) AND TRUNC(SYSDATE - 1)
GROUP BY hour, interaction_classification
ORDER BY hour DESC;

Another common pattern is joining with dimension tables (like JTF_RS_GROUPS for group names) to produce manager-friendly reports that break down average handle time or service level by interaction classification and campaign.

Related Objects

Based on the provided metadata, BIX_SUM_GRP_CLS has defined relationships with other objects through its primary and unique keys:

• Primary Key: The table is primarily identified by BIX_SUM_GRP_CLS_PK on the column SUM_GRP_CLS_ID. This key would be referenced by any foreign keys in dependent fact or summary tables.
• Unique Key: The table enforces a unique constraint, BIX_SUM_GRP_CLS_UK, on the combination of HOUR, RESOURCE_GROUP_ID, INTERACTION_CENTER_ID, CAMPAIGN_ID, and INTERACTION_CLASSIFICATION. This ensures data integrity for the specific aggregation grain.
• Source Table: As per its description, the table's data is sourced from and summarizes the granular BIX_INTERACTIONS table.
• Dimension Tables: While not explicitly listed in the snippet, the ID columns (RESOURCE_GROUP_ID, INTERACTION_CENTER_ID, CAMPAIGN_ID) are foreign keys to their respective dimension tables within the EBS schema, such as JTF_RS_GROUPS, ICI_INTERACTION_CENTERS, and AMS_CAMPAIGNS_ALL_B.