Search Results move_tab
Overview
BSC_SCORECARD_PVT is a private PL/SQL package in the Oracle EBS Balanced Scorecard (BSC) module, owned by the APPS schema. Its header carries the version string BSCVTABS.pls 120.0, and it serves as the internal implementation layer that supports the BSC Scorecard tabs framework. The package handles the persistence and lifecycle of scorecard tabs, tab-level indicator grouping, view configuration, and the grant/access infrastructure that controls which users may administer or view a given scorecard tab.
Because the package is classified as PVT (private), it is not intended for direct use by customers or third-party developers. Its public-facing counterparts are the corresponding entities and administration APIs in the BSC_SCORECARD_PUB package. BSC_SCORECARD_PVT is referenced by three other packages, consistent with its role as a dependent worker module invoked from higher-level scorecard administration routines and UI-driven flows. The package is documented under ETRM for both Oracle EBS 12.1.1 and 12.2.2, and the source header indicates a stable, long-standing interface (dated 2005, noship).
Key Procedures and Functions
The package exposes 16 documented procedures and functions. The core tab entity lifecycle is handled by CREATE_TAB, RETRIEVE_TAB, UPDATE_TAB, DELETE_TAB, and MOVE_TAB, providing standard insert, query, update, delete, and reordering operations on scorecard tab definitions. Administrative metadata refresh is performed by UPDATE_TAB_TIME_STAMP and UPDATE_SYSTEM_TIME_STAMP, which maintain audit and system-level timestamps on tab records.
Validation logic is provided by three routines: VALIDATE_TAB, VALIDATE_KPI_GROUP, and VALIDATE_KPI. These are the routines most relevant to the search term validate_kpi. VALIDATE_KPI checks a KPI definition for structural and referential correctness before it is persisted or associated with a tab, guarding against orphaned or malformed indicator references. VALIDATE_KPI_GROUP performs the equivalent check at the KPI-group level, ensuring group membership is coherent. VALIDATE_TAB validates the containing tab entity itself.
Access and security management is handled by CREATE_TAB_ACCESS, CREATE_TAB_GRANTS, INSERT_SCORECARD_GRANTS, REMOVE_SCORECARD_GRANTS, and REVOKE_GRANT. These routines synchronize the scorecard grant tables with the package constants BSC_ADMIN_ACCESS (BSC_SCORECARD_ADMINISTRATOR) and BSC_VIEWER_ACCESS (BSC_SCORECARD_USER), and with the grantee type and program-name constants (BSC_GRANTEE_TYPE, BSC_PROGRAM_NAME, BSC_OBJECT_NAME, BSC_INSTANCE_TYPE) used when registering FND grants. IS_MORE provides a cursor/utility check, typically used by callers iterating over result sets.
Tables Accessed
The package reads and writes the BSC tab core tables BSC_TABS_B and BSC_TABS_TL, which hold base and translated tab definitions. Tab indicator configuration flows through BSC_TAB_INDICATORS, BSC_TAB_IND_GROUPS_B, and BSC_TAB_IND_GROUPS_TL; these are the tables referenced by the VALIDATE_KPI and VALIDATE_KPI_GROUP routines. KPI master data is drawn from BSC_KPIS_TL.
View and layout configuration uses BSC_TAB_VIEWS_B, BSC_TAB_VIEWS_TL, and BSC_TAB_VIEW_LABELS_B. Scorecard "critical success factor" associations are stored in BSC_TAB_CSF_B and BSC_TAB_CSF_TL. Presentation assets and dimension metadata come from BSC_SYS_IMAGES, BSC_SYS_IMAGES_MAP_TL, BSC_SYS_COM_DIM_LEVELS, and BSC_SYS_INIT. All tables are accessed through APPS synonyms.
Usage Notes
BSC_SCORECARD_PVT is invoked indirectly through the Balanced Scorecard administrator forms and concurrent processes, and through the public BSC_SCORECARD_PUB API. It is not a supported integration point for custom development. Any custom code requiring scorecard-tab functionality should call the corresponding PUB procedure, which in turn delegates to this private package. Direct calls to VALIDATE_KPI or other routines carry upgrade risk, as the private interface may change without notice between EBS releases.