Read operation on table 'sn_hr_core_case_total_rewards' from scope 'Global' was denied because the source could not be found.

N_Ladanga
Tera Contributor

‎04-21-2019 10:16 PM

Hi Everyone,

I'm stuck here. I created a new HR service under Total Rewards table [sn_hr_core_case_total_rewards]. Working pretty fine until I encountered this recently when I updated the hr service assignment group to a new one. When I use my own user (admin) to test, works perfectly fine - first task [sn_hr_core_task] gets auto-assigned to an agent. However not the case when I use actual employee profiles for testing. Seems like the error is causing the auto-assignment error?

I tried updating relevant Restricted Caller Access Privileges to Allowed status, however error still happens. Will appreciate your leads for resolution.find_real_file.png

find_real_file.png

Preview file
32 KB
Preview file
21 KB
0 Helpfuls
  • 2,080 Views
4 REPLIES 4

Alikutty A
Tera Sage

‎04-21-2019 10:33 PM

Hi,

I believe SN has not added the required Caller access entry for this operation. You may need to add it manually or raise an HI ticket for support,

Please refer to this post: https://community.servicenow.com/community?id=community_question&sys_id=964c8567dbd87f08fff8a345ca96... and see if you could add your entry in the caller access table.

N_Ladanga
Tera Contributor
In response to Alikutty A

‎04-26-2019 01:02 AM

Apologies for the late response A K. This has been helpful. So it's just some missing configurations. I don't know the whole list of all Caller access entries that I have to manually maintain. I tried one of the Business Rules but error is still happening. I have documented this and will raise to HI to ensure all possible entries are maintained. Much appreciated your prompt response. Thanks!

0 Helpfuls

pinki1
Tera Contributor
In response to N_Ladanga

‎06-28-2019 06:46 PM

Hi, I am also facing the similar issue in my instance. I hope you have resolved the issue. Could you please share the resolution if issue is resolved.
0 Helpfuls

jayesh mohan2
Mega Expert

‎04-29-2019 06:14 AM

N.Ladanga,
 
I have encountered this error many times in other instnaces and it probably is due to a Human Resources: Core script include which has Caller Access as Caller Restriction. Specifically, it might be a script include which is auto-assigning tickets. If you have a sub-production instance, you can list all the script includes which are in Human Resources: Core scope and see if you can change anything which has Caller Access as Caller Restriction to none. Let me know if this helps?
0 Helpfuls