Search Results bsc_apps




Overview

APPS.BSC_APPS is a VALID package body in the APPS schema of Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Balanced Scorecard (BSC) product family, the module within Oracle EBS that provides scorecard, KPI, and strategy-management functionality. Functionally, BSC_APPS is best characterized as an internal infrastructure and utility library rather than a single business API: the ETRM record classifies its API classification as OTHER, and its documented procedure inventory consists almost entirely of helpers for dynamic DDL execution, tablespace and storage clause derivation, concurrent request submission and status checks, message and lookup retrieval, and property (profile-style) value management.

The package depends on the FND foundation layer (FND_API, FND_FILE, FND_GLOBAL, FND_MESSAGE, FND_MSG_PUB, FND_REQUEST, FND_CONCURRENT, FND_INSTALLATION, FND_ORACLE_USERID, FND_RESPONSIBILITY, FND_USER, FND_USER_RESP_GROUPS) together with the DDL and data-dictionary facilities AD_DDL through APPS, AD_TSPACE_UTIL, UTL_FILE, and the USER_/ALL_ dictionary views. It is referenced by 76 other database objects, confirming its role as a shared low-level dependency across the Balanced Scorecard schema components. It is not referenced by any higher-level object outside that set.

Key Procedures and Functions

Tables Accessed

The package reads and writes BSC_MESSAGE_LOGS (persisted message and error history) and references the FND security and identity tables FND_USER, FND_RESPONSIBILITY, FND_USER_RESP_GROUPS, FND_ORACLE_USERID, and PER_ALL_PEOPLE_F for user/responsibility and Oracle-schema identity resolution. DDL support objects include AD_DDL and the data-dictionary views ALL_TABLES, ALL_INDEXES, USER_TABLES, USER_INDEXES, USER_OBJECTS, USER_VIEWS, plus PLITBLM (large PL/SQL table storage), UTL_FILE (file generation), and V$PARAMETER (database parameter inspection).

Usage Notes

BSC_APPS is not intended for direct end-user invocation. It is called by Balanced Scorecard packages, concurrent programs, and internal setup/maintenance routines — any of the 76 dependent objects — to perform dynamic DDL, build IN-list predicates, resolve user context, log messages, and query concurrent request status. Customizations should call the harness APIs (for example, BSC_MESSAGE) rather than these internals, because the DDL and IN-list routines are implementation helpers whose behavior is tied to the installed schema and tablespace configuration.