Search Results get_classifications




Overview
Explore in AI Chat

Overview

APPS.BIX_QUEUE_DETAIL_REPORT is a reporting package body in Oracle E-Business Suite that supports the BIX (Interaction Center / Telephony and Queue) reporting subsystem. Its primary business function is to populate the reporting staging table BIX_DM_REPORT with aggregated queue classification data so that the Interaction Center Queue Detail Report can be rendered for a given reporting period. The package consolidates call queue statistics held in BIX_DM_REAL_QUEUE_SUM and organizes them by classification, session, and time range, producing a denormalized result set consumed by the report layer.

The package body as documented spans Oracle EBS 12.1.1 and remains referenced in 12.2.2. The source header (bixxrqdb.pls 115.31, dated 2003) confirms this is a long-standing component of the Interaction Center reporting stack. Several package-level globals drive runtime behavior: G_TIME_RANGE, G_SESSION_ID, G_CLASSIFICATION_ID, G_CLASSIFICATION, G_NULL_DESC, and G_DRILLDOWN. These globals carry the session and filter context used across the package's internal procedures.

Key Procedures and Functions

The documented API surface consists of two procedures:

  • POPULATE — The main driver procedure. It accepts a context parameter and orchestrates population of the reporting table. Internally it invokes the private helper INSERT_TEMP_TABLE, which performs the actual data load into BIX_DM_REPORT. The helper first deletes prior data for the current session and report code, then determines the count of calls with no classification, and finally iterates over all valid classifications returned by the GET_CLASSIFICATIONS cursor to insert summary-level rows. The user's search for "insert_temp_table" corresponds directly to this documented internal routine; it is a private procedure inside the package body and is not exposed as a public API.
  • GET_HEADING — A procedure that returns or constructs the column heading text used by the report output. It supports the presentation layer by supplying the labels that align with the columns populated in BIX_DM_REPORT.

Per ETRM, the package is classified as OTHER and exposes no additional documented subprograms; internal constructs such as the GET_CLASSIFICATIONS cursor and INSERT_TEMP_TABLE are implementation details of POPULATE.

Tables Accessed

All tables are referenced through APPS synonyms:

  • BIX_DM_REPORT — The target staging/reporting table. Rows are deleted by session_id and report_code ('BIX_QUEUE_DETAIL_REPORT') before each run, and re-inserted with classification summary data.
  • BIX_DM_REAL_QUEUE_SUM — The source of call queue summary facts. It supplies the unclassified call count and, joined to classifications, the classified call rows.
  • CCT_CLASSIFICATIONS — Provides the classification identifiers and descriptive names used to group and label queue data. It is joined with BIX_DM_REAL_QUEUE_SUM to enumerate valid classifications.
  • DUAL — Used for scalar computations and single-row selects within the package logic.

Usage Notes

BIX_QUEUE_DETAIL_REPORT is invoked indirectly through the Interaction Center Queue Detail Report concurrent program or its reporting framework equivalent. The POPULATE procedure is called with a runtime context that sets the session identifiers and time range; INSERT_TEMP_TABLE then materializes the report rows in BIX_DM_REPORT keyed by the session. Because the delete-and-insert pattern is scoped by session_id and the fixed report code 'BIX_QUEUE_DETAIL_REPORT', concurrent runs with distinct session identifiers do not interfere. Custom extensions that search for "insert_temp_table" should note that this routine is private to the package body and cannot be called directly; any custom report should instead invoke POPULATE or read the staged results from BIX_DM_REPORT after the standard concurrent program completes.