Symptom
How do I Terminate employees via Import?
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
What is the correct order to import Termination data?
The correct order is -:
- Termination Details
- Job Information (not needed - only if you need to update Job Info data)
What is the behaviour?
When you import Termination Details data, the system will create both Termination Details and the corresponding Job Information record with the Termination Date +1 day and the same Event Reason as was used in the Termination Details import. For event View 2617429 - Event Reason Availability and Configuration in Employee Central
Data Issues:
If data is imported in the wrong order (i.e. Job Information > Termination Details), the system will still create a new Job Info Termination record corresponding with the data in the Termination Details import. It will do it with sequence number = null - which results in the system determining the next sequence number and using that. For example -: If you import Job Info termination record first it will get seq-number "1". Then when you import Termination Details the system will create the Job Info record to corrspond with the Termination Details import, but as a Job Info record already exists on that date, the system will create the new 2nd Job Info record with seq-number "2".
When Termination Details of Managers and Direct Reports in Same File: There may be some data issues if both managers and their direct reports' termination details are included in same file. The data issue may be in the form of overlapping time slicess in Job Information. Because the termination records are in the same file, the direct report's Job Information may have two time slices - one for his/her own termination record one for the manager change because termination of the manager. The manager change records are created because of transfer of direct reports function when managerial positions change. This will create overlapping time slices in direct report's Job Information when the manager's termination date is before direct report's termination date. Hence, the best practice is to prepare seperate files for managers termination and direct reports termination. Our engineering team is working on a permanent fix for this. This article will be updated once the fix is implemented.
For more information on Employee Central Imports, please refer to the Employee Central Imports admin guide on the SAP Help site.
Best Practice : Terminate EC User
- User Terminate VIA Take action - MSS or Import
- Manager only from Via Take action - MSS
FAQ - Additional Information
Q) Where can I get information on this from the Guide?
A) Guide : Managing Mass Changes in Employee Central - Chapter: Termination Details Imports and Event
Guide Implementing Position Management - Chapter: Transferring Reports in Case of Termination
See Also
- 2545988 - How to Purge/Delete users in SuccessFactors
- 3375924 - How To check User Status Via Data inspector
- 2731597 - Termination Details Missing for Terminated User
- 2283806 - Termination Reason drop-down menu in Take Action > Terminate (MSS UI) is empty
- 2617429 - Event Reason Availability and Configuration in Employee Central
- 2079424 - Terminated Employee is Still “Active” in the System - Employee Central
- 2232778 - Transfer of Direct Reports When Manager promoted to New Position
- 2901514 - How to transfer direct reports to next manager on leaving position - Employee Central
Keywords
ec, employee central, employee data import, data imports, termination details, terminate via import, ECT-124331, manager, subordinate, supervisor, termination import, terminating via import, mass termination, mass change, mass route, separation, mass change , KBA , LOD-SF-EC-EDP-TER , Termination Details Import , LOD-SF-EC-EMP , Employment Information (Employment Details) , How To