Search Results bsc_tab_ind_groups_b




Overview
Explore in AI Chat

Overview

The BSC_TAB_IND_GROUPS_B table is a core data structure within the Oracle E-Business Suite Balanced Scorecard (BSC) module. It serves as the base table for storing the fundamental definition and assignment of indicator groups. In the Balanced Scorecard methodology, a Critical Success Factor (CSF) is decomposed into specific, measurable indicators. This table acts as the junction, defining which groups of these performance indicators (IND_GROUP_ID) are associated with a given CSF (CSF_ID) within a specific scorecard tab or perspective (TAB_ID). Its primary role is to maintain the structural integrity of the performance measurement framework by enforcing the relationships between these key entities, enabling the organization and hierarchical presentation of metrics for strategic analysis.

Key Information Stored

The table's design centers on a composite primary key that uniquely defines each indicator group assignment. The critical columns are CSF_ID, which references the Critical Success Factor; IND_GROUP_ID, which identifies the specific group of performance indicators; and TAB_ID, which denotes the scorecard perspective or tab containing the CSF. While the provided metadata does not list all columns, the structure implies these are the essential identifiers. The table likely contains additional audit columns such as CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and LAST_UPDATED_BY, which are standard in Oracle EBS base tables. The data stored here is primarily transactional and relational, forming the backbone for the navigational and reporting layers of the Balanced Scorecard.

Common Use Cases and Queries

This table is central to queries that list or report on the composition of a Balanced Scorecard. A common use case is generating a report of all indicator groups defined for a particular Critical Success Factor. Developers and system integrators may query this table to validate data configurations or during migration scripts. A typical SQL pattern involves joining to the translated table (BSC_TAB_IND_GROUPS_TL) to retrieve user-friendly names in a specific language.

SELECT bg.CSF_ID, bg.IND_GROUP_ID, bg.TAB_ID, tl.NAME
FROM BSC.BSC_TAB_IND_GROUPS_B bg,
     BSC.BSC_TAB_IND_GROUPS_TL tl
WHERE bg.CSF_ID = tl.CSF_ID
  AND bg.IND_GROUP_ID = tl.IND_GROUP_ID
  AND bg.TAB_ID = tl.TAB_ID
  AND tl.LANGUAGE = USERENV('LANG')
  AND bg.TAB_ID = :p_tab_id;

Another critical use case is integrity checking, ensuring every IND_GROUP_ID in this table has a corresponding translation record.

Related Objects

The table exists within a tightly defined schema with clear foreign key relationships, as documented in the ETRM metadata.

  • Referenced By (Parent Table): BSC_TAB_IND_GROUPS_B references BSC_TAB_CSF_B via the columns CSF_ID and TAB_ID. This enforces that an indicator group can only be assigned to a valid, existing Critical Success Factor within the correct tab.
  • Referenced By (Child Table): BSC_TAB_IND_GROUPS_TL (the translation table) references BSC_TAB_IND_GROUPS_B via its full primary key (CSF_ID, IND_GROUP_ID, TAB_ID). This relationship stores the multilingual names and descriptions for each indicator group.

These relationships highlight that BSC_TAB_IND_GROUPS_B is the master definition table, while BSC_TAB_IND_GROUPS_TL provides the locale-specific labels. Any customization or data load process must respect this hierarchy to maintain application integrity.