Search Results get_detail_page_function




Overview

APPS.BIV_DBI_TMPL_UTIL is a utility package within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environment that supports the Oracle Business Intelligence (BI) reporting infrastructure, specifically the Service Intelligence (BIV) module. The package is classified under the UTIL API classification, indicating it is a helper library rather than a public business API. Its primary responsibility is to centralize the constants, dynamic SQL builders, and parameter processing logic required by the BIV reporting template programs.

The package defines the canonical codes for the dimensionality model used in service analytics. Fields such as g_REQUEST_TYPE, g_CATEGORY, g_PRODUCT, g_SEVERITY, g_STATUS, g_CHANNEL, g_RESOLUTION, g_CUSTOMER, g_ASSIGNMENT, g_AGING, g_BACKLOG_TYPE, and g_RES_STATUS map service reporting concepts to their underlying source columns. These constants are consumed by the template engine to build the drill-down, aggregation, and trend logic. The header revision 120.0 dates the production version, and the package remains backward compatible across both 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents 23 procedures and functions. Notable members include:

Tables Accessed

The package references three APPS synonyms:

  • BIV_DBI_BACKLOG_AGE_DATES — provides the aging bucket boundaries used by the bucket query builders and the g_AGING dimension.
  • FND_LOOKUP_VALUES — supplies seeded lookup codes for status, severity, channel, and similar dimensions.
  • PLITBLM — used for parameter and bind-value handling within the template engine.

Usage Notes

BIV_DBI_TMPL_UTIL is not invoked directly by end users. It is called by the BIV intelligence templates and by five other packages that depend on its constants and SQL helpers. It loads into the BIV report page flow (BIS_PMV_PAGE_PARAMETER_TBL parameters) and is exercised when users run backlog, activity, closed, or backlog-age reports or drill into detail pages. Customizations should preserve the global constants, as report templates reference them by name.