Search Results bix_cci_collect

Overview

APP.BIX_CCI_COLLECT is a PL/SQL package registered in the APPS schema and classified under Oracle EBS as an "OTHER" API within the Customer Intelligence (BIX) product family. The package is documented as VALID in ETRM for both 12.1.1 and 12.2.2. Its purpose is to gather customer interaction data from the Oracle Interaction History (IH) and related interaction tables and consolidate that data into the structures used by the Customer Intelligence collection process. In practice the package acts as an extraction and aggregation layer: it reads raw interaction records generated by CRM, telephony, e-mail, and other channel activities, and produces the collected interaction rows that downstream BIX analytics consume. The package is therefore part of the plumbing that supports customer intelligence reporting rather than an end-user facing feature.

Key Procedures and Functions

The ETRM metadata documents three callable units (two named procedures/functions, with the third being the package body entry). These are described below; parameter lists are deliberately not reproduced because the metadata does not expose them.

• COLLECT_CCI_DATA — The principal data collection routine. It queries the interaction history tables and inserts or updates the collected interaction records used by Customer Intelligence. It is the procedure normally scheduled or called to populate the CCI data set for a given run.
• COLLATE_CALLS — A supporting routine that aggregates or consolidates call interaction records. Given the presence of JTF_IH_MEDIA_ITEMS and JTF_IH_MEDIA_ITEM_LC_SEGS among the dependencies, this routine is understood to collect call-level interaction data, including media item locale segments and locale segment types, and to hand the consolidated result to the collection logic.
• Package body — The implementation container for COLLECT_CCI_DATA and COLLATE_CALLS. It is listed as a subobject and is not in itself a callable procedure.

Tables Accessed

The package is documented as referencing five application tables through APPS synonyms. In all cases the access is read-oriented, with the collection logic producing BIX output rows rather than modifying the source IH tables.

• BIX_INTERACTIONS — The Customer Intelligence interaction table; the primary store into which collected interaction data is loaded or refreshed.
• JTF_IH_INTERACTIONS — The Interaction History master table; the authoritative source of interaction header records.
• JTF_IH_MEDIA_ITEMS — Media item detail for interactions, including call and other media records used to build the collected rows.
• JTF_IH_MEDIA_ITEM_LC_SEGS — Locale-specific media item segments, supplying localized detail that accompanies a media item.
• JTF_IH_MEDIA_ITM_LC_SEG_TYS — Locale segment type definitions used to interpret the locale segment rows.

No dependencies on other APPS packages are documented; the package references only SYS.STANDARD and is itself referenced by no other package, confirming that it is a top-level entry point rather than a shared library routine.

Usage Notes

Because BIX_CCI_COLLECT is referenced by no other package, it is expected to be invoked directly — typically from a concurrent program, a scheduled request set, or the EBS scheduler that drives Customer Intelligence collection. A common pattern for this class of API is to call COLLECT_CCI_DATA for a defined date range, with COLLATE_CALLS used internally to prepare the call interaction set before the main collection step. Custom code may call the package through a thin APPS wrapper, and the object should generally be executed as the APPS user with the standard EBS initialization. Administrators should treat the package as delivery-owned: it is not a public extension API, so direct modifications are not supported and upgrades may replace the package body. Monitoring should focus on the volume of rows inserted into BIX_INTERACTIONS per run, since that is the observable output of the collection process.