Search Results user_attrib_name

Overview

The IGS.IGS_SC_USR_ATTRIBS table is a core repository for user-defined security attributes within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It functions as a master definition table, enabling the creation and management of custom attributes that can be used to control user access and personalize application security. This table is part of the IGS (iGovernment) schema, indicating its primary use in public sector or specialized industry verticals for implementing granular, attribute-based security models. Its role is to store the metadata and configuration for these security attributes, which can then be assigned to individual users to drive data visibility and functional permissions.

Key Information Stored

The table's structure is designed to define the attribute's characteristics and its data source. The primary columns include:

• USER_ATTRIB_ID: The unique numeric identifier for the attribute, populated from a sequence.
• USER_ATTRIB_NAME: A mandatory, unique name (up to 260 characters) assigned to the attribute by the implementer. This is the key field referenced in security configurations.
• USER_ATTRIB_TYPE and STATIC_TYPE: Define the nature of the attribute's value, such as whether it is static, dynamic, or derived from a lookup.
• SELECT_TEXT: A critical column holding a SQL query text string (up to 4000 characters). This query dynamically determines the list of valid values for the attribute at runtime, providing powerful flexibility.
• ACTIVE_FLAG: A flag used to mark attributes that are no longer in use, facilitating deactivation without deletion.
• Standard Who Columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN): Audit columns tracking the creation and modification history of each attribute record.

Common Use Cases and Queries

This table is central to configuring advanced security profiles. A common use case involves creating an attribute, such as 'SECURITY_ORGANIZATION', where the SELECT_TEXT column contains a query to fetch a list of operating units. This attribute can then be assigned to users, and subsequently leveraged in security profiles or personalized menu exclusions to restrict data access based on the user's assigned organization.

Key operational queries include retrieving all active attribute definitions or auditing recent changes. For example, to list all configured security attributes, the following query, as suggested by the ETRM, is used:

SELECT USER_ATTRIB_ID, USER_ATTRIB_NAME, USER_ATTRIB_TYPE, SELECT_TEXT, ACTIVE_FLAG FROM IGS.IGS_SC_USR_ATTRIBS WHERE NVL(ACTIVE_FLAG, 'Y') = 'Y' ORDER BY USER_ATTRIB_NAME;

To investigate dependencies or usage, one might query for attributes with specific text in their name or SELECT statement. Reporting typically focuses on the attribute definitions themselves rather than the data within them, as the actual attribute values for specific users are stored in related assignment tables.

Related Objects

While the provided dependency information shows no outward references from this table, it is explicitly referenced by objects within the APPS schema. This indicates that the defined attributes in IGS_SC_USR_ATTRIBS are consumed by application logic and security engines in the EBS core. The most direct related objects are typically user attribute assignment tables (which would store USER_ATTRIB_ID against a USER_ID), profile option setup tables, and security profile definition tables. These dependent objects use the USER_ATTRIB_ID and USER_ATTRIB_NAME as foreign keys to link security rules back to the master definitions stored in this table.