Search Results grant_cond_num




Overview
Explore in AI Chat

Overview

The IGS_SC_GRANT_CONDS table is a core data repository within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the IGS (Internet Grant System) module. Its primary role is to store the detailed conditional logic associated with security grants. In the context of EBS security, a grant defines a user's permission to perform an action on a specific object. This table allows administrators to attach granular conditions to those grants, thereby implementing complex, attribute-based security rules. Each row in this table represents a single condition linked to a parent grant, enabling fine-grained access control beyond simple yes/no permissions.

Key Information Stored

The table's structure is designed to capture the components of a security condition. The mandatory GRANT_ID column links the condition to its parent security grant defined in the IGS_SC_GRANTS table. The GRANT_COND_NUM column, which was the focus of the user's search, is a sequence number (1-999) that orders multiple conditions within a single grant. The logic of the condition itself is defined by a combination of columns: OBJ_ATTRIB_ID (referencing an object attribute from IGS_SC_OBJ_ATTRIBS), USER_ATTRIB_ID (referencing a user attribute from IGS_SC_USR_ATTRIBS), a CONDITION operator (e.g., =, >, LIKE), and a TEXT_VALUE for comparison. Standard EBS "Who" columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) track audit information.

Common Use Cases and Queries

A primary use case is auditing and reporting on the conditional security landscape of the application. System administrators often query this table to understand complex access rules, troubleshoot permission issues, or document security configurations during compliance reviews. A typical query involves joining to the parent grant and attribute tables to translate IDs into meaningful names. For example, to list all conditions for a specific grant:

  • SELECT gc.GRANT_COND_NUM, oa.ATTRIBUTE_NAME AS OBJECT_ATTRIBUTE, ua.ATTRIBUTE_NAME AS USER_ATTRIBUTE, gc.CONDITION, gc.TEXT_VALUE FROM IGS_SC_GRANT_CONDS gc JOIN IGS_SC_GRANTS g ON gc.GRANT_ID = g.GRANT_ID LEFT JOIN IGS_SC_OBJ_ATTRIBS oa ON gc.OBJ_ATTRIB_ID = oa.OBJ_ATTRIB_ID LEFT JOIN IGS_SC_USR_ATTRIBS ua ON gc.USER_ATTRIB_ID = ua.USER_ATTRIB_ID WHERE g.GRANT_NAME = '<GRANT_NAME>' ORDER BY gc.GRANT_COND_NUM;

Another common pattern is identifying grants with conditions referencing a particular attribute, which is crucial for assessing the impact of attribute changes.

Related Objects

The IGS_SC_GRANT_CONDS table is central to the IGS security data model. Its relationships are defined through foreign key columns, though the provided metadata indicates no explicit referential integrity constraints are documented in the ETRM. Based on the column comments, the key related objects are:

  • IGS_SC_GRANTS: The parent table. The GRANT_ID in IGS_SC_GRANT_CONDS is generated from and references a record in IGS_SC_GRANTS.
  • IGS_SC_OBJ_ATTRIBS: The OBJ_ATTRIB_ID column references an object attribute identifier from this table.
  • IGS_SC_USR_ATTRIBS: The USER_ATTRIB_ID column references a user attribute identifier from this table.

The table is indexed by the unique primary key IGS_SC_GRANT_CONDS_PK on the combination of (GRANT_ID, GRANT_COND_NUM), ensuring no duplicate condition numbers exist for a given grant.