Search Results bsc_update_lock




Overview
Explore in AI Chat

Overview

BSC_UPDATE_LOCK is a PL/SQL package owned by the APPS schema that functions as the concurrency-control layer for the Oracle Balanced Scorecard (BSC) update infrastructure in Oracle E-Business Suite 12.1.1 and 12.2.2. Its sole architectural purpose is to serialize access to shared BSC configuration and data objects, preventing two concurrent sessions from simultaneously modifying scorecard metadata such as indicators, dimensions, calendars, and materialized views. Rather than implementing its own locking algorithm, the package wraps the Oracle-supplied DBMS_LOCK facility, providing a domain-specific API that BSC processing components call before performing write-intensive operations.

The package is classified as OTHER in ETRM and is marked VALID in the documented 12.1.1 release. It is a well-connected node in the BSC dependency graph: it invokes helper logic in BSC_UPDATE_UTIL and the SYS.STANDARD package, and is itself referenced by BSC_UPDATE, BSC_UPDATE_DIM, BSC_UPDATE_INC, and recursively by BSC_UPDATE_LOCK. This dependency profile confirms that the package sits beneath the main BSC refresh and incremental-update drivers, which acquire locks through it before touching indicators or summary objects.

Key Procedures and Functions

ETRM documents 29 callable units, all named with a LOCK_ prefix, grouped by the resource they protect:

Tables Accessed

Through APPS synonyms the package reads BSC_KPIS_B, BSC_SYS_DIM_LEVELS_B, and BSC_SYS_DIM_LEVEL_RELS to resolve indicator and dimension-level identities when deriving lock handles. BSC_KPI_DATA_TABLES, BSC_DB_TABLES, BSC_DB_TABLES_RELS, BSC_SYS_CALENDARS_B, and BSC_SYS_PERIODICITIES supply the mapping between logical BSC objects and their physical storage or calendar context. DBMS_LOCK is the operative system dependency where the actual lock allocation occurs.

Usage Notes

BSC_UPDATE_LOCK is not end-user facing. It is invoked programmatically by BSC_UPDATE, BSC_UPDATE_DIM, and BSC_UPDATE_INC, typically from concurrent programs and internal refresh routines rather than from Oracle Forms. Custom code that modifies BSC indicator, dimension, or calendar metadata should acquire the corresponding lock first to avoid corrupting an in-flight refresh; locks should be released in the same session that acquired them.