Search Results bsc_kpi_properties




Overview

The BSC_KPI_PROPERTIES 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 repository for storing configurable attributes, or properties, associated with Key Performance Indicators (KPIs). This table functioned as a child entity to the main KPI definition table, enabling a flexible, extensible model where multiple discrete properties could be defined for a single indicator. Its role was to support the detailed configuration and behavioral metadata necessary for scorecard calculations, reporting, and display logic within the BSC application framework.

Key Information Stored

The table's structure centers on a composite primary key that uniquely identifies each property for a given KPI. The critical columns, as indicated by the metadata, are the INDICATOR and PROPERTY_CODE. The INDICATOR column is a foreign key linking the property to its parent KPI definition in the BSC_KPIS_B table. The PROPERTY_CODE column identifies the specific type of property being stored, such as a threshold value, a formatting rule, or a calculation parameter. While the specific data column for the property value is not detailed in the provided excerpt, a typical design would include a column (e.g., PROPERTY_VALUE or a similar variant) to hold the actual data for the code. This key-value pair design allows for dynamic extension of KPI characteristics without altering the core table structure.

Common Use Cases and Queries

Primary use cases involved the retrieval and management of KPI metadata for runtime scorecard rendering and administrative configuration. Common queries would join this table to the main KPI definition to fetch all properties for a specific indicator or a set of indicators. For example, a report generating a KPI configuration document might use a query such as: SELECT kpi.NAME, prop.PROPERTY_CODE, prop.PROPERTY_VALUE FROM BSC_KPIS_B kpi, BSC_KPI_PROPERTIES prop WHERE kpi.INDICATOR = prop.INDICATOR ORDER BY kpi.NAME, prop.PROPERTY_CODE;. Another typical scenario was querying for KPIs that possessed a specific property value, which was essential for filtering or applying business rules within the scorecard application logic.

Related Objects

The most significant related object is the BSC_KPIS_B table, which holds the base transactional data for KPI definitions. The relationship is enforced via a foreign key constraint where BSC_KPI_PROPERTIES.INDICATOR references BSC_KPIS_B. As a core entity within the obsolete BSC module, this table would have been referenced by various application forms, concurrent programs, and PL/SQL packages within the BSC schema responsible for scorecard calculation, publishing, and analytics. Given the module's obsolete status, direct integration with newer EBS functionalities or modules is unlikely, and the table exists primarily for historical data reference in upgraded environments.