Are and of you using SAP SuccessFactors as your Identity Authoritative source?
We were using OnBoarding module 1.0, and that works fine. That module is being deprecated, and moved to 2.0.
The difference is not that ‘People’ are created earlier in the SuccessFactors process.
SailPoint is aggregating and creating identities as expected. It works fine for new Employees and Contractors, but the issue arises for re-hires. We end up with duplicates for rehires.
I see similar-ish questions have been raised before (links below) but there were no solutions.
I am wondering if anyone here has a good solution. The only solution I have found is this one, where they created a flag/attribute in SuccessFactors to determine whether to aggregate the account or not
If you are getting duplicates for rehires - are you sure that this is not an HR problem and they are entering the user as a new hire?
When I was using SF2, the system actively asks the question of HR ‘these details are very similar to ‘joe bloggs’ is it the same person?’ Designed to prevent the problem you are witnessing
A similar kind of solution was proposed to us when we were encountering duplicates during AD integration. But the flag had to be set from SP end. Here it is at SAP end. Have you tried the solution? Have you considered writing Connector rule.
You are correct it does this, but the new v2.0 onBoarding Module does this now after creating the identity shell account. (which gets aggregated)
So if you say ‘yes, this is the same joe bloggs’ - it will link to the old SF account, but that shell account still remains in SuccessFactors. I have no idea why they made this design decision, but it is something everyone has to work around.