Search Results g_time_range




Overview
Explore in AI Chat

Overview

APPS.BIX_CALLS_TYPE_RPT_PKG is a reporting package in the Oracle E-Business Suite (BIX/Digital Business Intelligence) product family. Its name indicates that it produces a "Calls Type" report — a breakdown of interaction or telephony activities grouped by call classification — and writes the results into the temporary reporting table BIX_DM_REPORT for rendering by a BI/Reports front-end. The package body is stamped with $Header: bixxrctb.pls 115.16 2001/09/27, indicating a mature, relatively stable code line carrying through 12.1.1 and 12.2.2 in unchanged form.

The body declares a set of package-level globals that drive report behaviour: g_session_id, g_time_range, g_site_id, g_period_ind, g_from_date/g_to_date, g_from_time/g_to_time, g_sqlstmt, g_sysdate, g_classification_param, g_classification_parent, g_null_desc and g_nls_date_format. Together these hold the runtime report parameters and the dynamically assembled SQL text. The variable g_time_range is the pivot governing the report's granularity: when it equals 5 the report groups rows by date; otherwise rows are grouped by time. The value also decides which date/time display format (g_nls_date_format) is concatenated into the generated statement.

Key Procedures and Functions

  • POPULATE — the single documented entry point. It is the driver that accepts the report parameters (site, period, date/time window, classification scope), assigns them to the package globals, and populates BIX_DM_REPORT for the requested session. It also governs the internal flow used by the helper routine form_sqlstmt, which builds the INSERT ... SELECT statement into BIX_DM_REPORT.
  • form_sqlstmt (helper) — constructs g_sqlstmt, an INSERT with parallel hints into BIX_DM_REPORT, and emits either a "total row" or a "detail row" depending on the p_total_row_ind Boolean and the p_classification_id supplied. In detail mode it concatenates classification_id with period_start_date for sorting (col3), the period start date for display (col4), and classification description with the period start date for graphing (col5). The g_time_range global is tested here: value 5 produces date-based output; any other value produces time-based output.

Tables Accessed

  • BIX_DM_REPORT — the reporting staging/temp table. The package inserts one row per report cell (session_id, report_code, col1..col30), with the row shape determined by total-versus-detail mode. This is the primary write target.
  • BIX_DM_AGENT_CALL_SUM — the aggregated source of agent call activity by classification and period. It is read to supply the classification, period start date, and measure values inserted into BIX_DM_REPORT.
  • DUAL — referenced for scalar expressions and single-row computations that support the dynamic SQL generation.

Usage Notes

The package is invoked by the BIX Calls Type Report concurrent program or by the associated BI/Oracle Reports executable, which sets the report parameters and calls POPULATE for the current session. Because report output is written to BIX_DM_REPORT keyed on session_id and report_code, each run must supply a unique session identifier so that rows from concurrent runs do not collide.

The package is standalone: the ETRM metadata records no dependent packages referencing it, so customisations should call POPULATE directly rather than extend the private helper. Parameter values for g_time_range should be validated against the report's lookup before invocation, since the value 5 is treated as a special case. When adapting the package, note that the dynamic SQL embeds the NLS date format at runtime and uses parallel hints (degree 2) on both the source and target, which may warrant review on environments where parallel DML is restricted. No public parameters or exceptions are documented beyond the single POPULATE entry point, and the code is unchanged between 12.1.1 and 12.2.2.