Search Results bsc_users




Overview
Explore in AI Chat

Overview

The BSC_USERS table is a core repository for user information within the Oracle E-Business Suite Balanced Scorecard (BSC) application. It functions as the primary user master table for the BSC module, storing a distinct list of users who are authorized to access and interact with Balanced Scorecard functionalities. Its role is central to user administration, security, and personalization within the BSC environment, serving as the parent record for a wide array of user-specific configurations and transactional data. The table's integrity is enforced by the primary key BSC_USERS_PK on the USER_ID column, making it the authoritative source for user identification within the BSC schema.

Key Information Stored

While the provided metadata does not list specific column definitions beyond the primary key, the table's description and its extensive foreign key relationships indicate its critical structure. The central column is USER_ID, which uniquely identifies each BSC user. Based on standard application patterns and the related tables, it is reasonable to infer the table likely stores fundamental user attributes. These may include the user's login name, display name, email address, active status indicator, and creation metadata (created by, creation date). The USER_ID serves as the foreign key link to numerous child tables that store user-centric preferences, responsibilities, and analytical settings.

Common Use Cases and Queries

This table is essential for administrative reporting, audit trails, and troubleshooting user access within the Balanced Scorecard. Common operational scenarios include generating a list of all active BSC users, identifying users associated with specific configurations, and validating user existence before assigning new responsibilities. A fundamental query retrieves all users, while more complex joins are used for analytical purposes. For instance, to list users along with their assigned responsibilities, one would join BSC_USERS to BSC_USER_RESPONSIBILITY. Similarly, investigating user-specific KPI calculation overrides would involve joining BSC_USERS to BSC_KPI_CALCULATIONS_USER. A basic reporting pattern is:

  • SELECT user_id, user_name FROM bsc.bsc_users WHERE enabled_flag = 'Y' ORDER BY user_name;

Data from this table is typically accessed via the BSC application's user administration interfaces, not via direct public APIs.

Related Objects

The BSC_USERS table has a foundational relationship with several key BSC tables, as documented by its foreign key constraints. The USER_ID column is referenced by the following tables, which store user-dependent data:

  • BSC_APPS_USERS: Links BSC users to specific applications.
  • BSC_KPI_ANALYSIS_OPT_USER: Stores user-level analysis options for Key Performance Indicators.
  • BSC_KPI_CALCULATIONS_USER: Holds user-specific calculation rules for KPIs.
  • BSC_KPI_DIM_LEVELS_USER: Contains user-defined dimension levels for KPIs.
  • BSC_KPI_PERIODICITIES_USER: Manages user-specific periodicity settings for KPIs.
  • BSC_KPI_SHELL_CMDS_USER: Stores user-level shell command preferences.
  • BSC_UI_COLOR_USER: Holds user interface color personalization settings.
  • BSC_USER_INFO: Likely contains supplemental profile information for the user.
  • BSC_USER_RESPONSIBILITY: Defines the responsibilities and associated security roles assigned to each BSC user.

These relationships underscore that BSC_USERS is the central hub for all user-centric data within the Balanced Scorecard module.