Results for “bsc_responsibility_pk”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BSC_RESPONSIBILITY is a core configuration table within the Oracle Balanced Scorecard (BSC) product, owned by the BSC schema. It stores responsibility definitions used throughout the Balanced Scorecard application to govern user access, tab visibility, and menu assignments. In Oracle EBS 12.1.1 and 12.2.2, this table functions as the authoritative registry of responsibilities that can be assigned to Balanced Scorecard users, distinct from the native FND responsibilities used broadly across the E-Business Suite. Each row represents a single responsibility, complete with its associated application context, form, menu, request group, and security attributes.

From a Data Vault modeling perspective, the FK topology mined from the schema suggests a hub-leaning classification: RESPONSIBILITY_ID behaves as a durable business key around which several satellite and link tables cluster (BSC_RESPONSIBILITY_TL, BSC_USER_RESPONSIBILITY, BSC_USER_TAB_ACCESS). The table itself is relatively narrow in transactional churn and serves primarily as a reference/configuration entity.

Key Information Stored

Of the 25 documented columns, the following are the most operationally significant:

• RESPONSIBILITY_ID — the surrogate primary key defined by BSC_RESPONSIBILITY_PK. Uniquely identifies each responsibility record.
• APPLICATION_ID — the owning application context; participates in both unique indexes as a business-key component.
• RESPONSIBILITY_KEY — a business-key candidate (via BSC_RESPONSIBILITY_U2 combined with APPLICATION_ID).
• RESPONSIBILITY_NAME — the display name of the responsibility.
• MENU_ID / MENU_APPLICATION_ID — the menu attached to the responsibility; MENU_ID carries an FK to FND_MENUS.
• FORM_ID / FORM_APPLICATION_ID — the primary form invoked by the responsibility.
• DATA_GROUP_ID / DATA_GROUP_APPLICATION_ID — the data group governing data access scope.
• REQUEST_GROUP_ID / GROUP_APPLICATION_ID — the concurrent request group granted to the responsibility.
• START_DATE / END_DATE — effective dating for the responsibility's active period.
• RO_ORACLE_ID_ACCESS_FLAG / TERM_SECURITY_ENABLED_FLAG — security-related flags controlling access behavior.
• WEB_HOST_NAME / WEB_AGENT_NAME — web-tier routing attributes.
• DESCRIPTION — free-text description.
• Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and VERSION.

Two unique indexes are documented: BSC_RESPONSIBILITY_U1 (APPLICATION_ID, RESPONSIBILITY_ID) and BSC_RESPONSIBILITY_U2 (RESPONSIBILITY_KEY, APPLICATION_ID), confirming the composite business key.

Common Use Cases and Queries

Typical uses include auditing which responsibilities are assigned to which Balanced Scorecard users, reconciling menu/form/request-group configuration, and building access reports.

• Listing all responsibilities with their menus: SELECT responsibility_id, responsibility_name, menu_id, form_id FROM bsc_responsibility WHERE end_date IS NULL;
• Joining user assignments: SELECT r.responsibility_name, ur.user_id FROM bsc_responsibility r JOIN bsc_user_responsibility ur ON r.responsibility_id = ur.responsibility_id;
• Resolving translated names via BSC_RESPONSIBILITY_TL for multilingual reporting.
• Reconciling tab access by joining BSC_USER_TAB_ACCESS on RESPONSIBILITY_ID.
• Verifying menu integrity by joining MENU_ID to FND_MENUS.

Related Objects

• BSC_RESPONSIBILITY_TL — translation table joined on RESPONSIBILITY_ID.
• BSC_USER_RESPONSIBILITY — links responsibilities to users.
• BSC_USER_TAB_ACCESS — defines tab-level permissions per responsibility.
• FND_MENUS — referenced via the MENU_ID foreign key.
• Related configuration tables such as BSC_USER and BSC_USER_PREFERENCES manage the surrounding security and personalization data.