Search Results bix_dm_agent_call_sum_pkg




Overview
Explore in AI Chat

Overview

The concurrent program BIX_DM_AGENT_CALL_SUMMARY_PKG belongs to the product BIX – Interaction Center Intelligence, a module now classified as obsolete within the Oracle E-Business Suite. The program is identified by the user-facing name Populate Interaction Center Intelligence Calls Summary and is documented as an enabled concurrent program in ETRM 12.2.2. Its functional purpose is to collect Call summary information, specifically gathering both Calls Summary and Agent Summary information for downstream reporting and analysis within the Interaction Center Intelligence data model.

Interaction Center Intelligence historically supported the telephony and contact-center analytics layer of Oracle EBS, providing aggregated insight into call volumes, agent activity, and related interaction metrics. The BIX_DM_AGENT_CALL_SUMMARY_PKG program serves as the data-collection mechanism that populates the summary structures consumed by those analytical reports. Because the module is marked obsolete, organizations running 12.1.1 or 12.2.2 should treat this program as a legacy artifact retained for backward compatibility rather than as a component of current strategic functionality.

Execution Details

The documented execution attributes of this concurrent program are as follows:

  • Product: BIX – Interaction Center Intelligence (Obsolete)
  • Enabled: Yes
  • Execution Method: PL/SQL Stored Procedure
  • Argument Method: Standard
  • Executable: BIX_DM_AGENT_CALL_SUM_PKG
  • Execution Filename: BIX_DM_AGENT_CALL_SUMMARY_PKG.COLLECT_CALLS_SUMMARY

The program is therefore implemented as a PL/SQL stored procedure entry point. The executable registered in the concurrent program definition is BIX_DM_AGENT_CALL_SUM_PKG, while the actual invocation resolves to the packaged procedure BIX_DM_AGENT_CALL_SUMMARY_PKG.COLLECT_CALLS_SUMMARY. This distinction between the registered executable name and the packaged routine is common in EBS, where the executable definition points to a PL/SQL package and the specific procedure is named in the execution filename. The standard argument method indicates that arguments, if any, follow the conventional Oracle concurrent program argument conventions rather than a specialized or token-based method.

How to Run

Users submit this program through the standard Submit Request (SRS) window, accessible from the navigation menu or by running the Submit a New Request form. Because the argument method is documented as Standard, the program may present one or more defined parameters in the SRS parameters region; the ETRM metadata excerpt provided does not enumerate specific parameter prompts, so administrators should inspect the concurrent program definition in the Concurrent Programs form to determine the exact parameter list, value sets, and any required defaults.

Typical operational guidance includes scheduling the request during periods of low contact-center activity, since summary collection may involve reading substantial call-detail volumes. The program can be submitted on demand or added to a request set for recurring execution. As with any BIX program in the obsolete module, validate that dependent objects remain available in the target instance before scheduling, particularly after upgrades to 12.2.2 where obsolete components may have been superseded.

Related Objects

The program is closely associated with the following components:

  • BIX_DM_AGENT_CALL_SUM_PKG – the registered executable that fronts the packaged procedure.
  • BIX_DM_AGENT_CALL_SUMMARY_PKG.COLLECT_CALLS_SUMMARY – the actual PL/SQL routine invoked at runtime.
  • Interaction Center Intelligence summary and staging tables – the data structures populated by the collection process, which feed the BIX agent and call summary reports.
  • Related BIX data-collection programs – companion concurrent programs in the BIX module that gather complementary interaction data and are commonly assembled into the same request set.

Because BIX is marked obsolete, related interface tables, APIs, and reports may no longer be documented in current release notes. Implementers should consult the original BIX data model documentation and verify object existence in the specific 12.1.1 or 12.2.2 instance before relying on this program in a production schedule.