Search Results user_attrib_id

Overview

The IGS_SC_USR_ATTRIBS table is a data dictionary object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases, specifically belonging to the IGS (Student System) product family. Its core function is to serve as a master repository for defining security user attributes. These attributes act as configurable data points or categories that can be assigned to users within the system to control access or personalize functionality based on user-specific characteristics. Critically, the provided ETRM metadata explicitly labels the IGS - Student System module as "Obsolete," indicating this table is part of a legacy or deprecated code stream. Furthermore, the documentation states it is "Not implemented in this database," suggesting that while the table definition exists in the data dictionary, it may not be populated or actively used in a standard EBS implementation, potentially remaining as an artifact from an earlier version.

Key Information Stored

Based on the documented structure, the table is designed to store the metadata for each security attribute. The primary column is USER_ATTRIB_ID, which serves as the unique identifier (Primary Key: IGS_SC_USR_ATTRIBS_PK) for each attribute definition. While the ETRM excerpt does not list additional columns, tables of this nature in Oracle EBS typically contain columns to define the attribute's name (e.g., ATTRIBUTE_NAME or ATTRIBUTE_CODE), a description (DESCRIPTION), data type, and potentially status or enabled flags. The USER_ATTRIB_ID is the critical piece of information leveraged by related tables to link specific attribute values to their definitions.

Common Use Cases and Queries

Given its status as obsolete and not implemented, active operational or reporting use cases in a production EBS environment are unlikely. Its primary use would be for historical analysis, data migration auditing, or support during an upgrade from a very old version of the IGS product. Sample queries would focus on understanding the defined attribute framework. A basic investigative query would be: SELECT USER_ATTRIB_ID FROM APPS.IGS_SC_USR_ATTRIBS; to confirm if any records exist. To understand relationships, a join with the documented foreign key tables could be used: SELECT ua.USER_ATTRIB_ID, COUNT(pav.USER_ATTRIB_ID) FROM APPS.IGS_SC_USR_ATTRIBS ua LEFT JOIN APPS.IGS_SC_PER_ATTR_VALS pav ON ua.USER_ATTRIB_ID = pav.USER_ATTRIB_ID GROUP BY ua.USER_ATTRIB_ID; This would show which attribute definitions have values assigned in the related table.

Related Objects

The ETRM documentation specifies two key foreign key relationships, indicating this table is a parent to the following:

• IGS_SC_PER_ATTR_VALS: This table likely stores the actual personal attribute values assigned to specific persons or entities, linked via the USER_ATTRIB_ID column.
• IGS_SC_USR_ATT_VALS: This table likely stores the actual user attribute values assigned to specific system users, also linked via the USER_ATTRIB_ID column.

These relationships form a classic master-detail structure where IGS_SC_USR_ATTRIBS defines the "what" (the attribute), and the related tables store the "who" and the "value." All these objects share the "Obsolete" designation.