- When there is a case of an Contingent worker and later on hired as Permanent Employee, the system consider the newly created permanent Employment as secondary and the terminated Cworker record as primary.
- You have a Business Rule with logic to check the "IsPrimary" record that meant to validate if the current Employment is Primary or Secondary Employment.
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental"
SAP SuccessFactors - Employee Central
This is an expected behavior, as when a Contingent Worker is later hired as a Permanent Employee, there is no way to determine or set one of the employments to primary or secondary.
"IsPrimary" is no longer supported (it is Deprecated) This behavior is documented on this guidebook Data Object Tables in Employee Central
See Note - 'You can not use this field because it has been deprecated.'
The only way you can set a Primary or Secondary employment in this scenario is by creating a new custom field and picklist.
You could create a custom field called 'is primary employment' or something and assign a yes/no picklist.
The custom field would need to be maintained then to hold the value.
IsPrimaryEmployment, Employment Characteristic, Rehired Contingent worker, Permanent Employment, IsPrimary , KBA , LOD-SF-EC-HIR , Hire & Rehire Wizards , LOD-SF-EC-RUL , DO NOT USE - Business Rules & Event Derivation , Problem