Search Results deflt_update_sn_fm_cm




Overview

BSC_DESIGNER_PVT is a private PL/SQL package in the APPS schema that supports the Oracle Balanced Scorecard (BSC) Designer module within Oracle E-Business Suite. It encapsulates the backend logic used by the Scorecard Designer to build, copy, validate, and maintain Key Performance Indicator (KPI) definitions and their associated metadata. The package is a companion to the public-facing BSC designer entities and is not intended for direct invocation by external code; its procedures are consumed by other BSC packages (27 documented dependents) and by the BSC Designer forms and concurrent processes.

The code includes the header identifier BSCDSGS.pls 120.5, indicating its role in the KPI/indicator design subsystem. A large set of named constants (C_INDICATOR, C_KPI_TABLE, C_KPI_MEAS_TABLE, C_SOURCE_CODE, C_SYSTEM_TABLE, C_CAUSE_INDICATOR, C_EFFECT_INDICATOR, and numeric codes such as C_COLOR_CHANGE=7, C_MASTER_KPI=5, C_SHARED_KPI=3, and the C_SOURCE_TYPE_* values) reflects the internal classification of KPI source types and copy behaviors handled by the package.

Key Procedures and Functions

Tables Accessed

The package reads and writes a broad set of BSC dictionary tables via APPS synonyms, including BSC_KPIS_B (KPI definitions), BSC_KPI_DEFAULTS_B, BSC_KPI_CALCULATIONS, BSC_KPI_DATA_TABLES, BSC_KPI_DIM_GROUPS, BSC_KPI_DIM_LEVELS_B, BSC_KPI_ANALYSIS_GROUPS, BSC_KPI_ANALYSIS_MEASURES_B/_TL, BSC_KPI_ANALYSIS_OPTIONS_B/_TL, BSC_COLOR_RANGE_ID_S, BSC_COLOR_TYPE_PROPS, and BSC_INDICATOR_ID_S. ALL_DB_LINKS is referenced to support the g_DbLink_Name global used in distributed deployments. These tables hold the scorecard/indicator metadata that the DEFLT_* and DUPLICATE_* routines maintain.

Usage Notes

BSC_DESIGNER_PVT is a PVT (private) API; Oracle does not support direct customer calls. It is invoked indirectly through the Balanced Scorecard Designer forms and by other BSC packages that manage KPI design, duplication, and default refresh. Customizations should avoid hard-coding to this package because its interfaces may change between releases. The inclusion of FND_PROFILE_GET confirms the package relies on profile-driven behavior, so custom code that needs similar behavior should call FND_PROFILE.GET directly rather than this private package.