Symptom
After 1H 2023 release no possibility to edit the first SCWK job info record to change them into hire record. This is due to Centralized Services(CS) validations. Now the users not having a hire record as a first record in job info which preventing to make any changes to job info since all job info transaction types are supported by CS universally with 2H 2023 release.
Environment
SAP SuccessFactors Employee Central
Cause
Users having Start Contingent Worker(SCWK) event as event for their first job info record.
Resolution
If the Start Contingent Worker(SCWK) event related job info record is the first record (or other events which are no hire or rehire), it is possible to create hire record via job history before the SCWK record.
For such contingent workers whose first record is not hire record:
1. Perform a job history import for the relevant users to create their hire records with effective start date being the day before their current SCWK record (their current first job info record). Make sure to provide all the relevant job info data in the import file (i.e. the same data that is used in the current SCWK record for the user except for the event reason which has to be a hire related one).
2. Delete the users' SCWK records (manually via history or in bulk via job history import).
3. If it is required to have the Hire record with the same effective start date than the former SCWK records had, you can use the Hire date correction tool to move the hire records to the relevant date. This can be done either via the Hire Date Correction(HDC) UI or via MDF import for the HDC object.
Keywords
KBA , LOD-SF-EC-CWF , Contingent Workforce , LOD-SF-EC-JOB-UI , History UI & MSS UI , Problem