Results for “handler_id”

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

Overview

BIX_INTERACTIONS_INF is a table in the BIX schema (Interaction Center Intelligence), a component of the Oracle E-Business Suite product family that provides analytical and reporting capabilities for interaction center operations. The table resides in the Oracle EBS releases 12.1.1 and 12.2.2 and carries a VALID status in the data dictionary. Its documented purpose is to hold sales data broken up by product group and resource group, which positions it as a supplementary fact or detail store attached to interaction records rather than a standalone transactional entity.

From a Data Vault modeling perspective, the metadata heuristic classifies this table as satellite-leaning. This classification reflects its structure: it carries a dedicated surrogate primary key, references a parent interaction entity, and stores descriptive attribute payloads (handler, key, subkey, value) that describe context around an interaction. Rather than functioning as an independent hub, the table extends the BIX_INTERACTIONS parent with the granular detail required for dimensional and analytical reporting.

Key Information Stored

The table is documented with eight physical columns in the 12.1.1 schema. The most significant columns are:

• INTERACTIONS_INF_ID — the surrogate primary key, enforced by the constraint BIX_INTERACTIONS_INF_PK. This is a system-generated identifier with no business meaning.
• INTERACTIONS_ID — the foreign key to BIX_INTERACTIONS. This is the principal business-key candidate connecting the detail row to its parent interaction.
• HANDLER_ID — identifies the agent, resource, or handler associated with the interaction detail.
• KEY and SUBKEY — attribute name qualifiers, used to categorize the detail payload.
• VALUE — the payload attribute value, stored alongside its KEY/SUBKEY pair.
• PRODUCT_GROUP_ID — foreign key to FND_PRODUCT_GROUPS, supplying the product group segmentation referenced in the object description.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-tenant or organizational access partitioning.

The combination of INTERACTIONS_ID, HANDLER_ID, PRODUCT_GROUP_ID, and SECURITY_GROUP_ID acts as the effective business-key candidate for the row.

Common Use Cases and Queries

The table is primarily used in Interaction Center Intelligence reporting and in custom extensions that require sales detail segmented by product group and resource. Typical scenarios include:

• Aggregating sales amount by product group for a given date range, joining to BIX_INTERACTIONS for the interaction timestamp.
• Comparing performance across resource groups (HANDLER_ID) for a specific product line.
• Enforcing security-group filtering when exposing interaction detail to different business units.

A representative query:

SELECT i.INTERACTION_ID,
       inf.PRODUCT_GROUP_ID,
       inf.HANDLER_ID,
       SUM(inf.VALUE) AS total_value
FROM   BIX_BIX_INTERACTIONS_INF inf,
       BIX_INTERACTIONS i
WHERE  inf.INTERACTIONS_ID = i.INTERACTION_ID
AND    inf.SECURITY_GROUP_ID = :security_group
GROUP BY i.INTERACTION_ID, inf.PRODUCT_GROUP_ID, inf.HANDLER_ID;

Because KEY and SUBKEY are generic payload qualifiers, reports that need to isolate a specific metric typically filter on those columns before aggregation.

Related Objects

The following objects are the most significant in relation to this table:

• BIX_INTERACTIONS — parent entity; joined via INTERACTIONS_ID.
• BIX_INTERACTIONS_INF_PK — the primary key constraint on INTERACTIONS_INF_ID.
• FND_PRODUCT_GROUPS — lookup for product group segmentation, joined via PRODUCT_GROUP_ID.
• FND_SECURITY_GROUPS — organizational access partitioning, joined via SECURITY_GROUP_ID.
• FND_USER — related indirectly through handler identification for resource reporting.
• BIX Interaction Center Intelligence fact/dimension views — downstream analytical objects that consume this detail table for dashboard and warehouse loads.

Any modification to interaction detail flows through this table, making it a dependency for BIX reporting extracts and for the standard Oracle Interaction Center dashboards that rely on product-and-resource-group breakdowns.