Search Results bix_sum_agt_prd_n2




Overview

BIX.BIX_SUM_AGT_PRD is an Oracle E-Business Suite summary table that stores pre-aggregated interaction performance metrics for contact center agents, broken down by product group. It resides in the BIX schema and the APPS_TS_SUMMARY tablespace, and is owned as FND Design Data (BIX.BIX_SUM_AGT_PRD) with status VALID. The table is part of the Oracle Interaction Center / Telephony (Advanced Outbound and inbound interaction analytics) reporting layer, capturing rolled-up counts of transactions, sales quotes, leads generated, sales revenue, sales orders, promises to pay, and amounts collected at an hourly grain per agent and product group.

The object carries an explicit internal-use warning: Oracle does not support direct access to application data through this object except from standard Oracle Applications programs. Custom reporting should therefore treat it as read-only and expect schema changes across patch levels. Its ETRM metadata indicates a heuristic Data Vault classification of standalone; in Data Vault modeling terms this suggests treating the table as a self-contained aggregate or reference structure rather than a traditional hub, link, or satellite, since no foreign keys to other BIX summary entities are documented (its only outbound references are to shared FND tables). The single primary key BIX_SUM_AGT_PRD_PK is defined on SUM_AGT_PRD_ID.

Key Information Stored

The table holds 22 documented columns. The most significant include:

No unique index is documented other than the primary key; BIX_SUM_AGT_PRD_N2 is non-unique on (HOUR, RESOURCE_ID).

Common Use Cases and Queries

Typical use cases include agent productivity dashboards, product-group lead and revenue attribution, and hourly interaction-volume trending for capacity planning. Because the grain is agent/product-group/hour, a representative query for lead performance is:

SELECT RESOURCE_ID, HOUR, SUM(LEADS_GENERATED) LEADS, SUM(SALES_REVENUE) REVENUE FROM BIX.BIX_SUM_AGT_PRD GROUP BY RESOURCE_ID, HOUR ORDER BY HOUR;

Filtering by campaign or interaction center supports marketing attribution: WHERE CAMPAIGN_ID = :campaign_id or WHERE INTERACTION_CENTER_ID = :center_id. Although documented as non-unique, the (HOUR, RESOURCE_ID) index supports efficient range scans for a specific agent over a time window. Reporting tools such as Oracle BI or custom APPS views should join to FND_PRODUCT_GROUPS and FND_SECURITY_GROUPS for descriptive and security context, and always apply SECURITY_GROUP_ID filters where CRM hosting is enabled.

Related Objects

  • FND_PRODUCT_GROUPS — referenced via BIX_SUM_AGT_PRD.PRODUCT_GROUP_ID = FND_PRODUCT_GROUPS.PRODUCT_GROUP_ID.
  • FND_SECURITY_GROUPS — referenced via BIX_SUM_AGT_PRD.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID.
  • CCT_CALL_CENTER — source of INTERACTION_CENTER_ID for center-level aggregation and reporting.
  • BIX_SUM_AGT_PRD_PK — primary key constraint on SUM_AGT_PRD_ID.
  • BIX_SUM_AGT_PRD_N2 — non-unique index on (HOUR, RESOURCE_ID).
  • Sibling BIX summary tables and the FND schema objects referenced above complete the reporting dependency set; standard Oracle Applications programs populate and consume this object, and no additional supported API is documented in the metadata.