- In monitor job and in provisioning there is an entry for importing Job Relationship
- Non-authorized user was able to do Import Employee Data
SuccessFactors Employee Central: Import
Reproducing the Issue
In monitor job and in provisioning an entry for importing Job Relationship by user who is not authorized to access Import Employee Data.
These jobs are created internally as a background job on terminating a manager from UI, who has a large number of direct reports.
When a manager is terminated from UI, who has large number of direct reports, then background job will be created, which is "Employee Data Import Job" to update direct report's jobinfo and jobRelationship details.
If a logged in user has permission to perform any of these below actions, then as part of termination these jobs will be created (creator of this job will be the logged in user who does below actions):
- Permission to terminate a user
- Permission to approve workFlow
- Some Position related changes
- This is expected behavior. Since this background job name is similar to employee data import job name, it is difficult to differentiate whether these jobs are created from EmoployeeDataImport page or not.
- Our Engineering team will work towards changing the background job name to avoid confusion. However, this is an enhancement request and fixed release version is not confirmed.
Import Employee Data, unauthorized user import job, monitor jobs, audit Log for Job Relationship Import Job, Unknown imports sent to Monitor Job , KBA , LOD-SF-EC-EDP , Import Employee Data (EC Core only) , LOD-SF-EC-JOB , Job Information , Problem