Search Results bix_sum_grp_cls

Overview

BIX_SUM_GRP_CLS is a summary (aggregate) table owned by the BIX schema within the Oracle E-Business Suite Interaction Center Intelligence module (BIX). It consolidates interaction data from the base transactional table BIX_INTERACTIONS and rolls it up across four analytical dimensions: time (to the day, via the HOUR column), agent resource group, interaction center, campaign, and interaction classification. The presence of the INTERACTION_CLASSIFICATION column makes this object directly relevant to the user's search term, as it is one of the table's primary grouping attributes alongside time, agent group, call center, and campaign. The table is marked VALID in the ETRM 12.1.1 dataset and comprises 42 columns.

From a dimensional modeling perspective, the mined metadata suggests a standalone Data Vault classification. No parent hub or link dependencies are recorded other than a single foreign key to FND_SECURITY_GROUPS (via SECURITY_GROUP_ID). This heuristic implies the table behaves as a self-contained aggregate rather than a normalized transactional entity, which is consistent with its role as a pre-aggregated fact table feeding Interaction Center analytics dashboards and reports.

Key Information Stored

The most operationally significant columns fall into three categories: identifiers, grouping attributes, and measures.

• SUM_GRP_CLS_ID — Surrogate primary key, defined by the BIX_SUM_GRP_CLS_PK constraint. It uniquely identifies each summarized row and is the recommended join key for internal relationships.
• Business-key candidates — The unique index BIX_SUM_GRP_CLS_UK combines HOUR, RESOURCE_GROUP_ID, INTERACTION_CENTER_ID, CAMPAIGN_ID, and INTERACTION_CLASSIFICATION. These five columns together define the natural grain of the summary (the level of aggregation).
• Grouping attributes — HOUR (day-level time bucket), RESOURCE_GROUP_ID (agent group), INTERACTION_CENTER_ID (call center), CAMPAIGN_ID, and INTERACTION_CLASSIFICATION.
• Volume measures — NUMBER_OF_INTERACTIONS, INTERACTIONS_ANSWERED_LIVE, INTERACTIONS_HANDLED_BY_IVR, ABANDONED_COUNT, TRANSFERS, CONTACTS, TRANSACTIONS.
• Time measures — TALK_TIME, WRAP_TIME, WAIT_TIME_TO_ABANDON, SPEED_TO_ANSWER, IVR_TIME, ROUTE_TIME, PARTY_WAIT_TIME, IDLE_TIME, RESOLUTION_TIME and RESOLUTION_TIME_INTERNAL.
• Business outcome measures — FIRST_INTERACTION_RESOLN_COUNT, SALES_ORDERS, SALES_QUOTES, SALES_REVENUE, LEADS_GENERATED, PROMISE_TO_PAY, AMOUNT_COLLECTED.
• Security and extensibility — SECURITY_GROUP_ID (FK to FND_SECURITY_GROUPS) supports multi-org/data security filtering, while USER_ATTRIBUTE1 through USER_ATTRIBUTE5 provide customer-defined extension slots.

Common Use Cases and Queries

Because the table is pre-aggregated, it is primarily used for reporting and analytics rather than transaction processing. Typical scenarios include agent group performance analysis, interaction classification trending, campaign ROI measurement (via SALES_REVENUE and SALES_ORDERS), and call center abandonment/speed-to-answer monitoring.

A representative query for classification rollups by day would resemble:

SELECT hour, interaction_classification,
       SUM(number_of_interactions) AS interactions,
       SUM(talk_time) AS total_talk_time,
       SUM(sales_revenue) AS revenue
FROM   bix.bix_sum_grp_cls
WHERE  interaction_center_id = :center_id
  AND  hour BETWEEN :from_date AND :to_date
GROUP  BY hour, interaction_classification
ORDER  BY hour;

Filtering by SECURITY_GROUP_ID is standard in multi-org deployments, and joining RESOURCE_GROUP_ID or CAMPAIGN_ID to their respective dimension tables enriches the result set with descriptive attributes.

Related Objects

• BIX_INTERACTIONS — Source transactional table from which BIX_SUM_GRP_CLS is summarized.
• FND_SECURITY_GROUPS — Direct FK via SECURITY_GROUP_ID; governs data visibility per security profile.
• BIX_SUM_GRP_CLS_PK — Primary key constraint on SUM_GRP_CLS_ID.
• BIX_SUM_GRP_CLS_UK — Unique constraint on HOUR, RESOURCE_GROUP_ID, INTERACTION_CENTER_ID, CAMPAIGN_ID, INTERACTION_CLASSIFICATION.
• Campaign and resource group dimension tables — Joined on CAMPAIGN_ID and RESOURCE_GROUP_ID respectively to resolve descriptive names.
• Interaction center dimension — Joined on INTERACTION_CENTER_ID for center-level reporting.

Collectively, these relationships position BIX_SUM_GRP_CLS as a central reporting fact for Interaction Center Intelligence, with interaction classification serving as one of its key analytical axes.