Search Results bix_kpi_cls_rpt_pkg

Overview

The APPS.BIX_KPI_CLS_RPT_PKG package is a PL/SQL reporting utility that belongs to the Oracle EBS Business Intelligence (BIX) product family, specifically the component historically associated with Oracle's eBusiness Intelligence / Balanced Scorecard and KPI reporting infrastructure. The package header marker (bixxkcts.pls, version 115.2, dated 2003) places it in the early-2000s generation of BIX extract and reporting code that shipped with Oracle Applications releases and remains present in the 12.1.1 and 12.2.2 application schemas. Its declared purpose is to populate report-oriented data structures that support Key Performance Indicator (KPI) classification report output. The package is declared with AUTHID CURRENT_USER, meaning that at runtime its SQL statements execute with the privileges of the invoking schema rather than as the defining APPS owner; this is a deliberate design choice for packages that read from APPS data dictionary and AOL synonyms while writing intermediate output. It is classified in ETRM as an OTHER API, i.e., it is an internal implementation package rather than a published or supported PL/SQL interface. It exposes a single documented entry point and is not referenced by any other package in the ETRM metadata, indicating it sits at the leaf of the dependency chain and is invoked directly by a concurrent program, form, or report rather than by sibling code.

Key Procedures and Functions

• POPULATE — The sole documented procedure in the package. It accepts an optional p_context parameter defaulting to NULL. Its role is to gather and stage the KPI classification report data consumed by the corresponding BIX report. The p_context argument allows the caller to scope the population run, typically distinguishing one execution context from another (for example, a particular reporting instance or run identifier) so that successive invocations do not collide. Because the ETRM metadata documents no additional internal procedures, the bulk of the extraction, aggregation, and file-writing logic is contained within this single procedure.

Tables Accessed

Three APPS synonyms plus the UTL_FILE built-in are documented as referenced objects:

• BIX_DM_AGENT_CALL_SUM — A BIX data mart summary table holding agent call statistics. POPULATE reads aggregated call-summary rows from this table to build the KPI classification report content.
• BIX_DM_REPORT — A data mart table describing or storing report definitions and report-level attributes. It supplies the report metadata that frames the output produced by the procedure.
• DUAL — The standard Oracle single-row utility table, used for inline constant evaluation, sequence-less value derivation, or existence checks consistent with the package's 2003 vintage.
• UTL_FILE — The Oracle supplied file I/O package. Its presence indicates that POPULATE writes extracted report data to an operating-system file, a pattern typical of BIX/KPI report generation where data is staged to a flat file for downstream consumption.

Usage Notes

As an ETRM-classified OTHER package with no inbound package references, BIX_KPI_CLS_RPT_PKG is not intended for direct use by customer extensions. It is normally triggered by a BIX concurrent program or a scheduled reporting request registered in Oracle Applications Manager, and its file output depends on the target directory being registered in UTL_FILE_DIR (or an equivalent directory object in later releases) with appropriate privileges for the APPS schema. Because of the AUTHID CURRENT_USER declaration, any custom caller must hold the necessary privileges on the BIX data mart tables and on the file directory. The absence of documented internal helpers and the 2003 header date indicate that the package has been frozen for many years; it should be treated as legacy reporting plumbing rather than an extensible framework, and any customization should occur at the report or concurrent program level rather than by modifying the package body.