Results for “text_value”

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

Overview

IGS_SC_GRANT_CONDS is a table in the IGS (Student System) schema of Oracle E-Business Suite, documented as VALID in both release 12.1.1 and 12.2.2. It stores the conditions that qualify a security grant defined by the user. In the Oracle Student System security model, a grant typically authorizes a user or role to act upon a secured object, and the condition rows held here refine that authorization by attaching attribute-based predicates. Each record therefore represents one condition line belonging to a parent grant, evaluated against an object attribute and a user attribute drawn from the referenced attribute tables.

Heuristic Data Vault classification mined from the foreign key structure identifies this object as a link. In Data Vault modeling terms, that suggests treating IGS_SC_GRANT_CONDS as a relationship entity connecting a grant to object attributes and user attributes, rather than as a standalone hub or a descriptive satellite. The 11 documented columns and the composite primary key support that interpretation.

Key Information Stored

The table carries 11 documented columns. The most significant are:

• GRANT_ID — Identifies the parent security grant to which the condition belongs; part of the primary key and the principal join path back to the grant definition.
• GRANT_COND_NUM — The condition sequence number within a grant. This is the column users most often search for, since it appears in the primary key and is used for ordering and addressing individual conditions.
• OBJ_ATTRIB_ID — Foreign key to IGS_SC_OBJ_ATTRIBS, identifying the secured object attribute tested by the condition.
• USER_ATTRIB_ID — Foreign key to the user-attribute side of the model, identifying the user attribute compared against the object attribute.
• CONDITION — The operator or comparison logic applied between the object and user attributes.
• TEXT_VALUE — Literal value supplied for the condition where a textual operand is required.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle audit columns capturing insert and update accountability.

The surrogate-style composite primary key, IGS_SC_GRANT_CONDS_PK, is defined on (GRANT_ID, GRANT_COND_NUM). It is also the only documented unique index, making both columns the business-key candidates for the row. Because GRANT_COND_NUM only carries meaning relative to its parent GRANT_ID, uniqueness is enforced at the pair level rather than on either column alone.

Common Use Cases and Queries

Typical queries resolve the conditions attached to a grant, or list which grants reference a given attribute.

• Retrieve all conditions for a grant, ordered by sequence: SELECT grant_cond_num, obj_attrib_id, user_attrib_id, condition, text_value FROM igs_sc_grant_conds WHERE grant_id = :grant_id ORDER BY grant_cond_num;
• Locate a specific condition line by number: SELECT * FROM igs_sc_grant_conds WHERE grant_id = :grant_id AND grant_cond_num = :n;
• Impact analysis when an object attribute changes: SELECT grant_id, grant_cond_num FROM igs_sc_grant_conds WHERE obj_attrib_id = :obj_attrib_id;
• Reporting on recently maintained conditions using the audit columns filtered by last_update_date.

Related Objects

• IGS_SC_OBJ_ATTRIBS — joined on IGS_SC_GRANT_CONDS.OBJ_ATTRIB_ID; supplies the object attribute definition evaluated by each condition.
• Grant master table (parent of GRANT_ID) — joined on GRANT_ID to obtain grant-level context such as the owning user or role.
• User attribute reference — reached through USER_ATTRIB_ID to resolve the user-side operand.
• IGS_SC_GRANT_CONDS_PK — the primary key constraint/index that enforces (GRANT_ID, GRANT_COND_NUM) uniqueness.
• Security-extraction and personalization views or concurrent programs in the IGS security module that read condition rows when evaluating access.