Search Results bix_interactions_inf1_n1

Overview

BIX.BIX_INTERACTIONS_INF is a summary-table object owned by the BIX schema and located in the APPS_TS_SUMMARY tablespace. It stores interaction-level informational attributes captured by the BIX (Business Intelligence Extraction) infrastructure that supports Oracle EBS interaction and CRM reporting. Each row represents a single interaction information record, identified by a surrogate primary key (INTERACTIONS_INF_ID) and linked to its parent interaction through a foreign key to BIX_INTERACTIONS.

Structurally, BIX_INTERACTIONS_INF hangs off a parent entity and carries descriptive detail — a key/subkey/value triplet together with context columns such as HANDLER_ID and PRODUCT_GROUP_ID. Following the heuristic Data Vault classification derived from the FK structure (satellite-leaning), this object is best modeled as a suggestion: a satellite of BIX_INTERACTIONS, where INTERACTIONS_ID acts as the reference to the parent hub/link and the surrounding columns carry the contextual attributes. It is not intended to be a hub of its own. Oracle marks this object for internal use only, so supported access is through standard Oracle Applications programs rather than direct DML.

Key Information Stored

The documented physical schema contains eight columns. The most significant are:

• INTERACTIONS_INF_ID (NUMBER) — the surrogate primary key defined by BIX_INTERACTIONS_INF_PK, uniquely identifying each informational attribute row.
• INTERACTIONS_ID (NUMBER) — the foreign key to BIX_INTERACTIONS, anchoring each row to its parent interaction; this is the join column used in the non-unique index BIX_INTERACTIONS_INF1_N1 and the most likely business-key candidate for reaching the parent record.
• HANDLER_ID (NUMBER, length 15) — the client application ID that identifies the handler or source application associated with the informational value.
• KEY (VARCHAR2, 32) — the descriptive attribute name, for example "Revenue" in the documentation sample.
• SUBKEY (VARCHAR2, 32) — an optional qualifier for the key, documented as "Null" in the supplied example.
• VALUE (NUMBER, 16) — the numeric value of the attribute, documented as "55.00" in the sample.
• PRODUCT_GROUP_ID (NUMBER) — foreign key to FND_PRODUCT_GROUPS, enabling product-group filtering and reporting by application context.
• SECURITY_GROUP_ID (NUMBER) — the security group column retained for CRM hosting and multi-organization security enforcement.

Note that the primary key (INTERACTIONS_INF_ID) is distinct from the business-key path (INTERACTIONS_ID), and the index provided on INTERACTIONS_ID is non-unique, reflecting the one-to-many relationship with the parent interaction.

Common Use Cases and Queries

The table is typically queried to surface the informational attributes attached to an interaction for reporting, BI extraction, or reconciliation against the parent interaction record. A common pattern is to return all key/value pairs for a given interaction or application:

• Retrieve attributes for a specific interaction: SELECT INTERACTIONS_INF_ID, KEY, SUBKEY, VALUE FROM BIX.BIX_INTERACTIONS_INF WHERE INTERACTIONS_ID = :interactions_id;
• Filter by application handler: ... WHERE HANDLER_ID = :handler_id AND PRODUCT_GROUP_ID = :product_group_id;
• Locate a named attribute: ... WHERE KEY = 'Revenue';
• Join to the parent interaction to enrich reporting: SELECT i.INTERACTIONS_ID, n.KEY, n.VALUE FROM BIX.BIX_INTERACTIONS i JOIN BIX.BIX_INTERACTIONS_INF n ON n.INTERACTIONS_ID = i.INTERACTIONS_ID;
• Summarize attribute values by product group for BI aggregation: SELECT PRODUCT_GROUP_ID, KEY, SUM(VALUE) FROM BIX.BIX_INTERACTIONS_INF GROUP BY PRODUCT_GROUP_ID, KEY;

Because the table is populated and maintained by the standard Oracle Applications integration and the BIX extraction programs, custom code should treat it as read-only for reporting and analysis.

Related Objects

The most significant related objects, based on the documented FK and dependency data, are:

• BIX.BIX_INTERACTIONS — the parent table joined via BIX_INTERACTIONS_INF.INTERACTIONS_ID = BIX_INTERACTIONS.INTERACTIONS_ID.
• FND_PRODUCT_GROUPS — joined via BIX_INTERACTIONS_INF.PRODUCT_GROUP_ID = FND_PRODUCT_GROUPS.PRODUCT_GROUP_ID for application context.
• FND_SECURITY_GROUPS — joined via BIX_INTERACTIONS_INF.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID for CRM hosting security.
• APPS.BIX_INTERACTIONS_INF — the APPS-level synonym/view listed as referencing this object, used by standard applications and concurrent programs.
• BIX_INTERACTIONS_INF1_N1 — the non-unique index on INTERACTIONS_ID that supports parent lookups and the join to BIX_INTERACTIONS.

This object does not itself reference any database object beyond these dependencies, confirming its role as a dependent satellite within the BIX interaction information model.