Search Results bix_summary_pub




Overview

BIX_SUMMARY_PUB is a public PL/SQL package in the APPS schema that belongs to the Oracle E-Business Suite Business Intelligence reporting infrastructure. Its name follows the standard EBS naming convention for public API packages: the BIX prefix identifies the Business Intelligence Extensions family, and the PUB suffix indicates that the package exposes callable entry points intended for use by other EBS components, concurrent programs, or customer extensions. In Oracle EBS 12.1.1 and 12.2.2, this package is primarily used to build and refresh the summary (aggregate) tables that underpin interaction and agent performance analytics.

The package is registered as VALID in the ETRM repository, indicating that it is compiled and present in the current installation. Its design is typical of EBS summary population utilities: a public package spec exposing a single documented entry point, with the implementation logic housed in the corresponding package body. This separation allows Oracle to modify internal logic without changing the published interface.

Key Procedures and Functions

  • POPULATE_BIX_SUM_X — The single documented procedure in this package. Its name follows the EBS convention in which the trailing X denotes a procedure that performs data population or processing rather than a value-returning function. Based on the package name and the tables it accesses, POPULATE_BIX_SUM_X populates the BIX summary tables, aggregating interaction-level data into agent-class and group-class summary records. It is the primary, and in this release the only, published entry point for summary generation in the BIX_SUMMARY_PUB interface.

No additional procedures or functions are documented in the ETRM metadata for this package. The exact parameter list is not published here; callers should verify the signature in the APPS package specification on their specific EBS release before invoking it. The package body additionally contains internal, non-public logic that supports the population process.

Tables Accessed

  • BIX_INTERACTIONS — The base interaction table. Summary population reads raw interaction records from this table as the source data from which aggregates are derived.
  • BIX_SUM_AGT_CLS and BIX_SUM_AGT_CLS_S — Agent-class summary table and its corresponding _S (sequence/snapshot) companion. POPULATE_BIX_SUM_X writes aggregated per-agent-class results here. The _S table typically stores the sequence-keyed version of the same aggregate, supporting the summary detail and its surrogate key relationship.
  • BIX_SUM_GRP_CLS and BIX_SUM_GRP_CLS_S — Group-class summary table and its _S companion, holding aggregates rolled up by group classification. These are populated in the same pass to provide a higher-level view of the same interaction data.

The package references these objects through APPS synonyms, per standard EBS practice. The dependency listing confirms only a minimal set of external references (SYS.STANDARD), which is consistent with a self-contained population routine.

Usage Notes

BIX_SUMMARY_PUB is not referenced by any other documented package in the ETRM repository, which indicates that it is invoked from outside the PL/SQL package layer. Typical invocation points include Business Intelligence concurrent programs that refresh interaction summaries on a scheduled basis, and custom or extension code that needs to force a rebuild of the BIX summary tables.

Because it is a PUB-classified API, the package is considered a supported interface for partner and customer code on both 12.1.1 and 12.2.2, provided callers use only the documented entry points. In 12.2.x, EBS Online Patching should be considered when scheduling summary population, since long-running summary jobs can hold resources that affect the cutover window. It is recommended that POPULATE_BIX_SUM_X be executed in a controlled concurrent-program context rather than interactively, and that input tables be validated for completeness before execution, as the procedure writes aggregate results into the BIX_SUM_* tables without a documented rollback mechanism.