Search Results bix_calls_handled_bin_pkg




Overview
Explore in AI Chat

Overview

BIX_CALLS_HANDLED_BIN_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the Oracle Business Intelligence (BIX) family of database objects and is classified under the ETRM convention as an "OTHER" API type rather than a formal public API. The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the invoking session rather than the definer, a common pattern for internal EBS utility and data-transformation packages.

Functionally, the package supports the BIX interaction-center reporting and analytics model, specifically the aggregation of agent call activity statistics into the BIX data-mart staging structures and the population of "bin" (or bucket) definitions used to segment or rank those statistics. It is a data-population utility rather than a transactional business API; it does not create or update call records directly. Its header comment (115.6 2003/01/10) indicates the package body has been stable since the early 11i era and was carried forward unchanged into 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes a single documented procedure:

  • POPULATE — The principal entry point of the package. It accepts an optional context value (declared by default as NULL) that allows the caller to scope or qualify the population run, which is typical of concurrent-program-driven BIX utilities. Its purpose is to drive the aggregation and loading of call-handling data into the BIX data-mart tables: it consolidates agent-level call summary information and reflects it into the bin structures. No other subprograms are documented in the package specification, so all supporting logic resides in the package body and is not intended to be called directly.

Tables Accessed

The package operates against the following tables through APPS synonyms, as documented in ETRM metadata:

  • BIX_DM_AGENT_CALL_SUM — The agent-level call summary data-mart table; the primary source for the statistics being aggregated and binned.
  • BIX_DM_BIN — The bin (bucket) definition table, which supplies the classification boundaries into which aggregated call metrics are placed.
  • BIX_DM_GROUP_CALL_SUM — The group-level call summary data-mart table, providing aggregate figures for interaction groups.
  • JTF_RS_GROUPS_DENORM — The denormalized resource-group table from the JTF (Interaction Center) schema, used to resolve group membership and hierarchy for report grouping.
  • JTF_RS_GROUP_MEMBERS — The group membership table, used to associate individual resources with their teams.
  • JTF_RS_RESOURCE_EXTNS — The resource extension table holding descriptive attributes of agents and other resources.
  • DUAL — Used for simple scalar evaluation, consistent with standard PL/SQL practice.

The pattern of access indicates an ETL-style flow: read resource and group definitions from the JTF tables, summarize call activity, then write or refresh the BIX data-mart summary and bin tables.

Usage Notes

Because BIX_CALLS_HANDLED_BIN_PKG is classified as "OTHER" and is not referenced by any other package (zero inbound package dependencies per ETRM), it is not part of a documented inter-package call chain. In practice it is invoked in one of three ways:

  • As a concurrent program — The most common invocation. A BIX "Calls Handled Bin" or comparable data-mart refresh concurrent program calls POPULATE, passing a context parameter to scope the run.
  • From a scheduled or submitted request set — Data-mart population is ordinarily run on a recurring schedule after call activity has been captured, so that downstream interaction-center dashboards and analytics reflect current agent statistics.
  • From custom code — Since the specification is public and AUTHID CURRENT_USER, a custom PL/SQL block can call BIX_CALLS_HANDLED_BIN_PKG.POPULATE directly; the caller must possess the necessary DML privileges on the referenced BIX_DM and JTF_RS tables.

Support and customization notes: modifications to the package body should be avoided in favor of supported extensions, as it is delivered support code. Administrators should confirm that the referenced BIX_DM and JTF_RS tables are populated and that concurrent managers are active before diagnosing stale interaction-center bin reports, since a failure or skipped run of POPULATE will leave the bin structures unrefreshed.