SuccessFactors to Active Directory user provisioning service, wrong employment profile synced to AD

Michal Ziemba 256 Reputation points
2022-07-06T14:12:08.167+00:00

Hi,
When using SAP SuccessFactors to Active Directory User Provisioning model, for some users who has concurrent employments, we get the wrong profile synced to ActiveDirectory (not primary employment).
For example, if we have a user who had concurrent employment and now he or she has only one job in SuccessFactors, we get all the data related to inactive employment of this user from SF to AD.

At first, we were scoping users using personIdExternal.
After reading this article we changed the scope and used userId. But nether or less there is no difference. We still get the wrong employment data and for terminated employments, the user in AD is also terminated.

When I use the API and query the user, I got the correct profile. Is it a bug?

https://{<!-- -->{endpoint}}/odata/v2/EmpJob/?$filter=userId eq '10451'&$format=json&$expand=departmentNav  

Do you have any tips on how to scope users with primary active employment?

Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
6,432 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Michal Ziemba 256 Reputation points
    2022-09-15T11:11:47.267+00:00

    I have raised a service request and Afees helped me by suggesting the full-service restart as described in the article Restart synchronizationJob
    with the following criteria:

    {
    "criteria" : { "resetScope" : "Full" }
    }

    It seems that this solved the issue.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.