Search Results right_code




Overview
Explore in AI Chat

Overview

The IGW_ROLE_RIGHTS table is a core security and authorization object within the Oracle E-Business Suite Grants Proposal module (IGW). It functions as a junction table that defines the specific functional rights or permissions granted to a security role. This table is essential for implementing role-based access control (RBAC) within the Grants Proposal application, ensuring that users assigned to a particular role can only perform the actions and access the data explicitly permitted by that role's associated rights. It acts as the definitive mapping between abstract roles and the concrete application privileges they confer.

Key Information Stored

The table's structure is designed to enforce a many-to-many relationship between roles and rights through a composite primary key. The two critical columns are:

  • ROLE_ID: A foreign key column that references the IGW_ROLES table. This column stores the unique identifier for a security role defined within the Grants Proposal module.
  • RIGHT_CODE: This column stores a code that represents a specific functional right or permission within the application (e.g., CREATE_PROPOSAL, APPROVE_BUDGET, VIEW_CONFIDENTIAL_DATA). Together with ROLE_ID, it forms the table's primary key (IGW_ROLE_RIGHTS_PK), ensuring that a specific right can only be assigned to a given role once.
The combination of these columns answers the fundamental security question: "What can this role do?"

Common Use Cases and Queries

This table is central to security administration and access validation. A common administrative use case is querying all rights assigned to a specific role for audit or maintenance purposes. For example: 

SELECT right_code FROM igw.igw_role_rights WHERE role_id = 1001;
Conversely, identifying which roles possess a specific right is crucial for impact analysis before modifying a permission: 
SELECT r.role_name FROM igw.igw_roles r, igw.igw_role_rights rr WHERE r.role_id = rr.role_id AND rr.right_code = 'SUBMIT_PROPOSAL';
At runtime, the application logic will frequently join through this table to determine if a user's role permits a requested action. Reporting use cases include generating a complete matrix of role-to-right assignments for security compliance documentation.

Related Objects

The IGW_ROLE_RIGHTS table has a direct, documented relationship with the IGW_ROLES table, which stores the master definition of security roles (e.g., Proposal Manager, Budget Approver, Reviewer).

  • Foreign Key Relationship: The ROLE_ID column in IGW_ROLE_RIGHTS is a foreign key that references the IGW_ROLES table. This enforces referential integrity, ensuring that a right can only be associated with a valid, existing role.
This relationship is foundational. The IGW_ROLES table defines the "who" (the role entity), while the IGW_ROLE_RIGHTS table defines the "what" (the permissions). Any process or interface that manages role definitions or their associated privileges will inherently interact with both of these tables.