Search Results sum_grp_prd_out_id

Overview

The BIX_SUM_GRP_PRD_OUT table is a summary data object within the now-obsolete Oracle Interaction Center Intelligence (BIX) module for Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. Its primary role was to serve as a performance optimization and reporting layer for interaction center analytics. The table aggregates raw interaction data from the BIX_INTERACTIONS table, summarizing it to a daily grain across several key business dimensions, including time, agent groups, call centers, campaigns, and product groups. This pre-aggregation was designed to facilitate faster reporting and analysis of contact center performance metrics related to specific product groups without requiring complex, on-the-fly queries against the granular interaction data. The ETRM metadata explicitly notes this table is "Not implemented in this database," indicating it may have been a planned object that was not deployed in standard installations or was superseded by other reporting structures.

Key Information Stored

The table stores aggregated metrics derived from customer interactions. Its structure is defined by a combination of dimension foreign keys and a time grain. The most critical columns include the dimension identifiers that form the unique key (BIX_SUM_GRP_PRD_OUT_UK): HOUR, RESOURCE_GROUP_ID, INTERACTION_CENTER_ID, CAMPAIGN_ID, and PRODUCT_GROUP_ID. The PRODUCT_GROUP_ID is a central field, linking the summarized metrics to a specific categorization of products or services, which was a core dimension for analysis. The table's primary key is a surrogate key, SUM_GRP_PRD_OUT_ID. While the specific fact columns (e.g., call count, duration, outcome counts) are not listed in the provided metadata, typical summary tables in this context would contain numerical aggregates such as total interactions, average handle time, and number of sales or service requests related to each product group.

Common Use Cases and Queries

This table supported analytical reporting for contact center managers and campaign analysts. Common use cases included analyzing the volume and effectiveness of interactions segmented by product line, assessing agent group performance on specific product-related inquiries, and measuring campaign effectiveness in generating product interest. A typical query would filter and group by PRODUCT_GROUP_ID to generate reports.

• Product Group Performance Report: SELECT PRODUCT_GROUP_ID, SUM(INTERACTION_COUNT), AVG(HANDLE_TIME) FROM BIX_SUM_GRP_PRD_OUT WHERE HOUR BETWEEN [date1] AND [date2] GROUP BY PRODUCT_GROUP_ID;
• Campaign-to-Product Analysis: SELECT CAMPAIGN_ID, PRODUCT_GROUP_ID, SUM(SALES_COUNT) FROM BIX_SUM_GRP_PRD_OUT WHERE RESOURCE_GROUP_ID = [group_id] GROUP BY CAMPAIGN_ID, PRODUCT_GROUP_ID;

Related Objects

Based on the provided ETRM relationship data, the primary related object is the source table for its summarized data. The table's unique key suggests foreign key relationships to various dimension tables, though these are not explicitly listed.

• BIX_INTERACTIONS: This is the foundational transactional table cited in the description. The BIX_SUM_GRP_PRD_OUT table is a direct aggregate of data from this source, though no formal foreign key is documented in the snippet.
• Primary Key Relationship: The table has a self-referential relationship via its defined primary key constraint, BIX_SUM_GRP_PRD_OUT_PK, on the column SUM_GRP_PRD_OUT_ID.

The absence of documented foreign keys to dimension tables (like a product group master table) in the provided metadata suggests those relationships may have been enforced at the application level or are documented elsewhere in the full ETRM.