Search Results set_time_stamp_dim_set




Overview

BSC_BIS_LOCKS_PUB is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified as a PUB (public) API within the Oracle Balanced Scorecard (BSC) product family. Its principal business function is to manage locking and time-stamp management for the metadata objects that underpin the Balanced Scorecard reporting infrastructure — datasets, datasources, dimension levels, dimension groups, dimension sets, measures, and KPIs.

In a multi-user EBS environment, several concurrent sessions may attempt to modify shared scorecard definitions. The package provides a coordinated locking mechanism and a standardized time-stamp utility so that changes to one metadata object can be detected and reconciled by other sessions. The header comment identifies the source file as BSCPLOCS.pls and the timestamp format constant C_TIME_STAMP_FORMAT as 'YY/MM/DD-HH24:MI:SS'.

Key Procedures and Functions

The package exposes both getter and setter routines and a set of locking procedures. Documented public members include:

Internally, the package declares t_numberTable, t_lock_Rec (fields obj_key1, obj_key2, obj_index, obj_Flag where flags denote Deleted, Added, or Changed), and t_lock_table, indexed by object identifier.

Tables Accessed

The package references several tables through APPS synonyms. BSC_SYS_DATASETS_B stores dataset definitions and their time stamps. BSC_SYS_MEASURES holds measure metadata. BSC_SYS_PERIODICITIES supports time-stamp calculation relative to scorecard periods. BSC_CURRENT_SESSIONS, ICX_SESSIONS, and V$SESSION are consulted to identify active sessions for lock ownership and conflict detection.

Usage Notes

BSC_BIS_LOCKS_PUB is invoked by the Balanced Scorecard administrative forms and concurrent programs when users create, update, or delete scorecard metadata, and it is referenced by 17 other packages. Custom code modifying BSC metadata should call the appropriate SET_TIME_STAMP_* and LOCK_* APIs rather than updating base tables directly. Note that the package source is dated 2005 and is marked "noship," indicating it is an internal supporting API rather than a formally supported extension point.