Results for “ineraction_classification”

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

Overview

BIX_SUM_INFO_CONFIG is a configuration table owned by the BIX schema (Interaction Center Intelligence) in Oracle E-Business Suite 12.1.1 and 12.2.2. According to the ETRM documentation, the table "specifies the dimensions that a particular application will use for summarizing into BIX_SUM_INFO." In practical terms, it functions as the dimensional-mapping control table for the BIX summarization engine: each row identifies a handler (application context) and declares which analytical dimensions should be aggregated when interaction data is rolled up into the summary store BIX_SUM_INFO.

The metadata classifies this table heuristically as standalone in the Data Vault sense, with no inbound foreign-key dependents. Under a Data Vault modeling interpretation, the single documented foreign key to FND_SECURITY_GROUPS and the absence of dependent child tables suggest the object behaves more like a satellite or reference table anchored to a business handler key, rather than a hub or link. This classification should be treated as a modeling suggestion, not a physical constraint in the EBS schema.

The object has 23 documented columns, is flagged VALID, and is secured through Oracle's standard multi-tenant security model via SECURITY_GROUP_ID.

Key Information Stored

The table's primary key is BIX_SUM_INFO_CONFIG_PK, defined on the surrogate column SUM_INFO_CONFIG_ID, generated via a sequence. A secondary unique key, BIX_SUM_INFO_CONFIG_UK, is defined on HANDLER_ID, making HANDLER_ID the primary business-key candidate — one configuration row per application handler.

The column list divides naturally into an identity/security group and a dimensional-flag group:

• SUM_INFO_CONFIG_ID — surrogate primary key, referenced in ETRM by the index BIX_SUM_INFO_CONFIG_PK.
• HANDLER_ID — business key identifying the specific application or interaction handler whose summarization behavior is configured.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing operating-unit/security-group isolation of configuration rows.
• Time dimension: HOUR — flag controlling hourly roll-up granularity.
• Campaign and audience dimensions: CAMPAIGN, LIST, SCRIPT, and OUTCOME — directing summarization by campaign, contact list, script, and call outcome.
• Product and resource dimensions: PRODUCT_GROUP, RESOURCE_NAME, and RESOURCE_GROUP — controlling aggregation by product hierarchy and by agent or agent group.
• Interaction dimensions: INTERACTION_CENTER, MEDIA_ITEM_TYPE, INTERACTION_TYPE, INERACTION_CLASSIFICATION, RESULT, REASON, and PARTY — the interaction-context facets used to slice summarized activity.
• USER_ATTRIBUTE1 through USER_ATTRIBUTE5 — a five-column DFF-style extension set supporting client-specific dimensions without schema change.

Common Use Cases and Queries

The most common operational use is interrogating which dimensions are active for a given handler before running or diagnosing a summarization batch. A representative query resolves the business key and joins to the security group:

• SELECT c.SUM_INFO_CONFIG_ID, c.HANDLER_ID, c.CAMPAIGN, c.RESOURCE_GROUP, c.INTERACTION_TYPE, c.SECURITY_GROUP_ID FROM BIX.BIX_SUM_INFO_CONFIG c WHERE c.HANDLER_ID = :handler_id;
• Security-filtered lookup: SELECT * FROM BIX_SUM_INFO_CONFIG WHERE SECURITY_GROUP_ID = :sg_id ORDER BY HANDLER_ID;
• Audit of enabled dimensions: SELECT HANDLER_ID, HOUR, CAMPAIGN, LIST, SCRIPT FROM BIX_SUM_INFO_CONFIG;

Reporting scenarios include validating that a newly deployed interaction handler has the expected dimensional flags set, comparing configuration across operating units, and confirming the presence of user-defined attributes before extending analytics.

Related Objects

• FND_SECURITY_GROUPS — referenced by BIX_SUM_INFO_CONFIG.SECURITY_GROUP_ID; the sole documented FK relationship.
• BIX_SUM_INFO — the summary target populated according to the dimension flags defined here.
• BIX_SUM_INFO_CONFIG_PK / BIX_SUM_INFO_CONFIG_UK — primary and unique indexes on SUM_INFO_CONFIG_ID and HANDLER_ID respectively.
• BIX application handler tables — referenced indirectly through HANDLER_ID to identify the owning application.

Because the object is classified standalone, no child tables cascade from it; dependencies flow outward from configuration into the summarization process rather than inward from transactional data.