Search Results get_heading




Overview
Explore in AI Chat

Overview

BIX_CAMP_PERF_REPORT is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, shipped as part of the BIX (Business Intelligence) module lineage. It is declared with AUTHID CURRENT_USER, meaning that its SQL statements execute under the privileges of the invoking user rather than the package owner, an important characteristic for a reporting utility that must respect the caller's organization and security context. The package header carries a version marker from the 11i-era source file bixxrcps.pls, and the same object is documented for both release 12.1.1 and 12.2.2, where it remains classified under the generic API category (OTHER) in the ETRM repository.

Functionally, BIX_CAMP_PERF_REPORT underpins a campaign performance reporting capability — surfacing aggregated telemarketing or telesales activity at the campaign and agent level. It combines a data-population routine with a heading-retrieval function, following the common EBS reporting idiom in which a package both assembles a temporary result set and supplies the descriptive header text rendered above the report.

Key Procedures and Functions

The ETRM metadata documents exactly two callable components:

  • POPULATE — Accepts a single p_context argument and is responsible for assembling the report's working data set. Based on the referenced tables, it gathers campaign call activity into a JTFB temporary report structure, ready for consumption by a reporting engine, concurrent program, or form-based viewer. The p_context parameter allows the caller to pass run-time context (for example, the reporting period, organization, or user session) that the population logic uses to scope the extracted rows.
  • GET_HEADING — A parameterless function returning VARCHAR2 that supplies the display heading for the report. This is the element users most often search for, because it is the entry point referenced in report layouts and custom code that need the standardized title string rather than a hard-coded literal.

The record set held by POPULATE is transient by design; the package is intended to be invoked per reporting run rather than to maintain persistent state.

Tables Accessed

Per the documented dependency list, the package reads from the following objects via APPS synonyms:

  • BIX_DM_AGENT_CALL_SUM — a summary table holding per-agent call statistics, the primary source of the performance metrics reported.
  • BIX_DM_GROUP_CALL_SUM — a parallel summary table aggregating call statistics at the group or team level.
  • JTF_RS_GROUP_MEMBERS — the resource-group membership table, used to resolve which agents belong to which reporting group.
  • JTFB_TEMP_REPORT — a JTF temporary table used as the staging area into which POPULATE writes its assembled rows.
  • DUAL — the standard single-row dummy table, typically referenced by GET_HEADING to return a constant heading value or by validation logic inside POPULATE.

No insert, update, or delete activity against the source BIX_DM tables is documented; the package behaves as a read-and-stage utility.

Usage Notes

BIX_CAMP_PERF_REPORT is not a public integration API and is not referenced by any other documented package, confirming its role as an internal reporting worker. In practice it is invoked either from a concurrent program registered against the package and its POPULATE procedure, or directly from custom PL/SQL that first calls POPULATE, then reads JTFB_TEMP_REPORT for the result rows, and finally calls GET_HEADING to obtain the banner text. Because the package runs with AUTHID CURRENT_USER, permissions on the underlying BIX_DM summary tables and the JTFB temporary table must be granted to any invoking user or concurrent manager, and callers should ensure that the session context passed through p_context correctly constrains the data set. Customizations should avoid repositioning or altering the temporary table contract, since dependent report layouts expect the documented structure.