Search Results ro_oracle_id_access_flag

Overview

BSC.BSC_RESPONSIBILITY is a transactional data table in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments owned by the BSC schema. It stores the definition and configuration metadata for BSC responsibilities, including the responsibility identifier, the owning application identifier, the responsibility name, the underlying menu and request group assignments, and various security and web-access flags. In practice the table functions as the master definition source from which responsibility-level authorization is resolved at runtime for the BSC application stack.

From a Data Vault modeling perspective, the mined relationship metadata classifies this object as hub-leaning. The table can reasonably be modeled as a hub because it carries a single-column surrogate primary key (RESPONSIBILITY_ID) plus alternate business keys, and it is referenced by multiple downstream child tables rather than acting as a pure transactional satellite. The presence of the standard Who columns and descriptive attributes alongside the identity columns is consistent with a hub-and-satellite split, where identity lives in the hub and the descriptive fields would be separated into a satellite.

Key Information Stored

The table contains 25 documented columns. The most significant are:

• RESPONSIBILITY_ID — surrogate primary key (BSC_RESPONSIBILITY_PK), the internal identifier for the responsibility.
• APPLICATION_ID — application identifier owning the responsibility; combined with RESPONSIBILITY_ID it forms unique index BSC_RESPONSIBILITY_U1.
• RESPONSIBILITY_KEY — the responsibility key string; with APPLICATION_ID it forms unique index BSC_RESPONSIBILITY_U2, making both indexes business-key candidates.
• RESPONSIBILITY_NAME — the display name of the responsibility.
• MENU_ID and MENU_APPLICATION_ID — the menu and menu application assigned to the responsibility; MENU_ID carries a foreign key to FND_MENUS.
• FORM_ID and FORM_APPLICATION_ID — the form and form application bound to the responsibility.
• REQUEST_GROUP_ID and GROUP_APPLICATION_ID — the request group assignment controlling concurrent program access.
• DATA_GROUP_ID and DATA_GROUP_APPLICATION_ID — the data group assignment.
• RO_ORACLE_ID_ACCESS_FLAG — the read-only Oracle identifier access flag; a security control documented explicitly in the metadata and the column referenced by the user's search term.
• TERM_SECURITY_ENABLED_FLAG — indicates whether terminal-level security is enforced for the responsibility.
• START_DATE and END_DATE — the effective period for the responsibility definition.
• WEB_HOST_NAME and WEB_AGENT_NAME — web tier host and agent binding attributes.
• VERSION and DESCRIPTION — version tracking and free-text description.

Common Use Cases and Queries

Typical uses include responsibility security auditing, mapping responsibilities to menus and request groups, and reporting on the RO_ORACLE_ID_ACCESS_FLAG and TERM_SECURITY_ENABLED_FLAG settings to confirm that sensitive access is constrained. The following pattern retrieves responsibilities with their security flags for a given application:

• SELECT r.RESPONSIBILITY_ID, r.RESPONSIBILITY_KEY, r.RESPONSIBILITY_NAME, r.RO_ORACLE_ID_ACCESS_FLAG, r.TERM_SECURITY_ENABLED_FLAG FROM BSC.BSC_RESPONSIBILITY r WHERE r.APPLICATION_ID = :app_id;
• Joining MENU_ID to FND_MENUS resolves the menu name assigned to each responsibility.
• Filtering on START_DATE/END_DATE yields currently effective responsibilities.
• Grouping by APPLICATION_ID produces counts of responsibilities per application.

Related Objects

• BSC.BSC_RESPONSIBILITY_TL — references RESPONSIBILITY_ID; holds translated responsibility names.
• BSC.BSC_USER_RESPONSIBILITY — references RESPONSIBILITY_ID; links users to responsibilities.
• BSC.BSC_USER_TAB_ACCESS — references RESPONSIBILITY_ID; controls per-responsibility tab access.
• FND_MENUS — referenced via MENU_ID, defining the menu hierarchy behind the responsibility.
• FND_APPLICATION — the application master resolved through APPLICATION_ID, MENU_APPLICATION_ID, FORM_APPLICATION_ID, and GROUP_APPLICATION_ID.