Symptom
Check Tool is always returning the messages "The selected user does not exist for People Analytics" or "The availability of the selected user couldn’t be confirmed for Story report, because of a connection error" or "Unable to update the user configurations do Story report" even though users can create Story reports with no issue.
Environment
SAP SuccessFactors HCM Suite
Reproducing the Issue
- Look for Check Tool in the Tool Search in BizX
- Click on Validation tab
- Select Reporting > User record exists for Story report
- Run the check for a specific user
- The check returns one of the following messages for any user, even for users who can create Story reports successfully: "The selected user does not exist for People Analytics", "The availability of the selected user couldn’t be confirmed for Story report, because of a connection error" or "Unable to update user configurations for Story reports".
Cause
Some configuration information is incorrect or not updated on backend preventing Check Tool to work successfully.
Resolution
1. Go to provisioning > Configurations for Stories in People Analytics
- Run Refresh X509 Certificates
- Refresh and Regenerate SAC OAuth Configurations
- Refresh SAC Live Connection
Note: Kindly refresh all three in this order
*To access Provisioning and perform the necessary changes please contact your Partner or open a ticket with SAP Support under LOD-SF-ANA-SAC component.
2. Logout then login again in the instance and check the check tool again.
Issue should be resolved now.
See Also
Keywords
check tool issue, SAC User check, check tool for sac is incorrect, check tool for story does not work, check tool, incorrect, The availability of the selected user couldn’t be confirmed for Story report, because of a connection error, Unable to update user configurations for Story reports , KBA , LOD-SF-ANA-SAC-ADM , SF Admin configurations (Security Center, Provisioning) , Problem
Product
Attachments
| Image 1.png |
| Image 2.png |
| Image 3.JPG |
| Image 2.png |
| Image 1.png |
| Image 3.JPG |
SAP Knowledge Base Article - Public