Results for “grant_name”

50+ results




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

Overview

IGS_SC_GRANTS_V is a self-service view belonging to the IGS product family (Student System), which is documented in Oracle E-Business Suite as obsolete. The view is catalogued in ETRM for both EBS 12.1.1 and 12.2.2, but the implementation notes explicitly record that it is not implemented in the database. It therefore serves as a reference definition rather than an active runtime object in a standard installation.

The view exposes grant definitions used by the self-service security model of the legacy Student System. A grant in this context binds a user group to an object group and specifies the permitted select, insert, update, and delete operations. Because the object is obsolete, it appears in reporting and integration discussions primarily when administrators audit historical IGS customizations, investigate orphaned views after an upgrade, or search on attributes such as LOCKED_FLAG while troubleshooting self-service access records.

Underlying Base Objects

The documented view text defines IGS_SC_GRANTS_V over two base objects joined on the user group identifier:

  • IGS_SC_GRANTS (aliased GR) — the primary table holding the grant identifier, grant name, LOCKED_FLAG, user group reference, object group reference, the four DML privilege flags, the function identifier, and audit columns.
  • WF_LOCAL_ROLES (aliased RL) — the Workflow local roles table, used to resolve the user group into a display name.

The join predicate is RL.ORIG_SYSTEM = 'IGS' and RL.ORIG_SYSTEM_ID = GR.USER_GROUP_ID, restricting role rows to the IGS originating system and matching them to the grant's user group. The select list includes a literal empty string in the position that populates FUNCTION_NAME, indicating that the function name is not resolved within this view definition. ETRM lists no separately documented referenced base objects for the view, so the two tables above constitute its definitional footprint.

Key Columns

Common Use Cases and Queries

Typical use is investigative rather than operational. A representative query identifies grants that have been locked for a given user group:

SELECT grant_id, grant_name, user_group_name, locked_flag
FROM igs_sc_grants_v
WHERE locked_flag = 'Y'
ORDER BY user_group_name, grant_name;

Another common pattern reviews the privilege profile across object groups:

SELECT grant_name, user_group_name, obj_group_id,
grant_select_flag, grant_insert_flag,
grant_update_flag, grant_delete_flag
FROM igs_sc_grants_v
WHERE grant_delete_flag = 'Y';

Because the view is not implemented in the documented database, these statements are valid only in environments where the underlying IGS objects still exist. In upgraded or current 12.2.2 instances the query will typically raise ORA-00942 (table or view does not exist), which is itself a useful confirmation that the obsolete Student System component has been removed.