Search Results bsc_update




Overview
Explore in AI Chat

Overview

BSC_UPDATE is a core PL/SQL package in the APPS schema of Oracle E-Business Suite, belonging to the Oracle Balanced Scorecard (BSC) application. Its primary business function is to orchestrate the update, calculation, and recalculation of Key Performance Indicator (KPI) data within the Balanced Scorecard framework. The package acts as the central controller for the update process, managing the sequence of loading dimension tables, calculating system tables, applying periodicity calculations, executing year-change processing, and importing input tables from remote database sources.

The package is classified as OTHER in the ETRM repository and holds VALID status. It depends on BSC_UPDATE_UTIL and the SYS.STANDARD package, and is referenced by several other BSC packages, including BSC_MIGRATION, BSC_MO_LOADER_CONFIG_PKG, BSC_UPDATE_BASE_V2, BSC_UPDATE_INC, and BSC_UPDATE_LOCK. This dependency structure confirms that BSC_UPDATE is a foundational driver of the Balanced Scorecard update engine, invoked and extended by migration, incremental update, and locking utilities.

Key Procedures and Functions

The package exposes 54 documented procedures and functions. The following represent core capabilities documented in the ETRM metadata:

Tables Accessed

BSC_UPDATE references tables through APPS synonyms, spanning configuration, control, calendar, and KPI metadata domains:

Usage Notes

BSC_UPDATE is typically invoked from within the Balanced Scorecard update flow, most commonly through concurrent programs or from forms that launch KPI recalculation and year-change processing. Because BSC_UPDATE_BASE_V2, BSC_UPDATE_INC, BSC_UPDATE_LOCK, and BSC_MIGRATION reference this package, custom or extension code should route update logic through these dependent packages rather than calling BSC_UPDATE procedures directly, to preserve locking and incremental-update integrity. Direct invocation is appropriate for administrative tasks such as importing input tables from a remote database source or reinitializing environment values during troubleshooting. Administrators should monitor the BSC_DB_PROCESS_CONTROL and BSC_DB_PROCESS_ID_S tables to track process execution state.