SAP Knowledge Base Article - Public

3650979 - Concurrent Employment / isPrimaryAssignment Behaviour For Contingent Workers

Symptom

An employee is hired as a Contingent Worker with multiple Concurrent Employments / Secondary Assignments. Over time, the Primary Employment is changed. The employee profile reflects 'Is Primary Assignment' on the correct employment, and the 'Secondary Assignments' object for the user in 'Manage Data' reflects all of the Secondary Assignments, but when running an OData API call or checking the 'Table_PRIMARY_ASSIGNMENT' table for the employee in the Data Inspector, the 'isPrimary Assignment' / 'Primary Assignment' value reflects the wrong employment - it continues to reflect the original Primary Employment and does not change.

Environment

SAP SuccessFactors Employee Central

Cause

Concurrent Employment handling for Contingent Workers

Resolution

For employees who have all of their employments as Contingent Worker employments:

  • The primaryAssignment calculation is not based on the "Secondary Assignments" object in "Manage Data" like with regular Concurrent Employments
  • The calculation of Primary Assignments for Contingent Workers simply picks the first active Contingent Worker user, in order of Created Date, and assigns it as the primary.

Keywords

contingent, worker, contingent worker, concurrent, primary, secondary, employment, concurrent employment, primary employment, secondary employment, assignment, primary assignment, secondary assignment, INC14596136 , KBA , LOD-SF-EC-CON , Concurrent Employment , LOD-SF-EC-CWF , Contingent Workforce , Problem

Product

SAP SuccessFactors HCM Core 2505