Search Results per_security_users_pk




Overview
Explore in AI Chat

Overview

The PER_SECURITY_USERS table is a core data object within the Oracle E-Business Suite Human Resources (PER) module, specifically for versions 12.1.1 and 12.2.2. It functions as a junction table that defines the relationship between individual users and the security profiles assigned to them. Its primary role is to store the list of users for a given security profile, enabling the system to generate and maintain static lists of access permissions during the "Security List Maintenance" process. This process is critical for implementing data security and access control within HRMS, ensuring users can only view and modify data for the organizational structures, positions, or people defined by their assigned security profiles.

Key Information Stored

The table's structure is designed to map users to security profiles with minimal but essential attributes. The key columns are the surrogate primary key and the unique combination that defines the user-profile relationship. The SECURITY_USER_ID column serves as the unique primary key identifier for each record. The USER_ID column stores the unique identifier (typically from FND_USER) for the E-Business Suite user. The SECURITY_PROFILE_ID column holds the identifier for the security profile (from PER_SECURITY_PROFILES) to which the user is assigned. The unique key constraint on USER_ID and SECURITY_PROFILE_ID ensures a user cannot be assigned to the same security profile more than once.

Common Use Cases and Queries

A primary use case is auditing and reporting on user security assignments within HR. Administrators often need to generate lists of which users are assigned to specific security profiles or verify a user's assigned profiles. Common SQL queries include identifying all users for a given profile name and finding all security profiles assigned to a specific username. For example, to list users for a profile named 'US Managers', a typical query would join PER_SECURITY_USERS to PER_SECURITY_PROFILES and FND_USER. Another critical use case is during data fixes or security audits, where direct SQL may be used to insert or remove user assignments, though such operations should be performed with extreme caution and typically via the standard application interface.

Related Objects

The PER_SECURITY_USERS table has defined relationships with several key HR security objects. Its primary foreign key relationship is with the PER_SECURITY_PROFILES table via the SECURITY_PROFILE_ID column. This links each user assignment to the master definition of a security profile. While not listed in the provided metadata, the USER_ID column is logically a foreign key to the FND_USER.USER_ID column in the application's foundational user table. The table is central to the security list generation process and is referenced by various HRMS APIs and underlying security views that enforce data access. The primary key PER_SECURITY_USERS_PK and unique key PER_SECURITY_USERS_UK2 enforce data integrity for these relationships.