Search Results isc_dbi_sutil_pkg




Overview
Explore in AI Chat

Overview

ISC_DBI_SUTIL_PKG is a shared utility package in the Oracle E-Business Suite APPS schema, belonging to the Supply Chain Intelligence (ISC) and Daily Business Intelligence (DBI) reporting product family. Its name derives from "ISC DBI S[upply Chain] UTIL[ity]," and it is the supplier-focused counterpart to similar DBI utility packages such as POA_DBI_UTIL_PKG, on which it depends. The package body is marked VALID and is classified as an OTHER API, indicating that it contains internal helper logic rather than a formally published or supported public interface.

The package supplies reusable string-formatting, rate-derivation, unit-of-measure resolution, and dashboard view-lookup routines that are called by the supplier performance and spend analytics dashboards. These dashboards are built on the BIS_PMV_PAGE_PARAMETER_TBL framework, which drives page parameter binding for DBI dashboard regions. The package does not own any business transaction data; instead, it transforms and resolves values so that dashboard queries can render correctly.

Key Procedures and Functions

  • PROCESS_PARAMETERS — Primary entry point that evaluates and processes dashboard page parameters, typically retrieving the parameter definitions from BIS_PMV_PAGE_PARAMETER_TBL and applying default or contextual values.
  • GET_VIEW_BY_COL_NAME and GET_VIEW_BY_SELECT_CLAUSE — Metadata helpers that resolve the database view name corresponding to either a column name or a SELECT clause, supporting dynamic dashboard region generation.
  • GET_FACT_SELECT_COLUMNS — Returns the fact-table columns required for a given dashboard query, supporting the fact/dimension model used in DBI star schema reporting.
  • RATE_STR, CHANGE_STR, CHANGE_RATE_STR, and POS_DENOM_PERCENT_STR — String-formatting functions that convert numeric rates, period-over-period changes, and percentage values into display-ready strings for dashboard presentation, including handling of percentage denominators.
  • GET_GLOBAL_WEIGHT_UOM, GET_GLOBAL_VOLUME_UOM, and GET_GLOBAL_DISTANCE_UOM — Functions that retrieve the site-level unit-of-measure preferences for weight, volume, and distance, allowing dashboards to render quantities and metrics in the unit defined for the operating environment.

Tables Accessed

The package reads from WSH_GLOBAL_PARAMETERS, the Shipping Execution global parameters table, to obtain the default weight, volume, and distance UOMs returned by the three UOM retrieval functions. It also references PLITBLM, the standard Oracle-supplied PL/SQL table of PL/SQL tables type used for passing collections of values in and out of procedure calls. Dashboard framework data is obtained from BIS_PMV_PAGE_PARAMETER_TBL, which holds the page parameter definitions consumed by PROCESS_PARAMETERS. All access is through APPS synonyms, and the package performs read-only lookup operations; no insert, update, or delete activity is documented.

Usage Notes

ISC_DBI_SUTIL_PKG is referenced by fifteen other database objects, but is not itself referenced by any external database object listed in the dependency metadata, confirming its role as a leaf-level utility layer. It is invoked indirectly whenever supplier-related DBI dashboard regions are rendered, most often from within DBI page processing routines that call PROCESS_PARAMETERS first and then use the UOM and formatting helpers to render metric values. The dependency on POA_DBI_UTIL_PKG indicates a common set of DBI utility functions shared across purchasing and supplier dashboards.

Because the package is classified as OTHER and its procedures are not documented as public APIs, custom development should not call these routines directly. The procedures are not guaranteed to remain backward compatible across releases, and their signatures are intended primarily for consumption by the seeded DBI dashboard framework. Developers extending supplier DBI dashboards should follow the supported DBI personalization and page parameter configuration mechanisms rather than invoking package components directly.