Search Results fnd_obj




Overview
Explore in AI Chat

Overview

APPS.IGS_SC_OBJECTS_V is a seeded Oracle E-Business Suite view belonging to the Oracle Student System (IGS) product family. It exposes the security object registration metadata that the Student System uses to control row-level and functional access to database entities. The view is named after the "SC" (Security) schema component and presents one row per registered database object that participates in the Student System's object-level security framework.

Functionally, the view joins the IGS security object definition table (IGS_SC_OBJECTS) to the Oracle Application Object Library object registry (FND_OBJECTS). This join supplies the human-readable object name and owning application identifier from FND_OBJECTS while retaining the Student System-specific security flags, primary key column definitions, and audit columns held in IGS_SC_OBJECTS. The view is therefore a convenience layer for reporting on and diagnosing the Student System security configuration rather than a data-entry object itself. In EBS 12.1.1 and 12.2.2 it is a read-only, query-only view exposing no DML of its own; changes to security object registrations are made through the underlying base tables and the Oracle Student System administrative forms.

Underlying Base Objects

The view is defined over two base objects, joined on OBJECT_ID:

The equality predicate on OBJECT_ID is the only documented join condition. Because FND_OBJECTS is an inner-joined base table, any IGS_SC_OBJECTS row whose OBJECT_ID is not registered in FND_OBJECTS will not appear in the view. The ETRM metadata lists no additional referenced base objects.

Key Columns

  • OBJ_GROUP_ID — groups related security objects together for collective grant or administration.
  • OBJECT_ID — the unique surrogate key shared with FND_OBJECTS; the join pivot of the view.
  • OBJ_NAME — the user-facing object name sourced from FND_OBJECTS.
  • APPLICATION_ID — the owning application identifier from FND_OBJECTS.
  • DATABASE_OBJECT_NAME — the physical database table or object being secured.
  • PK1_COLUMN_NAME … PK5_COLUMN_NAME and matching PK1_COLUMN_TYPE … PK5_COLUMN_TYPE — define up to five primary key columns and their data types, enabling the security engine to uniquely identify individual rows.
  • SELECT_FLAG, INSERT_FLAG, UPDATE_FLAG, DELETE_FLAG — indicate which DML operations the object security model governs.
  • ENFORCE_PAR_SEC_FLAG — signals whether parent security rules are inherited or enforced.
  • ACTIVE_FLAG — indicates whether the registration is currently in effect.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include auditing which Student System objects are security-enabled, verifying primary key metadata before troubleshooting row-level security failures, and reconciling IGS security registrations against FND_OBJECTS. A representative query listing active, security-enforced objects is:

  • SELECT OBJECT_ID, OBJ_NAME, DATABASE_OBJECT_NAME, SELECT_FLAG, INSERT_FLAG, UPDATE_FLAG, DELETE_FLAG FROM APPS.IGS_SC_OBJECTS_V WHERE ACTIVE_FLAG = 'Y' AND ENFORCE_PAR_SEC_FLAG = 'Y' ORDER BY APPLICATION_ID, OBJ_NAME;
  • Finding PK definitions: SELECT OBJ_NAME, PK1_COLUMN_NAME, PK2_COLUMN_NAME, PK3_COLUMN_NAME FROM APPS.IGS_SC_OBJECTS_V WHERE DATABASE_OBJECT_NAME = :table_name;
  • Group review: SELECT OBJ_GROUP_ID, COUNT(*) FROM APPS.IGS_SC_OBJECTS_V GROUP BY OBJ_GROUP_ID;

Filters on ACTIVE_FLAG and ENFORCE_PAR_SEC_FLAG are recommended because inactive or non-enforcing registrations are rarely relevant to production access analysis.