SAP Knowledge Base Article - Public

3391845 - Managing Users Whose First Job Information Record is a Rehire Record


For users whose first Job Information Record is a Rehire Record this can cause various issues and validation messages to be shown.

This KBA aims to highlight why these users may have been created with a Rehire Record as their first record in Job Information and how you can continue to work with this users data to prevent any further validations or down-stream impacts. 


SAP SuccessFactors Employee Central 


Following older go-live and consulting guidance in 2015, customer where recommended to created Rehire Job Information Records as the first Job Information Record for some  migrated users. This lead to issues updating or adding Job records for these employees as with the introduction of Centralized Services, more advanced validations were introduced to ensure the users first record is a Hire record, which now cause validation messages to be shown for these employees.  This is a documented validation more information can be seen in the following section of the guide:
Implementing Employee Central Core: Data Validation for Job Information (MSS and History UI)

For example of an error you may see in the UI please review the following KBA: 3210187 - Error: 'You cannot create a job information record without the hire record for user ..." - Employee Central 


In order to be able to continue to update or add Job Information data for these users some actions are required to update their data. 

For the impacted users please do the following:

  • Via a Job History Import, create a dummy Hire Record and a Termination Record before the rehire record, e.g. if the rehire record was effective dated 01/01/2015, create via import a dummy hire record for 30.12.2014 along with a dummy termination record for 31.12.2014
  • This will need to be done with a Full Purge Job History Import and the Import file should also include the Rehire and any subsequent Job History Records.  
  • Things to consider
    • You can use the relevant permission settings to:
      -- prevent workflow from triggering during import
      -- onSave rule from triggering during import
      -- forward propagation from proceeding during import
      -- Further information can be found in the following section of the guide:
          Managing Mass Changes in Employee Central: Role-Based Permissions for Employee Data Import
    • If you use Position Management:
      - if the position field is required: you could use a mass position to assign to all the impacted users for the Hire and Termination records
      -- if the position field is not required: it can be left empty for the impacted users for the Hire and Termination records

Please Note for Customers who have intergrations with SAP ERP / S/4HANA:

  •  With regards to Full Transmission Start Date: please ensure that the settings are configured in a way that the newly created (Hire and Termination) records are not replicated.  


KBA , LOD-SF-EC-JOB , Job Information , How To


SAP SuccessFactors Employee Central all versions ; SAP SuccessFactors HCM Core all versions