Results for “bix_sum_info”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BIX_SUM_INFO is a table owned by the BIX schema, the database account associated with the Interaction Center Intelligence product family in Oracle E-Business Suite. Its documented purpose is to serve as a staging and summarization repository into which third-party applications write interaction data that must be aggregated along a configurable set of dimensions. Rather than acting as a transactional fact table for the Interaction Center itself, BIX_SUM_INFO functions as an integration landing zone: external systems deposit rows describing an interaction together with its dimensional context, and the Interaction Center Intelligence reporting layer consumes those rows to produce summarized metrics such as interaction counts by campaign, list, script, resource, or outcome.

The table is deployed in both EBS 12.1.1 and 12.2.2 with an identical documented physical schema of 27 columns. From a Data Vault modeling perspective, the mined relationship data classifies BIX_SUM_INFO as a standalone structure. While the table does carry foreign keys to FND_PRODUCT_GROUPS, FND_SECURITY_GROUPS, and JTF_IH_SCRIPTS, the heuristic analysis does not place it in a conventional hub, link, or satellite hierarchy; it is best modeled as an independent integration entity whose columns combine dimension references and additive measures in a single denormalized row.

Key Information Stored

The surrogate primary key is SUM_INFO_ID, enforced by the BIX_SUM_INFO_PK constraint. No separate business-key unique index is documented, so uniqueness of an inbound summarization record is established by the generated identifier rather than by a natural composite key. The most significant columns fall into three groups:

• Dimensional references: CAMPAIGN_ID, LIST_ID, SCRIPT_ID, RESOURCE_ID, RESOURCE_GROUP_ID, INTERACTION_CENTER_ID, HANDLER_ID, OUTCOME_ID, RESULT_ID, REASON_ID, and PARTY_ID identify the marketing, telephony, and interaction context of the summarized activity.
• Classification attributes: INTERACTION_TYPE, INERACTION_CLASSIFICATION, MEDIA_ITEM_TYPE, and the time dimension HOUR determine how the record is bucketed during aggregation. Note that INERACTION_CLASSIFICATION is stored with the documented spelling variance.
• Flexible key/value and measure columns: KEY, SUBKEY, VALUE, and NUMBER_OF_INTERACTIONS carry the summarizing application's own business key and the additive interaction count, while USER_ATTRIBUTE1 through USER_ATTRIBUTE5 provide extensibility for third-party-specific attributes.

PRODUCT_GROUP_ID and SECURITY_GROUP_ID control multi-tenant and function-security visibility of each row.

Common Use Cases and Queries

The primary use case is external data submission: a third-party IVR, dialer, or web channel writes rows into BIX_SUM_INFO, and Interaction Center Intelligence reports read them back aggregated across the dimensions present in the table. A representative aggregation query groups by the interaction dimensions while filtering on security:

SELECT CAMPAIGN_ID, OUTCOME_ID, INTERACTION_TYPE,
       SUM(NUMBER_OF_INTERACTIONS) TOTAL_INTERACTIONS
FROM   BIX.BIX_SUM_INFO
WHERE  PRODUCT_GROUP_ID = :product_group
AND    TRUNC(HOUR) BETWEEN :start_date AND :end_date
GROUP BY CAMPAIGN_ID, OUTCOME_ID, INTERACTION_TYPE;

Other common patterns include an inbound validation query that checks whether a KEY/SUBKEY/VALUE combination already exists before insert, and a purge routine that removes aging summarization rows by HOUR. Reporting consumers typically join to FND_SECURITY_GROUPS to enforce row-level access by responsibility.

Related Objects

The following objects are the most significant dependencies for BIX_SUM_INFO:

• JTF_IH_SCRIPTS — referenced through SCRIPT_ID; supplies the script definition associated with each summarized interaction record.
• FND_PRODUCT_GROUPS — referenced through PRODUCT_GROUP_ID; partitions data by application product group in multi-tenant deployments.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID; drives row-level security filtering on queries against the table.
• BIX_SUM_INFO_PK — the primary key constraint over SUM_INFO_ID that guarantees row identity.
• FND_USER / FND_RESPONSIBILITY views — indirectly constrain visibility of BIX_SUM_INFO rows through the security group chain.
• Interaction Center Intelligence reporting views — the consuming layer that aggregates NUMBER_OF_INTERACTIONS along the CAMPAIGN_ID, LIST_ID, RESOURCE_ID, and OUTCOME_ID dimensions.