Results for “bsc_user_responsibility”

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

Overview

BSC_USER_RESPONSIBILITY is a child table in the Oracle E-Business Suite Balanced Scorecard (BSC) module, an application component that Oracle has since classified as obsolete. The table records the association between a Balanced Scorecard user and the responsibilities granted to that user, functioning as a cross-reference or intersection entity within the BSC security model. Its described purpose is simply "responsibility associated to user," which confirms its role as an assignment table rather than a master or transactional entity.

In Data Vault modeling terms, the metadata's heuristic classification of this object is link. This follows directly from its structure: a two-column, composite-primary-key table whose columns are both foreign keys to independent parent entities. A link table in Data Vault captures a many-to-many relationship between hubs, and BSC_USER_RESPONSIBILITY fits that pattern precisely, resolving the many-to-many cardinality between BSC users and BSC responsibilities. Practitioners designing a Data Vault representation of the EBS security domain should therefore model this as a link, with BSC_USERS and BSC_RESPONSIBILITY as the corresponding hubs.

Key Information Stored

The documented physical schema for release 12.1.1 lists an owner of BSC and only two columns, making this one of the most compact objects in the ETRM catalog. Because the table is a pure intersection, there is no surrogate single-column key and no descriptive attributes.

• RESPONSIBILITY_ID — identifies the responsibility being granted. This column forms one half of the composite primary key and carries a foreign key to BSC_RESPONSIBILITY.
• USER_ID — identifies the user to whom the responsibility is assigned. It forms the other half of the composite primary key and carries a foreign key to BSC_USERS.
• BSC_USER_RESPONSIBILITY_PK — the primary key constraint defined over (RESPONSIBILITY_ID, USER_ID). This is the constraint name users most commonly search for.
• BSC_USER_RESPONSIBILITY_U1 — a unique index over (USER_ID, RESPONSIBILITY_ID). This is the business-key candidate, enforcing that a given user-responsibility pairing appears only once, independent of the primary key's column ordering.

The distinction between the PK and the unique index is worth noting: both constrain the same column pair, but the PK leads with RESPONSIBILITY_ID while the unique index leads with USER_ID, giving the optimizer an efficient access path for lookups driven by either column.

Common Use Cases and Queries

The dominant use case is security auditing and reconciliation — answering which BSC responsibilities are held by which users, and vice versa. Typical query patterns include:

• Listing all responsibilities for a specific user: SELECT RESPONSIBILITY_ID FROM BSC_USER_RESPONSIBILITY WHERE USER_ID = :user_id;
• Listing all users holding a specific responsibility: SELECT USER_ID FROM BSC_USER_RESPONSIBILITY WHERE RESPONSIBILITY_ID = :resp_id;
• Detecting orphaned assignments by outer-joining to the parent tables, useful during migration or data-cleansing projects.
• Comparing the BSC-native responsibility model against the standard EBS FND_USER_RESPONSIBILITY model when assessing legacy or obsolete module usage.

Because the ETRM documentation states that this table is "Not implemented in this database," queries against it will only succeed in environments where the obsolete BSC schema was installed. Reporting solutions and customizations that reference it should be treated as legacy dependencies and validated carefully before upgrade.

Related Objects

The most significant related objects are the two parent tables referenced by the documented foreign keys, plus the surrounding BSC security and configuration entities:

• BSC_RESPONSIBILITY — parent of RESPONSIBILITY_ID; holds the responsibility definitions themselves.
• BSC_USERS — parent of USER_ID; holds the BSC user identities.
• Other BSC assignment and access tables that share the same user and responsibility dimensions.
• The standard EBS FND_USER and FND_RESPONSIBILITY tables, relevant when reconciling BSC assignments against core application security.
• Application programming interfaces and concurrent programs within the obsolete BSC module that create or maintain these assignments.

The two foreign keys define the object's structural dependencies unambiguously: BSC_USER_RESPONSIBILITY.RESPONSIBILITY_ID references BSC_RESPONSIBILITY, and BSC_USER_RESPONSIBILITY.USER_ID references BSC_USERS. Any join analysis, integrity check, or Data Vault link construction should proceed from these two relationships.