Search Results bsc_tab_views_b_pk

Overview

The BSC_TAB_VIEWS_B table is a core data object within the now-obsolete Balanced Scorecard (BSC) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It served as a master table for storing metadata that defined different "views" or perspectives within a tab of the Balanced Scorecard application. The Balanced Scorecard module was a strategic performance management tool, and this table was integral to organizing and presenting performance data across various customizable lenses, such as financial, customer, internal process, and learning & growth perspectives. Its role was to maintain the structural definition of these views, linking them to their parent tabs and enabling the modular display of scorecard information.

Key Information Stored

Based on the provided ETRM metadata, the table's structure centers on a composite primary key. The key columns are TAB_ID and TAB_VIEW_ID. The TAB_ID is a foreign key that links the view definition to a specific parent tab stored in the BSC_TABS_B table, establishing a hierarchical relationship. The TAB_VIEW_ID uniquely identifies a specific view configuration within that tab. While the full column list is not detailed in the excerpt, typical data stored would include attributes such as the view's display name, sequence or order within the tab, configuration flags controlling its behavior and visibility, and potentially references to underlying data sources or KPIs. The table's purpose is to catalog these view definitions rather than store the actual performance data displayed within them.

Common Use Cases and Queries

A primary use case involved administrative setup and reporting on the Balanced Scorecard's configuration. System administrators or implementers would query this table to understand the defined views across all tabs, often joining it with the parent BSC_TABS_B table. Common SQL patterns included listing all views for a specific tab or validating configuration integrity. For instance, a query to audit the view structure might be: SELECT tab.tab_name, view.tab_view_id, view.view_name FROM bsc_tab_views_b view, bsc_tabs_b tab WHERE view.tab_id = tab.tab_id ORDER BY tab.tab_id, view.sequence_num;. In operational use, the application would read from this table to dynamically render the available view selectors within the user interface. Reporting use cases often involved extracting this metadata to document the implemented scorecard framework.

Related Objects

• BSC_TABS_B: This is the primary related table, as defined by the foreign key constraint. BSC_TAB_VIEWS_B.TAB_ID references BSC_TABS_B, establishing that every tab view must belong to a defined tab.
• BSC_TAB_VIEWS_B_PK: The primary key constraint enforcing uniqueness on the combination of TAB_ID and TAB_VIEW_ID.
• Potential Child Tables: While not specified in the metadata, it is highly probable that other BSC tables (e.g., for view-specific KPI assignments or layout details) would have foreign keys referencing the BSC_TAB_VIEWS_B table to store configuration details for each specific view.

Critical Note: The ETRM explicitly states this table is "Not implemented in this database," indicating it may be a reference definition or that the BSC module itself is not installed. Furthermore, the BSC module is marked as "Obsolete," meaning this table is relevant primarily for maintaining, migrating, or decommissioning legacy implementations.