Search Results per_assignment_list




Overview
Explore in AI Chat

Overview

The PER_ASSIGNMENT_LIST table is a core data security object within the Oracle E-Business Suite Human Resources (PER) module. It functions as a detailed access control list, explicitly defining the specific employee assignments that a user, governed by a particular security profile, is authorized to view and process. Its primary role is to enforce data-level security within HRMS, ensuring that users can only access personnel and assignment data for which they have been granted explicit permission. This table is populated and managed by the application's security infrastructure, typically during the generation or refresh of a security profile's access list, and is critical for the correct operation of secure HR reporting, self-service, and transactional forms.

Key Information Stored

The table stores a composite record that binds a user, a security rule, and a specific assignment. Its structure is defined by a three-column primary key, reflecting this relationship. The key columns are ASSIGNMENT_ID, which stores the unique identifier for an employee's assignment (from PER_ALL_ASSIGNMENTS_F); SECURITY_PROFILE_ID, which references the controlling security profile definition (from PER_SECURITY_PROFILES); and USER_ID, which identifies the application user (from FND_USER). Each row represents a single grant of access, permitting the specified user to view data for the given assignment under the authority of the linked security profile.

Common Use Cases and Queries

This table is predominantly used by the application's internal security engine to filter data. Common practical scenarios include the real-time filtering of employee lists in HR forms and the generation of secure reports. A typical query pattern involves joining PER_ASSIGNMENT_LIST to PER_ALL_ASSIGNMENTS_F and PER_ALL_PEOPLE_F to retrieve the list of employees and assignments a user is permitted to see. For example, to generate a secure list of employees for a specific user, a query would join on ASSIGNMENT_ID and filter by USER_ID and SECURITY_PROFILE_ID. This mechanism ensures that standard reports or data extracts automatically respect the complex security rules defined within HRMS, without requiring manual filtering in every query.

Related Objects

The table maintains defined foreign key relationships with other critical HR and application foundation objects. As per the provided metadata, the primary relationship is with the PER_SECURITY_PROFILES table via the SECURITY_PROFILE_ID column. This links the access list entries to the master security profile definition. While not explicitly listed in the provided excerpt, the ASSIGNMENT_ID column logically references PER_ALL_ASSIGNMENTS_F.ASSIGNMENT_ID, and USER_ID references FND_USER.USER_ID. The table is also intrinsically linked to the view PER_PEOPLE_SECURITY (and its underlying logic), which is a primary API for secure employee data access. Other objects, such as PER_ASSIGNMENT_SECURITY, may build upon or interact with the data stored in PER_ASSIGNMENT_LIST to enforce comprehensive data security.