A new hire is added to the instance. During entering the data, a Duplicate Check appears and the system informs about the matching data from a previous employment. The “Ignore Matches” option is selected and the system continue with a new hire instead of a rehire. After entering all data, a workflow is triggered for approval and send to an approver.
The approver click on the "udpate" option in the workflow, which takes him to the “Add new employee” screen, prefilled with all data which is already entered. If the user clicks to “Continue” after the block for Identification Information, the system again presents the Duplicate check with information regarding the found match in the system.
If the “Accept Match” option is chose, the event reason changes for “Rehire” and the field for Person ID is left empty. However, when directly doing a rehire after using the “Accept Match” button in Duplicate Check, the field for Person ID is prefilled with the previous Person ID. But if we have a workflow in place and the first approver is changing the new hire to rehire, the “old” Person ID is missing.
This behavior only happens via the Update button on workflow, if the accept match is made via Add New Employee screen, the person ID remains. If there is no hire template, the person ID also remains.
It only happens for the Update option via workflow and when there is a hire template.
SAP SuccessFactors Employee Central
ECT-215936, update, workflow, add new hire, new hire, edit workflow, template, hire template, personID, person ID, KI2211 , KBA , LOD-SF-EC-HIR-RIE , Rehire Inactive Employee , Known Error
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.