Search Results sum_info_config_id

Overview

The BIX.BIX_SUM_INFO_CONFIG table is a configuration and metadata table within the Oracle E-Business Suite (EBS) Business Intelligence (BI) for Interaction Center (BIX) product. Its primary role is to define the dimensional structure for summary data aggregation within the BIX reporting framework. Specifically, it stores configuration records that dictate which attributes—such as HOUR, CAMPAIGN, or RESOURCE_GROUP—are to be treated as dimensions (i.e., grouping criteria) when generating summarized interaction data. This table is critical for enabling flexible and performant reporting by pre-defining how detailed interaction records are rolled up into summary fact tables. It operates under the BIX schema and is stored in the APPS_TS_SUMMARY tablespace, indicating its purpose for summary data management. As noted in the documentation, direct access to this object is for Oracle Internal Use Only and is unsupported except from standard Oracle Applications programs.

Key Information Stored

The table's structure centers on a primary key and a series of flags that control dimensional analysis. The SUM_INFO_CONFIG_ID column serves as the unique primary key for each configuration record. The HANDLER_ID acts as a Client Application ID, likely linking the configuration to a specific data processing handler or module. A series of columns, including HOUR, CAMPAIGN, LIST, SCRIPT, PRODUCT_GROUP, RESOURCE_NAME, RESOURCE_GROUP, INTERACTION_CENTER, MEDIA_ITEM_TYPE, INTERACTION_TYPE, OUTCOME, RESULT, REASON, and PARTY, are all of datatype NUMBER. For these, a value of '1' indicates the attribute is to be used as a dimension for summarization, while '0' indicates it is not. The INERACTION_CLASSIFICATION column (VARCHAR2) appears to serve a similar purpose. The table also provides extensibility through five USER_ATTRIBUTE columns and includes a SECURITY_GROUP_ID for CRM hosting considerations.

Common Use Cases and Queries

The primary use case for BIX_SUM_INFO_CONFIG is to administer the summarization framework for BIX reporting. An administrator would query and maintain this table to enable or disable specific reporting dimensions, thereby controlling the grain and performance of summary tables. A common query would retrieve the active dimensional configuration for a specific handler to understand the reporting structure. For example:

• To view all configurations: SELECT * FROM BIX.BIX_SUM_INFO_CONFIG ORDER BY SUM_INFO_CONFIG_ID;
• To check which dimensions are enabled for a specific handler: SELECT HANDLER_ID, HOUR, CAMPAIGN, RESOURCE_GROUP FROM BIX.BIX_SUM_INFO_CONFIG WHERE HANDLER_ID = &handler_id;
• To identify configurations where "CAMPAIGN" is a key reporting dimension: SELECT SUM_INFO_CONFIG_ID, HANDLER_ID FROM BIX.BIX_SUM_INFO_CONFIG WHERE CAMPAIGN = 1;

These configurations directly influence the ETL processes that populate BIX summary fact tables, which are subsequently used for dashboards and operational reports in Oracle CRM.

Related Objects

The documented relationship for this table is its primary key constraint, BIX_SUM_INFO_CONFIG_PK, on the SUM_INFO_CONFIG_ID column. This key is almost certainly referenced by foreign keys in child summary fact tables within the BIX schema, such as various BIX_SUM_* fact tables (e.g., BIX_SUM_AGENT_PERF_F, BIX_SUM_CAMPAIGN_F), which would store the aggregated data based on the dimensions activated in this configuration table. The HANDLER_ID column may also serve as a foreign key to a handler definition table, though this specific relationship is not detailed in the provided metadata. Developers and administrators should trace dependencies from this table to discover the complete set of related summary objects.