Search Results bix_dm_agent_sum_s

Overview

BIX_DM_AGENT_CALL_SUMMARY_PKG is a PL/SQL package body owned by the APPS schema that forms part of the Oracle E-Business Suite Interaction Center / Telephony (BIX) and Marketing (AMS) analytics infrastructure. Its purpose is to collect, aggregate, and stage agent-level call activity summary data used for reporting on inbound and outbound telemarketing and telesales operations. In EBS 12.1.1 and 12.2.2 the package operates within the "BIX" product family, which supports call center intelligence, campaign execution, and agent performance dashboards.

The package consolidates raw interaction, activity, and campaign data into denormalized summary tables (BIX_DM_*), which are then consumed by Oracle Daily Business Intelligence or custom call center reporting. According to the ETRM metadata, the body is status VALID in the APPS schema and is classified as an "OTHER" API. It exposes a single documented entry point, COLLECT_CALLS_SUMMARY, and references a substantial set of AMS, JTF, AS, and BIX objects.

Key Procedures and Functions

The ETRM metadata documents one procedure for this package body: COLLECT_CALLS_SUMMARY. As the name implies, this procedure is responsible for gathering call summary data from the underlying interaction and activity sources and loading it into the BIX_DM summary tables. It is the orchestration routine that drives the aggregation logic of the package.

No procedure parameters are documented in the available ETRM excerpt; therefore, the exact signature cannot be stated here and should be verified against the actual package specification in the target environment. The remaining internal functions and private subprograms within the package body are not surfaced in the metadata and are considered implementation detail. They typically handle currency conversion, "who" column population, and row-by-row insertion into staging and summary tables, but these are not documented as public APIs.

Tables Accessed

The package reads from and writes to a wide range of tables, indicating an ETL-style role:

• BIX_DM_* summary and interface tables — BIX_DM_AGENT_SUM, BIX_DM_AGENT_SUM_S, BIX_DM_AGENT_OUTCOME_SUM, BIX_DM_AGENT_OUTCOME_SUM_S, BIX_DM_CALL_SUM, BIX_DM_CALL_SUM_S, BIX_DM_GROUP_SUM, BIX_DM_GROUP_SUM_S, BIX_DM_GROUP_OUTCOME_SUM, BIX_DM_GROUP_OUTCOME_SUM_S, BIX_DM_COLLECT_LOG, BIX_DM_COLLECT_LOG_S, BIX_DM_CONNECT_LOOKUPS, BIX_DM_RESPONSE_LOOKUPS, BIX_DM_DNIS, BIX_DM_GOALS, BIX_DM_INTERFACE, and BIX_DM_APPS_DEPENDENCY. These are the primary targets of the collection process.
• Telephony / Interaction History tables — JTF_IH_INTERACTIONS, JTF_IH_ACTIVITIES, JTF_IH_MEDIA_ITEMS, JTF_IH_MEDIA_ITEM_LC_SEGS, and JTF_IH_MEDIA_ITM_LC_SEG_TYS provide the raw call and media interaction records.
• Marketing (AMS) tables — AMS_ACT_LISTS, AMS_CAMPAIGNS_ALL_B, AMS_CAMPAIGN_SCHEDULES, AMS_CAMPAIGN_SCHEDULES_VL, AMS_LIST_HEADERS_ALL, and AMS_SOURCE_CODES supply campaign, list, and source-code context.
• Leads and Resources — AS_LEADS_ALL, AS_SALES_LEADS, AS_STATUSES_VL, JTF_RS_GROUPS_DENORM, JTF_RS_GROUP_MEMBERS, and JTF_RS_RESOURCE_EXTNS tie summaries to agents, groups, and leads.
• Service and utility objects — CS_INCIDENTS_AUDIT_B, CCT_CLASSIFICATION_VALUES, IEC_G_LIST_SUBSETS, GL_CURRENCY_API, FND_FILE, FND_GLOBAL, and FND_PROFILE support incident linkage, classification, currency conversion, file output, and profile-driven behavior.

Usage Notes

Because the package is not referenced by any other database object per the ETRM metadata, it is invoked as a top-level entry point rather than as a dependency of another package. It is most commonly executed from a concurrent program or a scheduled batch job that runs the call summary collection on a nightly or periodic basis. Administrators may schedule COLLECT_CALLS_SUMMARY through the standard concurrent manager, and its output typically includes log rows written to BIX_DM_COLLECT_LOG.

Given the presence of FND_FILE and FND_GLOBAL references, the procedure is expected to run in a concurrent-program context where request IDs and output files are available. Custom code invoking this package should ensure that the APPS schema is the runtime user and that all BIX_DM summary tables are appropriately initialized. Direct column updates to the summary tables are discouraged; the package should be treated as the authoritative loader.