Search Results grant_cond_num

Overview

The IGS_SC_GRANT_CONDS table is a core data structure within the Oracle E-Business Suite (EBS) Student System (IGS) modules. It functions as the repository for user-defined security grant conditions. These conditions are integral to the application's security model, defining the specific criteria under which a user or role is granted access to particular objects or data within the Student System. The table operates in conjunction with other security-related tables to enforce granular, rule-based access controls, ensuring that users can only interact with the system components and information for which they are explicitly authorized. Its role is critical for maintaining data security and compliance within the complex functional landscape of a higher education institution.

Key Information Stored

The table stores the logical components that constitute a security condition. Each record is uniquely identified by a composite primary key consisting of GRANT_ID and GRANT_COND_NUM. The GRANT_ID links the condition to a specific security grant definition. The GRANT_COND_NUM is a sequence number that orders multiple conditions within a single grant. Crucially, the table stores references to the specific attributes being evaluated through foreign key columns: OBJ_ATTRIB_ID points to a defined object attribute in the IGS_SC_OBJ_ATTRIBS table, and USER_ATTRIB_ID points to a user attribute. The condition logic itself (e.g., comparison operators and values) is typically stored in related columns or child tables, allowing the system to evaluate if a user's attribute satisfies the condition applied to the object attribute.

Common Use Cases and Queries

The primary use case is the runtime evaluation of user access permissions. When a user attempts to perform an action, the security engine queries the conditions stored in this table to determine if the associated grant is applicable. Administratively, it is used for auditing and maintaining security rules. A common reporting query would involve joining this table to its parent grant and related attribute tables to document the complete security model. For example, to list all conditions for a specific grant:

• SELECT grant_id, grant_cond_num, oa.attrib_name AS obj_attrib, ua.attrib_name AS user_attrib FROM igs_sc_grant_conds gc JOIN igs_sc_obj_attribs oa ON gc.obj_attrib_id = oa.obj_attrib_id JOIN igs_sc_user_attribs ua ON gc.user_attrib_id = ua.user_attrib_id WHERE grant_id = :p_grant_id ORDER BY grant_cond_num;

Troubleshooting access denials often involves tracing failed condition evaluations back to the specific rules stored here.

Related Objects

The IGS_SC_GRANT_CONDS table is centrally connected to other security definition tables via foreign key relationships. The documented dependencies are:

• Primary Key (IGS_SC_GRANT_CONDS_PK): The table is uniquely identified by the composite of GRANT_ID and GRANT_COND_NUM.
• Foreign Key to IGS_SC_OBJ_ATTRIBS: The OBJ_ATTRIB_ID column references the IGS_SC_OBJ_ATTRIBS table. This join defines the object-side attribute (e.g., "Student College," "Course Department") involved in the condition.
• Foreign Key to IGS_SC_USER_ATTRIBS: The USER_ATTRIB_ID column references the IGS_SC_USER_ATTRIBS table. This join defines the user-side attribute (e.g., "User Responsibility," "Person ID") that is evaluated against the object attribute.

Furthermore, IGS_SC_GRANT_CONDS is a child of a parent grant table (implied by GRANT_ID) which defines the overarching security privilege, and it is likely referenced by tables storing the condition's operator and comparison value.