Search Results bix_sum_grp_prd_out_pk

Overview

BIX_SUM_GRP_PRD_OUT is a summary table owned by the BIX schema within the Oracle E-Business Suite Interaction Center Intelligence module. It aggregates interaction records from the BIX_INTERACTIONS base table to a daily grain, consolidating activity across the dimensions of time, agent, resource group, interaction center, campaign, and product group. The table serves as a pre-aggregated fact store, allowing operational and analytical reports on contact center productivity, revenue contribution, and product-group performance to run without scanning high-volume transactional interaction data.

The physical schema documented for ETRM 12.1.1 contains 37 columns. The table is bound by a surrogate primary key constraint, BIX_SUM_GRP_PRD_OUT_PK, defined on SUM_GRP_PRD_OUT_ID, and a unique key constraint, BIX_SUM_GRP_PRD_OUT_UK, defined over HOUR, RESOURCE_GROUP_ID, INTERACTION_CENTER_ID, CAMPAIGN_ID, and PRODUCT_GROUP_ID. Heuristic analysis of the foreign key structure classifies this object as standalone within a Data Vault modeling suggestion; it does not cleanly resolve to a hub, link, or satellite. Where a formal model is desired, the combination of HOUR, RESOURCE_GROUP_ID, INTERACTION_CENTER_ID, CAMPAIGN_ID, and PRODUCT_GROUP_ID can be treated as a candidate business key driving the daily summary grain, while the remaining measures behave as satellite-style descriptive metrics.

Key Information Stored

The most significant columns fall into identifier, dimensional, and measure categories:

• SUM_GRP_PRD_OUT_ID — Surrogate primary key, generated to uniquely identify each summary row.
• HOUR — Time dimension component; contributes to the unique business key and defines the daily reporting grain.
• RESOURCE_GROUP_ID — Identifies the agent resource group; part of the unique key.
• INTERACTION_CENTER_ID — Identifies the contact center; part of the unique key.
• CAMPAIGN_ID — Identifies the associated campaign; part of the unique key.
• PRODUCT_GROUP_ID — Product group dimension; foreign key to FND_PRODUCT_GROUPS and part of the unique key.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing data access partitioning.
• NUMBER_OF_INTERACTIONS — Core interaction count measure.
• TRANSFERS, CONTACTS, TRANSACTIONS — Volume measures for transferred, contacted, and transacted interactions.
• SALES_REVENUE, SALES_ORDERS, SALES_QUOTES, LEADS_GENERATED — Revenue and pipeline measures.
• AMOUNT_COLLECTED, PROMISE_TO_PAY — Collections-related measures.
• FIRST_INTERACTION_RESOLN_COUNT — First-contact resolution measure.
• OUTCOME_ID — Dimension linking summarization to interaction outcome.
• TALK_TIME, WRAP_TIME, IVR_TIME, ROUTE_TIME, SPEED_TO_ANSWER — Operational time and service-level measures.
• USER_ATTRIBUTE1 through USER_ATTRIBUTE5 — Configurable descriptive slots for client-specific extensions.

Common Use Cases and Queries

Typical reporting scenarios include daily agent-group productivity, campaign revenue attribution, product-group contact volume analysis, and service-level trending. A representative query aggregating revenue and interaction counts by product group and hour might read:

SELECT PRODUCT_GROUP_ID, HOUR, SUM(SALES_REVENUE), SUM(NUMBER_OF_INTERACTIONS)
FROM BIX.BIX_SUM_GRP_PRD_OUT
WHERE INTERACTION_CENTER_ID = :center_id
AND HOUR BETWEEN :from_date AND :to_date
AND SECURITY_GROUP_ID IN (:authorized_groups)
GROUP BY PRODUCT_GROUP_ID, HOUR;

Campaign performance reports join CAMPAIGN_ID to campaign master data, while product-oriented analysis joins PRODUCT_GROUP_ID to FND_PRODUCT_GROUPS. Security-aware queries must filter on SECURITY_GROUP_ID to honor folder-based access restrictions.

Related Objects

• BIX_INTERACTIONS — Source base table summarized into this table.
• FND_PRODUCT_GROUPS — Referenced via PRODUCT_GROUP_ID for product-group definitions.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID for access control.
• BIX_SUM_GRP_PRD_OUT_PK / BIX_SUM_GRP_PRD_OUT_UK — Primary and unique key constraints governing row identity and grain.
• Interaction center and campaign master tables — Joined through INTERACTION_CENTER_ID and CAMPAIGN_ID.