Search Results bim_utl_pkg




Overview
Explore in AI Chat

Overview

APPS.BIM_UTL_PKG is a utility package within the Oracle E-Business Suite Business Intelligence Management (BIM) module, which underpins the E-Business Intelligence / Daily Business Intelligence (DBI) functionality. As its name implies, the package provides shared, low-level infrastructure services that other BIM packages depend upon, rather than exposing end-user business transactions directly. In Oracle EBS 12.1.1 and 12.2.2 the package is validated and resides in the APPS schema, allowing it to be invoked interchangeably by concurrent programs, PL/SQL APIs, and other packages that resolve it through APPS synonyms.

The package consolidates three distinct responsibilities: physical index maintenance, currency conversion of aggregated fact values, and repository history logging. By centralising these operations, the BIM fact packages—such as BIM_LEAD_FACTS_PKG, BIM_LEAD_IMPORT_FACTS_PKG, and BIM_RESPONSE_FACTS_PKG—avoid duplicating boilerplate logic during ETL and refresh cycles. The ETRM metadata records four documented program units, a table reference list that spans both BIM repository tables and Oracle data dictionary views, and an inbound dependency set comprising four other APPS packages. The package itself depends only on SYS.STANDARD, confirming it is a foundational, comparatively self-contained component.

Key Procedures and Functions

  • DROP_INDEX — Removes an index associated with a BIM fact table. It is typically called before bulk data loads, where dropping and later recreating indexes reduces the overhead of maintaining them during high-volume inserts.
  • CREATE_INDEX — Rebuilds or creates the index dropped by DROP_INDEX, restoring query performance on the affected fact table after the load completes. Together these two procedures implement a drop-load-recreate pattern used by the BIM fact packages.
  • CONVERT_CURRENCY — Applies currency conversion to monetary fact measures so that aggregated results are expressed in a consistent reporting currency. This supports the multi-currency reporting requirements of DBI dashboards.
  • LOG_HISTORY — Writes an entry to the BIM repository history table, recording the outcome and timing of ETL or refresh activity. This provides auditability and supports operational monitoring of collection runs.

The metadata does not document parameter signatures; callers should consult the package specification in the EBS instance for exact argument lists.

Tables Accessed

  • BIM_REP_HISTORY — The repository history table written by LOG_HISTORY, capturing run records for BIM ETL processes.
  • BIM_ALL_INDEXES — A BIM-maintained catalogue of indexes, used to determine which indexes belong to the fact tables being managed.
  • ALL_INDEXES, ALL_IND_COLUMNS — Data dictionary views queried to validate existing indexes and their column definitions.
  • FND_PRODUCT_INSTALLATIONS, FND_APPLICATION, FND_ORACLE_USERID — Applications Object Library tables used for installation checks and to resolve the Oracle schema context in which objects are created or dropped.
  • DUAL — Used for scalar computations typical of PL/SQL utility logic.

Usage Notes

BIM_UTL_PKG is not normally invoked by end users through a form. Its principal consumers are the BIM fact packages that reference it: BIM_LEAD_FACTS_PKG, BIM_LEAD_IMPORT_FACTS_PKG, BIM_RESPONSE_FACTS_PKG, and BIM_SOURCE_CODE_PKG. These packages call the utility routines during collection and summarisation jobs, most commonly from concurrent programs scheduled by the DBI/BI administrator. Custom code that builds or extends BIM fact collection should reuse BIM_UTL_PKG rather than implementing its own index and logging logic, to remain consistent with concurrent index state and repository history. Because the package maintains physical database objects and writes to repository history, appropriate APPS-level privileges and adequate tablespace for index rebuilds are prerequisites for its use.