Search Results bsc_user_list_access_u1

Overview

The BSC.BSC_USER_LIST_ACCESS table is a core data security object within the Oracle E-Business Suite (EBS) Balanced Scorecard (BSC) application. Its primary function is to manage user-level permissions for dimension list buttons, which are interface elements used to filter and navigate hierarchical data within BSC scorecards and strategy maps. By storing specific combinations of responsibility, tab, and dimension level, this table controls which users can access and interact with particular data subsets, enforcing a granular security model. It operates as a configuration table, with records typically created and maintained through the application's security administration interfaces rather than direct transactional user activity.

Key Information Stored

The table's structure centers on a unique composite key that defines a permission entry, supplemented by standard audit columns. The critical columns are:

• RESPONSIBILITY_ID: Links the permission to a specific EBS responsibility, which defines a user's functional role and menu access.
• TAB_ID: Identifies the specific BSC tab (or perspective) within the application interface where the dimension list is located.
• DIM_LEVEL_INDEX: Specifies the index of the dimension level within the hierarchy (e.g., Level 0 for Total, Level 1 for Division).
• DIM_LEVEL_VALUE: Holds the specific value at the designated dimension level to which access is granted (e.g., 'NORTH_AMERICA').
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN: Standard EBS "Who" columns for tracking record authorship and modifications.

The unique index BSC_USER_LIST_ACCESS_U1 enforces that no duplicate permission rules exist for the same combination of responsibility, tab, and dimension level.

Common Use Cases and Queries

A primary use case is auditing or troubleshooting user access issues, such as when a user reports being unable to see expected data in a scorecard list. An administrator can query this table to verify if the necessary permission records exist for the user's responsibility. Another common scenario is generating a security report to document all dimension-level permissions assigned across the BSC module.

Sample query to list all permissions for a specific responsibility (ID 20420):

SELECT RESPONSIBILITY_ID,
       TAB_ID,
       DIM_LEVEL_INDEX,
       DIM_LEVEL_VALUE,
       CREATED_BY,
       LAST_UPDATED_BY
FROM BSC.BSC_USER_LIST_ACCESS
WHERE RESPONSIBILITY_ID = 20420
ORDER BY TAB_ID, DIM_LEVEL_INDEX;

To identify which users (via their responsibilities) have access to a specific dimension value ('Q1') on a specific tab (ID 5):

SELECT DISTINCT lu.USER_NAME, fr.RESPONSIBILITY_NAME, ula.DIM_LEVEL_VALUE
FROM BSC.BSC_USER_LIST_ACCESS ula
JOIN FND_RESPONSIBILITY_VL fr ON fr.RESPONSIBILITY_ID = ula.RESPONSIBILITY_ID
JOIN FND_USER_RESP_GROUPS_DIRECT urg ON urg.RESPONSIBILITY_ID = fr.RESPONSIBILITY_ID
JOIN FND_USER lu ON lu.USER_ID = urg.USER_ID
WHERE ula.TAB_ID = 5
AND ula.DIM_LEVEL_VALUE = 'Q1'
AND SYSDATE BETWEEN urg.START_DATE AND NVL(urg.END_DATE, SYSDATE);

Related Objects

The table has defined relationships with other key BSC configuration objects, primarily through foreign key constraints.

• Primary Key: BSC_USER_LIST_ACCESS_PK on (DIM_LEVEL_INDEX, RESPONSIBILITY_ID, TAB_ID).
• Foreign Key (Reference): The TAB_ID column references BSC.BSC_TABS_B. This links each permission record to the specific BSC tab definition, ensuring referential integrity. The relationship is: BSC.BSC_USER_LIST_ACCESS.TAB_ID → BSC_TABS_B.
• Dependency: The table is referenced by a synonym, APPS.BSC_USER_LIST_ACCESS, which is the standard access point for all application code and most queries, insulating them from the underlying schema.