Results for “igs_sc_usr_attribs”

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

Overview

IGS_SC_USR_ATTRIBS is a table within the Oracle E-Business Suite IGS — Student System product family, which is flagged as obsolete in the ETRM 12.1.1 / 12.2.2 documentation. The table stores information related to Security User Attributes — the definable attributes that participate in the Student System's user-level security model, governing how access to student records and related data is filtered based on the profile of the individual user.

In terms of Data Vault classification, the metadata's heuristic analysis describes this object as hub-leaning. From a modeling perspective, this is best understood as a hub: the table's primary key, USER_ATTRIB_ID, is a surrogate identifier for a distinct business concept (a security user attribute), and the table is the target of foreign keys from dependent tables, with no foreign key columns of its own documented. The object is not implemented in a standard Oracle EBS database, so it should be treated as a legacy or product-line-specific structure rather than a core EBS entity.

Key Information Stored

The documented physical schema contains 11 columns owned by the IGS schema. The most significant are:

• USER_ATTRIB_ID — the surrogate primary key, populated by the IGS_SC_USR_ATTRIBS_PK constraint and referenced by the dependent tables below. This is the column most often searched as user_attrib_id.
• USER_ATTRIB_NAME — the business name of the attribute. A unique index, IGS_SC_USR_ATTRIBS_UK, enforces uniqueness on this column, making it the natural business-key candidate alongside the surrogate key.
• USER_ATTRIB_TYPE — classifies the attribute for security evaluation logic.
• STATIC_TYPE — indicates whether the attribute is statically defined rather than resolved dynamically at runtime.
• SELECT_TEXT — stores the SQL text or selection expression associated with the attribute value resolution.
• ACTIVE_FLAG — the enablement indicator, used to include or exclude the attribute from security processing.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — capture the standard EBS WHO-column audit trail.

Common Use Cases and Queries

Access is primarily through the surrogate key or the unique business name. A typical lookup by the searched identifier is:

• Resolve an attribute definition: SELECT user_attrib_id, user_attrib_name, user_attrib_type, active_flag FROM igs_sc_usr_attribs WHERE user_attrib_id = :user_attrib_id;
• Look up by business key: SELECT * FROM igs_sc_usr_attribs WHERE user_attrib_name = :name; — served by IGS_SC_USR_ATTRIBS_UK.
• Report active attributes: SELECT user_attrib_id, user_attrib_name FROM igs_sc_usr_attribs WHERE active_flag = 'Y';
• Trace dependent values: join to the value and validation tables on user_attrib_id to reconstruct a complete attribute configuration for a security profile.

Reporting use cases center on auditing which security attributes exist, which are enabled, and how many dependent value records each attribute carries.

Related Objects

Two dependent tables carry USER_ATTRIB_ID as a foreign key into this hub:

• IGS_SC_PER_ATTR_VALS — holds per-person attribute values, joined via IGS_SC_PER_ATTR_VALS.USER_ATTRIB_ID = IGS_SC_USR_ATTRIBS.USER_ATTRIB_ID.
• IGS_SC_USR_ATT_VALS — holds user attribute values, joined via IGS_SC_USR_ATT_VALS.USER_ATTRIB_ID = IGS_SC_USR_ATTRIBS.USER_ATTRIB_ID.

These two satellites supply the actual values validated against the attribute definitions held in this table. Because the object is documented as not implemented in the standard database, verify its existence in the target instance before relying on it in custom code or reports.