Search Results bsc_apps_users_pk

Overview

The BSC_APPS_USERS table is a data object within the Oracle E-Business Suite (EBS) that belongs to the Balanced Scorecard (BSC) module, which is documented as obsolete. Its primary role was to serve as a junction or mapping table, linking application users to specific user definitions within the BSC module. This table was critical for managing user access and permissions within the Balanced Scorecard functionality, ensuring that only authorized application users could interact with BSC data and processes. The provided ETRM metadata explicitly states that this table is "Not implemented in this database," indicating it may have been part of a legacy design or a planned feature that was not deployed in standard EBS 12.1.1 or 12.2.2 instances, though its structure remains defined in the data dictionary.

Key Information Stored

The table's structure is centered on a single key column, as defined by its primary key constraint. The primary data element stored is the USER_ID. This column holds a numeric identifier that corresponds to a user within the broader Oracle EBS application framework (specifically, the FND_USER table, though not explicitly listed in the provided metadata). According to the documented foreign key relationship, this USER_ID in BSC_APPS_USERS references the USER_ID column in the BSC_USERS table. This design suggests BSC_APPS_USERS acted as a bridge, associating a generic EBS application user with a more specialized BSC user record that likely contained module-specific preferences or attributes.

Common Use Cases and Queries

Given the table's obsolete status and non-implementation note, direct operational use cases in active systems are unlikely. Historically, its purpose would have been to support user administration and security within the Balanced Scorecard. A system administrator might have queried it to audit which application users had been provisioned for BSC access. A typical join query to retrieve this mapping would have been:

• SELECT apps.user_id, bsc.user_name FROM bsc_apps_users apps, bsc_users bsc WHERE apps.user_id = bsc.user_id;

In a reporting context, it could have been used to filter BSC data (e.g., scorecards, initiatives) based on the currently logged-in application user by joining through this table to the BSC_USERS table and then to fact or transaction tables.

Related Objects

The table has a defined relationship with one other core BSC table, as per the provided metadata. Its primary key, BSC_APPS_USERS_PK, is defined on the USER_ID column. The documented foreign key shows that this table references the BSC_USERS table.

• BSC_USERS: This is the primary related table. The foreign key constraint defines that the BSC_APPS_USERS.USER_ID column references BSC_USERS.USER_ID. This establishes that every record in BSC_APPS_USERS must correspond to a valid record in the BSC_USERS table, enforcing referential integrity for user definitions within the obsolete module.