Results for “igs_sc_obj_grants”

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

Overview

IGS_SC_OBJ_GRANTS is a table in the IGS (Student System) product schema of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores the information related to the grants and objects defined to be secured within the Student System security model. In practical terms, it is the association table that binds a security grant definition to a specific object registered in the applications dictionary, so that the grant can be applied to that object.

The documented physical schema in ETRM 12.1.1 records the table as owned by IGS with eight columns. The primary key is IGS_SC_OBJ_GRANTS_PK, defined over (GRANT_ID, OBJECT_ID). A unique index over the same pair also exists, and the metadata lists these business-key candidates in the reverse column order (OBJECT_ID, GRANT_ID); both orderings describe the same unique combination. From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is link. This table is therefore best understood as a many-to-many link between grants and securable objects rather than as a hub or a descriptive satellite.

Key Information Stored

The table is narrow and dominated by its two identifying foreign key columns. The most important columns are:

• GRANT_ID — Identifier of the grant being applied. This column participates in the composite primary key and is a foreign key to IGS_SC_GRANTS, which holds the grant definition itself.
• OBJECT_ID — Identifier of the object to be secured. This column participates in the composite primary key and is a foreign key to FND_OBJECTS.
• GRANT_WHERE — Additional predicate or restriction text associated with the grant for the object, allowing the scope of the grant to be qualified beyond the simple grant-to-object association.
• CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS WHO columns recording insert and update audit context.

There is no single-column surrogate key: the primary key is a composite of GRANT_ID and OBJECT_ID, and this same pair constitutes the documented business-key candidate through the unique index IGS_SC_OBJ_GRANTS_PK. Consumers should treat the GRANT_ID / OBJECT_ID pair as the natural identity of a row and expect at most one row per combination.

Common Use Cases and Queries

The dominant use case is determining which objects a given grant secures, and conversely which grants apply to a given object. This supports security administration inquiries, access reviews, and impact analysis before a grant is changed or retired.

• List all objects secured by a specific grant:

SELECT g.GRANT_ID, g.OBJECT_ID, g.GRANT_WHERE
FROM   IGS.IGS_SC_OBJ_GRANTS g
WHERE  g.GRANT_ID = :grant_id;

• Resolve the grant name and object name for reporting by joining to the referenced parents:

SELECT s.GRANT_NAME, o.OBJECT_NAME, og.GRANT_WHERE
FROM   IGS.IGS_SC_OBJ_GRANTS og,
       IGS.IGS_SC_GRANTS      s,
       FND_OBJECTS            o
WHERE  og.GRANT_ID  = s.GRANT_ID
AND    og.OBJECT_ID = o.OBJECT_ID;

• Audit trail queries using the WHO columns to identify recently modified grant-to-object mappings for a period.
• Reconciliation queries that identify objects carrying grants, or grants not yet assigned to any object, by driving from IGS_SC_GRANTS or FND_OBJECTS with an outer join back to this table.

Because the table is a link, most reporting queries are join-driven rather than single-table extracts, and care should be taken to filter on the composing keys to keep joins selective.

Related Objects

The documented foreign keys identify the two most significant related objects, and additional Student System security tables and dictionary views are commonly joined in practice:

• IGS_SC_GRANTS — Parent of GRANT_ID; holds the grant definition, name, and descriptive attributes used to compose user-facing security views.
• FND_OBJECTS — Parent of OBJECT_ID; the application dictionary table registering each securable object, supplying OBJECT_NAME and related metadata.
• IGS_SC_OBJ_GRANTS_PK — The primary key / unique index that enforces the composite uniqueness of GRANT_ID and OBJECT_ID and should back all equality-driven access paths.
• FND_GRANTS / FND_OBJECT_INSTANCES — Related dictionary objects frequently consulted when mapping IGS security definitions to the underlying Oracle EBS function and object layer.
• IGS security administration forms and concurrent programs — The maintenance and validation entry points that insert, update, and delete rows in this table.

Queries against IGS_SC_OBJ_GRANTS should always respect the dependent relationship to IGS_SC_GRANTS and FND_OBJECTS, since orphan handling for these two foreign keys determines the integrity of the overall Student System security configuration.