Results for “bsc_kpi_dim_level_properti_u1”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BSC.BSC_KPI_DIM_LEVEL_PROPERTIES is a configuration table in the Oracle EBS Balanced Scorecard (BSC) schema that stores property metadata for dimension levels used within KPI definition. Each row describes how a specific dimension level behaves within a given dimension set for a specific indicator, governing display positioning, visibility, aggregation handling, and default key values. The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and is owned by the BSC schema. It is designated as FND Design Data, meaning it participates in the standard Oracle EBS patch and editioning infrastructure.

Heuristically, the mined foreign-key structure classifies this object as a link table. It resolves associations between dimension sets (via DIM_SET_ID) and dimension levels (via DIM_LEVEL_ID) in the context of an indicator, which is characteristic of a link construct connecting multiple hub-like entities. This classification is offered as a modeling suggestion rather than a documented architectural fact.

Key Information Stored

The table contains 13 documented columns. The primary key is defined by the constraint BSC_KPI_DIM_LEVEL_PROPERTI_PK, composed of DIM_LEVEL_ID, INDICATOR, and DIM_SET_ID. A unique index, BSC_KPI_DIM_LEVEL_PROPERTI_U1, enforces uniqueness on the same triplet, making INDICATOR, DIM_SET_ID, and DIM_LEVEL_ID the business-key candidate identifying each configuration row.

• INDICATOR — Numeric indicator code identifying the KPI to which the level property applies.
• DIM_SET_ID — Dimension set identifier, linking the row to a specific dimension set definition.
• DIM_LEVEL_ID — Dimension level identifier, linking the row to a specific level definition.
• POSITION — Controls display position; documented values are 0 = Normal, 1 = top-corner, and 2 = hide.
• TOTAL0 — Flags whether a code zero exists in the database for aggregation purposes.
• LEVEL_DISPLAY — Governs whether other dimension level indexes are disabled for display.
• DEFAULT_KEY_VALUE — VARCHAR2(400) column holding the default key value item; this is the column most directly associated with the search term “default_key_value” and stores the default member selection for the dimension level.
• USER_LEVEL0, USER_LEVEL1, USER_LEVEL2 — Visibility status flags for levels 0, 1, and 2 respectively.
• USER_LEVEL1_DEFAULT, USER_LEVEL2_DEFAULT — Default visibility status for levels 1 and 2.
• TARGET_LEVEL — Identifies the target level within the dimension hierarchy configuration.

Common Use Cases and Queries

Typical use cases involve auditing or reporting on how KPI dimensions are configured for display and default selection. Administrators and developers frequently query this table to determine the default key value applied to a dimension level, or to verify which levels are hidden or top-cornered within a scorecard. A representative query filtering on the searched column follows:

• SELECT INDICATOR, DIM_SET_ID, DIM_LEVEL_ID, DEFAULT_KEY_VALUE FROM BSC.BSC_KPI_DIM_LEVEL_PROPERTIES WHERE DEFAULT_KEY_VALUE IS NOT NULL;
• SELECT * FROM BSC.BSC_KPI_DIM_LEVEL_PROPERTIES WHERE INDICATOR = :p_indicator AND DIM_SET_ID = :p_dim_set_id;
• SELECT POSITION, LEVEL_DISPLAY, TARGET_LEVEL FROM BSC.BSC_KPI_DIM_LEVEL_PROPERTIES WHERE USER_LEVEL0 = 1;

These patterns support troubleshooting of scorecard rendering, validation of default dimension member behavior, and migration or comparison of configuration across environments.

Related Objects

The table maintains two documented foreign-key relationships and is referenced by application logic within the BSC schema.

• BSC.BSC_KPI_DIM_SETS_TL — Referenced via DIM_SET_ID; provides the translated dimension set definitions.
• BSC.BSC_SYS_DIM_LEVELS_B — Referenced via DIM_LEVEL_ID; provides the base dimension level definitions.
• APPS.BSC_KPI_DIM_LEVEL_PROPERTIES — The APPS synonym through which the table is commonly accessed by application code and reports.

Because the table is FND Design Data and carries no downstream database object references, its integration dependencies are expressed primarily through these parent lookups and through the BSC scoring engine that consumes the properties at runtime.