Symptom
An employee has a currently-active employment, and has a 'Secondary Assignment' object / record due to having a Secondary Assignment / Concurrent Employment at some point during their employment. The currently-active employment will be terminated in the future and the employee will be rehired on a new employment via Onboarding after that. After the future-dated rehire has been processed (hiring is completed, but it is still pending its hire date (status 'e', active external Onboardee)), it is the employment which has 'isPrimaryAssignment = true' when you perform an API Call on the employee's employments, even though the employee profile UI and 'Secondary Assignment' object in 'Manage Data' show the currently active employment as being the primary.
Read more...
Environment
SAP SuccessFactors Employee Central
Product
Keywords
primary, secondary, concurrent, employment, assignment, primary employment, secondary employment, concurrent employment, secondary assignment, isPrimary, is primary, is-primary, isPrimaryAssignment, primary, primary assignment, future, rehire, ONB, OBX, OData, API, OData API, Table_PRIMARY_ASSIGNMENT, INC14752426 , KBA , LOD-SF-EC-CON , Concurrent Employment , LOD-SF-INT-ODATA , OData API Framework , Bug Filed
About this page
This 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.
SAP Knowledge Base Article - Preview