Search Results igs_sc_objects_n1

Overview

IGS.IGS_SC_OBJECTS is a seed-data table in the Oracle E-Business Suite IGS (Interactive Genetic/Student Systems) schema that stores the registry of application objects for which row-level security is to be enforced. Each row associates an Oracle Forms block, view, or database object with an object group and declares the specific DML privileges — select, insert, update, and delete — that the security engine is permitted to restrict. The table therefore functions as the configuration backbone for the Self-Service security framework, determining which entities are subject to fine-grained access control and under what conditions.

In Data Vault modeling terms, the heuristic classification supplied with the metadata suggests this object behaves as a link, resolving the many-to-many relationship between the FND_OBJECTS registry and IGS_SC_OBJ_GROUPS and carrying its own descriptive attributes (the DML flags and the parent-security enforcement flag). It resides in the APPS_TS_SEED tablespace, consistent with its role as a seeded configuration object rather than transactional data.

Key Information Stored

The table contains thirteen columns, of which the following are most operationally significant:

• OBJECT_ID — Surrogate identifier for the secured object, generated from FND_OBJECTS. Also the leading column of the unique index IGS_SC_OBJECTS_PK, making it the principal business-key candidate.
• OBJ_GROUP_ID — Identifier of the object group to which the object belongs, drawn from IGS_SC_OBJ_GROUPS. Participates in the composite primary key and is indexed non-uniquely via IGS_SC_OBJECTS_N1.
• SELECT_FLAG / INSERT_FLAG / UPDATE_FLAG / DELETE_FLAG — Per-operation indicators declaring whether the object is registered for security enforcement on the corresponding DML privilege.
• ENFORCE_PAR_SEC_FLAG — The column most directly relevant to the user's search. It identifies objects whose insert and delete privileges are contingent upon holding update privilege on the parent record, enabling hierarchical security inheritance.
• ACTIVE_FLAG — Marks objects that are no longer in use, allowing obsolete registrations to be retained without participating in runtime checks.
• CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who columns providing audit lineage for each registration.

Common Use Cases and Queries

Administrators and developers consult this table to audit which objects participate in security enforcement and to troubleshoot privilege anomalies. A typical diagnostic query lists all active objects with delete enforcement, with special attention to parent-security inheritance:

SELECT o.object_id, o.obj_group_id, o.update_flag, o.delete_flag,
       o.enforce_par_sec_flag
  FROM igs.igs_sc_objects o
 WHERE o.active_flag = 'Y'
   AND o.delete_flag = 'Y';

Reporting use cases include documenting the security posture of an implementation prior to upgrade, reconciling seeding differences between 12.1.1 and 12.2.2, and verifying that newly registered custom objects have the correct flag combinations. Because the table is seeded in APPS_TS_SEED, changes should be applied through supported setup paths rather than direct DML.

Related Objects

The following objects are most significant in relation to IGS_SC_OBJECTS, based on the documented foreign-key and dependency metadata:

• FND_OBJECTS — Referenced via IGS_SC_OBJECTS.OBJECT_ID; supplies the master definition of each registrable object.
• IGS_SC_OBJ_GROUPS — Referenced via IGS_SC_OBJECTS.OBJ_GROUP_ID; defines the grouping that drives security assignment.
• APPS.IGS_SC_OBJECTS — The APPS-layer synonym or view that exposes the table to application code and is listed as a downstream dependency.

The IGS_SC_OBJECTS_PK unique index on OBJECT_ID and the non-unique IGS_SC_OBJECTS_N1 index on OBJ_GROUP_ID both reside in APPS_TS_SEED and support the joins described above. The parent-privilege semantics expressed by ENFORCE_PAR_SEC_FLAG are interpreted at runtime by the IGS self-service security routines, which consume this registration data to construct the effective privilege set for a given user and object group.