Results for “bsc_user_tab_access”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
BSC_USER_TAB_ACCESS is a transactional permission table in the Oracle E-Business Suite Balanced Scorecard (BSC) module, owned by the BSC schema. It defines which tabs of the Balanced Scorecard user interface are visible and accessible to a given responsibility. Each row maps a single responsibility to a single tab, effectively acting as an access-control intersection table that drives tab-level security and menu presentation for Scorecard users.
In Oracle EBS 12.1.1 and 12.2.2, the table is documented as VALID and contains nine columns. The heuristic Data Vault classification mined from its foreign key structure is link. Conceptually, this table behaves as a link/intersection entity: it resolves a many-to-many relationship between responsibilities and tabs, carrying no descriptive business attributes of its own beyond the association and its audit trail.
Key Information Stored
The table is deliberately narrow. The most significant columns are:
RESPONSIBILITY_ID— the responsibility for which tab permissions are granted; part of the composite primary key.TAB_ID— the tab being granted to the responsibility; the other half of the composite primary key.START_DATEandEND_DATE— effective dating controls that determine when the permission is active; important for date-tracked access reporting.CREATION_DATE,CREATED_BY— standard EBS who-columns capturing the initial insert.LAST_UPDATE_DATE,LAST_UPDATED_BY,LAST_UPDATE_LOGIN— standard EBS audit columns tracking the most recent change.
The surrogate/business key is the composite primary key BSC_USER_TAB_ACCESS_PK, defined over RESPONSIBILITY_ID and TAB_ID. A matching unique index, BSC_USER_TAB_ACCESS_U1, is documented on the same two columns, meaning the responsibility-plus-tab combination is the true business key candidate. No single-column surrogate is present; the intersection columns serve directly as the key.
Common Use Cases and Queries
Typical scenarios include auditing which Scorecard tabs a responsibility can see, troubleshooting tabs that fail to appear for users, and generating security matrices for compliance reviews. A common permission lookup:
- Join to
BSC_RESPONSIBILITYonRESPONSIBILITY_IDand toBSC_TABS_BonTAB_IDto translate IDs into responsibility and tab names. - Filter by
SYSDATE BETWEEN START_DATE AND NVL(END_DATE, SYSDATE)to return only currently effective permissions. - Group by
RESPONSIBILITY_IDand countTAB_IDto measure tab coverage per responsibility.
A representative query pattern selects RESPONSIBILITY_ID and TAB_ID from BSC_USER_TAB_ACCESS, joins to BSC_TABS_B for tab metadata, and applies the effective-dating predicate. Because the table is small and indexed on its key, such joins are inexpensive and suitable for embedded reporting or ad hoc DBA verification.
Related Objects
The following objects are the most significant references, based on the documented foreign keys:
BSC_RESPONSIBILITY— referenced byBSC_USER_TAB_ACCESS.RESPONSIBILITY_ID; the responsibility master driving access assignment.BSC_TABS_B— referenced byBSC_USER_TAB_ACCESS.TAB_ID; the base table defining available Scorecard tabs.BSC_TABS_TL— the translation table paired withBSC_TABS_Bfor tab display names.BSC_USER_TAB_ACCESS_PKandBSC_USER_TAB_ACCESS_U1— the primary key constraint and unique index enforcing the composite key.
Together these objects form the Scorecard tab-permission subsystem: BSC_TABS_B defines the tabs, BSC_RESPONSIBILITY defines the security context, and BSC_USER_TAB_ACCESS links them.
-
Tab permissions
-
Table: BSC_USER_TAB_ACCESS 12.2.2
Tab permissions
Not implemented in this database·Explore BSC module →
-
Table: BSC_RESPONSIBILITY 12.2.2
Responsibilities information
Not implemented in this database·Explore BSC module →
-
Table: BSC_TABS_B 12.2.2
Tabs information
Not implemented in this database·Explore BSC module →
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
PACKAGE: APPS.BSC_MIGRATION 12.1.1