Search Results bix_dm_agent_call_sum

Overview

APPS.BIX_KPI_CLS_RPT_PKG is a PL/SQL package body that supports the Oracle E-Business Suite Business Intelligence (BIX) KPI reporting infrastructure. Its name reflects its role as a KPI Classification Report package within the BIX product family, which provides out-of-the-box key performance indicator dashboards and analytics for EBS operational data. The package is deployed in the APPS schema and holds a VALID status in the ETRM registry, confirming it is a compiled, active component of the BIX reporting layer.

Functionally, the package acts as a reporting helper that consolidates KPI classification output. It draws on pre-aggregated BI data mart content and publishes report-extract files, positioning it in the presentation/staging tier of the BIX architecture rather than in the transactional data-capture tier. The package depends on a small, focused set of objects, suggesting a narrowly scoped responsibility: reading summarized agent performance data, resolving reporting context such as currency and profile options, and emitting a flat-file report.

Key Procedures and Functions

The ETRM metadata documents a single program unit within the package body: POPULATE. Based on the documented dependencies and naming convention, POPULATE is the package's main driver. It orchestrates the report-generation cycle by reading KPI summary rows, applying the classification logic implied by the package name, and writing the resulting report output. The procedure's internal dependency on FND_PROFILE indicates it resolves session or site-level profile option values at runtime, and its dependency on FND_CURRENCY indicates that monetary KPI values are resolved against functional or reporting currency definitions before output. Because the metadata does not publish a parameter list, parameter details should be verified directly against the deployed package specification (BIX_KPI_CLS_RPT_PKG) in the APPS schema.

Tables Accessed

• BIX_DM_AGENT_CALL_SUM — The primary data source. This BI data mart table stores summarized agent call activity, and it is the object returned when searching for bix_dm_agent_call_sum. POPULATE reads these pre-aggregated rows to build the KPI classification report, avoiding the performance cost of querying transactional call-handling tables directly.
• BIX_DM_REPORT — The report-definition/metadata table used to resolve report configuration, such as output layout, report identifiers, or parameter context for the extract being produced.
• DUAL — The standard single-row utility table, used for expression evaluation, date/currency normalization, or seed-value selection within PL/SQL control flow.
• UTL_FILE — Not a table but the Oracle-supplied file I/O package, documented here alongside the SQL objects. Its presence confirms that POPULATE writes the finished report to a flat file on the database server, rather than returning rows to a client.

Additional documented dependencies include BIX_UTIL_PKG (shared BIX utility routines), FND_CURRENCY and FND_PROFILE (currency and profile option APIs), and the SYS STANDARD package. The package is not referenced by any other database object, confirming it is an entry-point component invoked directly rather than called from another package.

Usage Notes

BIX_KPI_CLS_RPT_PKG is not referenced by any other database object, so it is consumed either by a concurrent program, a scheduled batch job, or direct invocation from SQL*Plus or a custom wrapper. The combination of UTL_FILE output and BIX_DM_REPORT configuration strongly suggests concurrent-program deployment: an operator or scheduled request would execute POPULATE, which resolves profile options and currency, reads the agent call summary mart, and deposits a report file in a directory registered with UTL_FILE (subject to the UTL_FILE_DIR or DIRECTORY object and database-directory privileges).

The package is identical in behavior across Oracle EBS 12.1.1 and 12.2.2; no online-form dependency is documented. Administrators diagnosing output issues should verify the file-directory configuration, the FND_PROFILE reporting values, and the currency setup, since all three are runtime dependencies of POPULATE. Because the package is an APPS-owned, unsupported-by-API-standard reporting component, customizations should be confined to report configuration rather than to the package body itself, and the underlying package should be re-validated after any EBS patch that touches the BIX data mart tables.