Search Results bsc_kpi_periodicities_user_pk

Overview

The BSC_KPI_PERIODICITIES_USER table is a core data object within the Oracle E-Business Suite Balanced Scorecard (BSC) module. It functions as a user-level customization table, storing specific periodicity preferences for Key Performance Indicators (KPIs). Its primary role is to enable personalized reporting and analysis by allowing individual users to define or override the default frequency (e.g., monthly, quarterly, annually) at which they wish to view or be notified about specific indicator data. This table is integral to the user-centric configuration of the performance management framework in Oracle EBS versions 12.1.1 and 12.2.2.

Key Information Stored

The table's structure centers on a composite primary key that uniquely identifies a user's periodicity setting for a given KPI. The critical columns are:

• INDICATOR: The identifier for the specific Key Performance Indicator.
• PERIODICITY_ID: The identifier for the selected reporting frequency or time period.
• USER_ID: The identifier for the BSC user who has defined this personal preference.

Together, these columns form the primary key (BSC_KPI_PERIODICITIES_USER_PK), ensuring that each combination of user, indicator, and periodicity is recorded only once.

Common Use Cases and Queries

A primary use case is generating a report of all personalized KPI periodicities for a specific user, often for audit or support purposes. Administrators may also query this table to identify which users have deviated from the system's default periodicity settings for critical indicators. A typical SQL pattern involves joining to the base periodicity and user tables for descriptive information:

SELECT u.USER_NAME, k.INDICATOR_NAME, p.PERIODICITY_NAME
FROM BSC_KPI_PERIODICITIES_USER pu,
BSC_USERS u,
BSC_KPI_PERIODICITIES k
WHERE pu.USER_ID = u.USER_ID
AND pu.INDICATOR = k.INDICATOR
AND pu.PERIODICITY_ID = k.PERIODICITY_ID
ORDER BY u.USER_NAME;

Another common operation is inserting or updating a user's preference, which directly manipulates this table based on user actions in the BSC application interface.

Related Objects

The BSC_KPI_PERIODICITIES_USER table maintains defined foreign key relationships with two fundamental BSC tables, ensuring referential integrity:

• BSC_USERS: The USER_ID column in BSC_KPI_PERIODICITIES_USER references the BSC_USERS table. This validates that the periodicity preference is associated with a valid application user.
• BSC_KPI_PERIODICITIES: The composite foreign key (INDICATOR, PERIODICITY_ID) references the BSC_KPI_PERIODICITIES table. This ensures that the user-selected indicator and periodicity combination exists as a valid configuration in the system's master data.

These relationships position BSC_KPI_PERIODICITIES_USER as a junction table that personalizes the core link between indicators and their reporting frequencies established in the BSC_KPI_PERIODICITIES table.