Search Results per_security_profiles




Overview
Explore in AI Chat

Overview

The PER_SECURITY_PROFILES table is a core data object within the Oracle E-Business Suite Human Resources (HRMS) module. It serves as the master repository for security profile definitions. These profiles are a fundamental component of the Oracle HRMS security model, enabling administrators to restrict user access to specific HR records based on criteria such as organization, position, payroll, and geography. By assigning a security profile to a user or responsibility, the system ensures that individuals can only view and process data for employees, assignments, and positions within their authorized purview, thereby enforcing data security and operational segregation.

Key Information Stored

The table stores the definitional header for each security profile. Its primary key is the system-generated SECURITY_PROFILE_ID. The unique key constraint on SECURITY_PROFILE_NAME and BUSINESS_GROUP_ID ensures profile names are unique within a business group. Critical foreign key columns define the profile's scope: BUSINESS_GROUP_ID anchors the profile, while ORGANIZATION_ID and POSITION_ID can specify a single organization or position for simple security models. For more complex, hierarchical security, the ORGANIZATION_STRUCTURE_ID and POSITION_STRUCTURE_ID columns reference the organizational and position hierarchies against which access rules are evaluated. The profile's name, description, and other control attributes are also stored in this table.

Common Use Cases and Queries

Primary use cases involve user security administration and audit reporting. Administrators create and maintain profiles via the "Security Profile" form, which writes to this table. Common technical queries include identifying all security profiles in a business group or finding profiles assigned to a specific user. For example:

  • Listing all security profiles: SELECT security_profile_id, security_profile_name, business_group_id FROM hr.per_security_profiles;
  • Finding profiles using a specific organization hierarchy: SELECT security_profile_name FROM hr.per_security_profiles WHERE organization_structure_id = <structure_id>;
  • Troubleshooting user access often involves joining PER_SECURITY_PROFILES with PER_SECURITY_USERS or PER_SEC_PROFILE_ASSIGNMENTS.

Reporting focuses on profiling security setup, mapping profiles to users, and ensuring correct business group alignment.

Related Objects

As the central definition table, PER_SECURITY_PROFILES has extensive relationships. It is referenced by numerous child tables that store the detailed components and assignments of each profile, including PER_SECURITY_ORGANIZATIONS, PER_SECURITY_USERS, PAY_SECURITY_PAYROLLS, and PER_SEC_PROFILE_ASSIGNMENTS. It is also linked to various "list" tables (e.g., PER_PERSON_LIST, PER_ASSIGNMENT_LIST, PER_ORGANIZATION_LIST) which cache the specific records a user can access for performance. Key foreign key relationships, as documented, link it to HR_ALL_ORGANIZATION_UNITS (for business group and organization), PER_ALL_POSITIONS, PER_ORGANIZATION_STRUCTURES, and PER_POSITION_STRUCTURES, defining its permissible scope of data.