Search Results bsc_mo_helper_pkg




Overview
Explore in AI Chat

Overview

BSC_METADATA_OPTIMIZER_PKG is an internal PL/SQL package in the APPS schema belonging to the Oracle Balanced Scorecard (BSC) product family, the module that provides the performance-management and KPI dashboard framework within Oracle E-Business Suite 12.1.1 and 12.2.2. The package name reflects its purpose: the optimization and regeneration of the metadata that underpins the BSC data model. Balanced Scorecard definitions — KPIs, their input sources, and the database objects that materialize them — are stored in metadata tables and mapped into generated database structures. BSC_METADATA_OPTIMIZER_PKG coordinates the preparation, flagging, and rebuilding of that metadata so that downstream loaders and readers operate against a consistent, validated repository. It also handles reserved-function initialization and provides supporting utilities such as file-directory resolution and progress logging. The package is classified as an OTHER API rather than a public interface; it is intended for internal invocation by other BSC components, not for direct customer use. Its STATUS is VALID and it exposes seven documented procedures and functions.

Key Procedures and Functions

  • INITMVFLAGS — Initializes materialized-view or related metadata flags used to indicate that a BSC object requires regeneration or refresh. It establishes the baseline flag state before optimization work begins.
  • INITRESERVEDFUNCTIONS — Populates or resets the set of reserved functions recognized by the metadata optimizer, ensuring that system-reserved expressions are recognized and not overwritten during generated-metadata processing.
  • RUN_METADATA_OPTIMIZER — The primary entry point. It performs the end-to-end optimization of BSC metadata, orchestrating the flag initialization, object analysis, and regeneration logic required to bring the metadata repository into a consistent state.
  • DOCUMENTATION — A self-documentation routine that emits descriptive information about the package and its metadata structures, typically for diagnostics or administrator review.
  • GETUTLFILEDIR — Resolves and returns the operating-system directory used for UTL_FILE output generated by the optimizer, observing the applicable database directory or parameter settings.
  • LOGPROGRESS — Writes progress and status messages to the FND_LOG diagnostic framework during long-running optimization processing, supporting troubleshooting of metadata generation.
  • IS_TOTALLY_SHARED_OBJ — Determines whether a given metadata object is shared across more than one definition, so the optimizer can avoid regenerating objects whose definitions are common to multiple KPIs.

Tables Accessed

The package works through the APPS synonym layer and references BSC_DB_TABLES, which describes the database objects underlying BSC metadata; BSC_KPI_PROPERTIES, which holds KPI attribute and property definitions; the temporary working tables BSC_TMP_BIG_IN_COND and BSC_TMP_OPT_UI_KPIS, used to stage large IN-list conditions and UI-visible KPIs during optimization; FND_LANGUAGES for language-sensitive metadata; AD_DDL for DDL execution; and DUAL and PLITBLM for PL/SQL internal mechanics. Dynamic SQL is executed through DBMS_SQL, file output through UTL_FILE, and instance configuration is read from V$PARAMETER. Progress messages are recorded in FND_LOG, and the view BSC_KPIS_VL supplies validated KPI definitions. Native DBMS_SQL, UTL_FILE, and STANDARD dependencies confirm the package both builds and executes dynamic statements at runtime.

Usage Notes

BSC_METADATA_OPTIMIZER_PKG is a foundational internal dependency rather than an end-user API. It is referenced by twelve other BSC packages, including BSC_MO_HELPER_PKG, BSC_MO_DB_PKG, BSC_MO_DOC_PKG, BSC_MO_INDICATOR_PKG, BSC_MO_INPUT_TABLE_PKG, BSC_MO_LOADER_CONFIG_PKG, BSC_MO_UI_PKG, BSC_AW_READ, BSC_BSC_ADAPTER, BSC_DBGEN_BSC_READER, BSC_DBGEN_UTILS, and BSC_OLAP_MAIN, and it recurses into itself, confirming its role as a shared utility layer for the wider BSC metadata-optimizer (BSC_MO) subsystem. It is normally invoked indirectly, during KPI definition deployment, metadata regeneration, or administrative maintenance of the Balanced Scorecard repository, rather than from a form or concurrent program directly. Because it issues DDL and dynamic SQL, it requires elevated privileges and should never be modified or called from custom code; the user search term "bsc_mo_helper_pkg" points to the sibling helper package built on top of this one. Support and patching should be handled exclusively through Oracle-provided patches to preserve the integrity of the generated BSC metadata model.