Symptom
This KBA explains how to grant permission to Employee Central HRIS elements before and after 1H 2025 release.
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Environment
- SAP SuccessFactors HXM Suite
- SAP SuccessFactors Employee Central
Resolution
Before 1H 2025 Release:
- Action Search: Manage Permission Roles
- Select the permission role
- Select the role. Click on Edit > Next
- In the User Permissions section, click Employee Central Import Entities
- Select as explained here: Role-Based Permissions for Additional Employee Central Import Entities
Role-based permissions for additional Employee Central entities are now available under Employee Central Import Entities.
The newly added Employee Central Import Entities are:- Biographical Information
- Personal Information
- National ID Information
- Addresses
- Phone Information
- Email Information
- Social Accounts Information
- Personal Documents Information
- Employment Details
- Global Assignment Details
- Person Relationship
- Termination Details
NOTE:
- If the user does not have "Enable RBP Access Validation for EC Elements during Imports (Do not enable during first time import)" checked in RBP (Manage Permission Roles > Role > Permission... > Administrator Permissions > Employee Central Import Settings), RBP validation will not occur during the import and the user will be able to import any entity.
-
To allow users to import employee data for selected entities, enable the Enable RBP Access Validation for EC Elements permission. If this permission is not enabled, you can still import the employee data but the permissions are not validated. This permission is applicable only for Job Information, Job Relationships and Compensation Information HRIS elements.
-
For existing permission roles that have the Import Employee Data permission from Employee Central Import Settings already enabled, the listed permissions are enabled by default in Employee Central Import Entities.
- For existing permission roles that don’t have the Import Employee Data permission from Employee Central Import Settings enabled, the listed permissions aren’t enabled by default. You must first enable Import Employee Data, and then enable Employee Central Import Entities to implement the newly added permissions.
- For newly created permission roles, you have to first enable Import Employee Data, and then enable Employee Central Import Entities to implement the newly added permissions.
After 1H 2025 Release:
- Action Search: Manage Permission Roles
- Select the permission role
- Select the role. Click on Edit > Next
- In the User Permissions section, click Employee Central Import Entities
- Select the entities under Import as explained here: Role-Based Permissions for Additional Employee Central Import Entities
- Biographical Information
- Personal Information
- National ID Information
- Addresses
- Phone Information
- Email Information
- Social Accounts Information
- Emergency Contacts
- Job Information
- Personal Documents Information
- Compensation Info
- Pay Component Non Recurring
- Employment Details
- Job Relationships
- Global Assignment Details
- Person Relationship
- Termination Details
Import permission for Compensation Info also controls the import of Recurring Pay Component for all import permissions. By default, these permissions will be displayed on Employee Central enabled instances only. - Select Target Population option for the entities as per your business requirement. This option allows you to import employee data with the selected Employee Central Import entities for the users within the target population.
NOTE:
- If the user does not have "Target Population" checked, RBP validation will not occur during the import and the user will be able to import for all user for the entities for which he/she has Import permission.
- You can configure import entities for the target population validation, except for the import of Person Relationships (Dependents)- related entities. The target population is validated when creating and updating the Person Relationships (Dependents) user and not validated when importing additional information for a particular dependent, such as an address or national ID.
- Do not enable the option during the first-time data import.
- The Target Population permission is dependent on the Import permission. So, the Import permission is verified first for all entities, followed by the Target Population permission. If the Import permission is not enabled for the entities, you cannot enable the Target Population option. Ensure you enable the Import permission to enable the Target Population permission.
- For existing permission roles that already have the permission "Enable RBP Access Validation for EC Elements during Imports (Do not enable during first time import)" granted, all entities for which Import permission is already configured, Target Population will also be granted. If the permission "Enable RBP Access Validation for EC Elements during Imports (Do not enable during first time import)" is not granted, no entity will have Target Population configured by default.
- The Target Population validation applies only to imports and doesn't support the OData API upsert.
FAQ - Additional Information
Q) Where can I get information on this from the Guide?
A) Guide - Chapter: Role-Based Permissions for Employee Data Import
See Also
- 2080082 - Basic Overview of Role Based Permissions in Employee Central
- 2434802 - Employee import - Please check RBP import configuration
- Role-Based Permissions for Employee Data Import
- WNV: Enhancements in Role-Based Permissions for Employee Central Import Entities
Keywords
Permission, RBP, Employee Central Import Entities, Job Relationships, Pay Component Non Recurring, Compensation Info, Job History, RBP, import, success factors, SF, EC, ECT-190253, ECT-247644, Target, b2505 , KBA , LOD-SF-EC-EDP , Import Employee Data (EC Core only) , How To