on 2024 Dec 19 7:34 AM
Hello,
We are facing an issue with one of our new hires in the ActiveDirectory-SuccessFactors integration.
Following message is shown in AD:
Failure Description
An entry cannot not be provisioned in this target: SuccessFactors. The entry is 12345. The reason the entry cannot be provisioned is internal to that application. An example of why an entry cannot be provisioned is a user with a given public identifier, such as an email address, having previously exercised a regulatory right to be removed from the application.
ReportableIdentifier
emp.emp@company.com
The username of the previous employment was the username AD is trying to update now. emp.emp@company.com
The username of the new employment was a number sequence, like 12345.
AD tried to update the new employment with the old username which was not possible since the old username was taken.
From past experience, I have seen that the old username is automatically updated to username_INACT. Why does this not happen in this case?
Hope someone knows the answer to this. I thought that was standard behavior.
Thanks!
Request clarification before answering.
Hi
When we rehire with new employment the new employee will not be able to use old the user name so there is a workaround advised by SAP where you enable the feature to login with old username even though having new username with new employment during rehire as described in kba 2677136 & SAP Article for this fix
Please review and check if it can resolve issue for your case.
Thanks
Manish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
7 | |
5 | |
5 | |
4 | |
4 | |
3 | |
2 | |
2 | |
2 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.