Search Results bsc_scorecard_pvt




Overview
Explore in AI Chat

Overview

APPS.BSC_SCORECARD_PVT is the private implementation package body for the Oracle Balanced Scorecard module in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It operates as a PVT-classified package, meaning it is not intended for direct invocation by external consumers; instead, it supplies the underlying procedural logic that the public package APPS.BSC_SCORECARD_PUB exposes to forms, the HTML-based Scorecard user interface, and internal framework components. Its central business function is the maintenance of scorecard tabs — the configurable workspace objects that hold KPIs, indicator groups, dimensions, views, and CSF associations for a scorecard. The package also administers the grants and access records that determine which users and responsibilities may view or modify a given tab. Because it is a PVT package, its procedures carry no public API contract, and Oracle reserves the right to change their signatures between patch levels.

Key Procedures and Functions

The documented interface comprises sixteen procedures and functions:

  • CREATE_TAB — creates a new scorecard tab, populating the base tab row and its associated definition rows.
  • RETRIEVE_TAB — reads an existing tab definition and its related attributes for display or downstream processing.
  • UPDATE_TAB — modifies the attributes of an existing tab.
  • DELETE_TAB — removes a tab and its dependent configuration records.
  • CREATE_TAB_ACCESS — establishes access records permitting a user or responsibility to use a tab.
  • MOVE_TAB — repositions a tab within the scorecard ordering, supporting the UI's drag-and-place or sequence maintenance.
  • UPDATE_TAB_TIME_STAMP — refreshes the last-update timestamp on a tab record.
  • UPDATE_SYSTEM_TIME_STAMP — records a system-level timestamp, typically for cache-invalidation or synchronization purposes.
  • VALIDATE_TAB — performs integrity checks on a tab definition before it is persisted.
  • VALIDATE_KPI_GROUP — validates that an indicator group reference is legal and consistent within the tab context.
  • VALIDATE_KPI — validates an individual KPI reference against the tab definition.
  • REMOVE_SCORECARD_GRANTS — deletes grant records associated with a scorecard or tab.
  • INSERT_SCORECARD_GRANTS — inserts grant records for scorecard access.
  • CREATE_TAB_GRANTS — creates the grant set that governs tab visibility and privileges.
  • REVOKE_GRANT — revokes a previously issued grant.
  • IS_MORE — a helper predicate used to test whether additional records remain, supporting cursor-based paging.

Tables Accessed

The package reads and writes the core Balanced Scorecard tab model. BSC_TABS_B and BSC_TABS_TL hold the base and translated tab rows. BSC_TAB_VIEWS_B, BSC_TAB_VIEWS_TL, BSC_TAB_VIEW_LABELS_B, and BSC_TAB_VIEW_LABELS_TL define tab views and their labels. BSC_TAB_INDICATORS, BSC_TAB_IND_GROUPS_B, and BSC_TAB_IND_GROUPS_TL associate KPIs and indicator groups to tabs, with BSC_KPIS_TL resolving KPI names. BSC_TAB_CSF_B and BSC_TAB_CSF_TL link tabs to critical success factors. BSC_USER_TAB_ACCESS and the FND_GRANTS family (accessed through FND_GRANTS_PKG) store access and grant information. Supporting reads come from BSC_SYS_COM_DIM_LEVELS, BSC_SYS_IMAGES, BSC_SYS_IMAGES_MAP_TL, and BSC_SYS_INIT, while FND_GLOBAL, FND_LANGUAGES, FND_USER, and FND_RESPONSIBILITY supply session, language, and security context.

Usage Notes

BSC_SCORECARD_PVT is invoked indirectly. The Scorecard user interface, the custom-view and PMF wrappers (BSC_CUSTOM_VIEW_UI_WRAPPER, BSC_PMF_UI_WRAPPER), and the dimensionality helper BSC_DIMENSION_LEVELS_PVT call into this body through BSC_SCORECARD_PUB. It is also referenced by three other database packages within the BSC schema. Direct calls from custom code are discouraged: the package is classified PVT, has no published parameter contract, and depends on FND_MSG_PUB and FND_API exception conventions that assume an active EBS session. Customers extending the Scorecard should use the public wrapper or, where necessary, copy the logic rather than binding to this body, because Oracle may alter procedure signatures during upgrades between 12.1.1 and 12.2.2.