SUPPORT / SAMPLES & SAS NOTES
Problem Note 67344: You are not able to route an entity, case, regulatory report, or CDD Review to a user in SAS® Anti-Money Laundering after applying Hot Fix 10
 |  |  |  |  |
You cannot route an entity, a case, a regulatory report, or a CDD Review to a user account who is not defined in SAS® Management Console as a direct member of a business unit group after you applying Hot Fix 10.
You might see the following error message in the user interface:
{{ Error: Invalid user ID: <userid>}}
{{ rest/<object>/triageRequest/route:400:}}
{{ Error routing <object>}}
{{ rest/<object>/triageRequest/route:400:}}
{{ Error routing <object>}}
The error message in SASComplianceSolutionsMid7.1.log is as follows:
ERROR 2021-01-08 15:52:22,878 [tomcat-http--8] - ServiceException.
com.sas.aml.service.ServiceException: Invalid user ID: <userID>
{{ at com.sas.aml.service.UserService.getUserByUserId(UserService.java:169)}}
{{ at com.sas.aml.service.QueueService.isUserInQueue(QueueService.java:201)}}
{{ at com.sas.aml.service.QueueService.checkUserInQueue(QueueService.java:223)}}
{{ at}}
com.sas.aml.service.QueueService$$FastClassBySpringCGLIB$$9f36e1c1.invoke(<gener
ated>)
{{ at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)}}
{{ at}}
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.interc
ept(CglibAopProxy.java:629)
{{ at}}
com.sas.aml.service.QueueService$$EnhancerBySpringCGLIB$$a8f0fa83.checkUserInQue
ue(<generated>)
{{ at com.sas.aml.service.CaseService.routeCases(CaseService.java:1069)}}
{{ at}}
com.sas.aml.service.CaseService$$FastClassBySpringCGLIB$$2aa60c68.invoke(<genera
ted>)
{{ at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)}}
com.sas.aml.service.ServiceException: Invalid user ID: <userID>
{{ at com.sas.aml.service.UserService.getUserByUserId(UserService.java:169)}}
{{ at com.sas.aml.service.QueueService.isUserInQueue(QueueService.java:201)}}
{{ at com.sas.aml.service.QueueService.checkUserInQueue(QueueService.java:223)}}
{{ at}}
com.sas.aml.service.QueueService$$FastClassBySpringCGLIB$$9f36e1c1.invoke(<gener
ated>)
{{ at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)}}
{{ at}}
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.interc
ept(CglibAopProxy.java:629)
{{ at}}
com.sas.aml.service.QueueService$$EnhancerBySpringCGLIB$$a8f0fa83.checkUserInQue
ue(<generated>)
{{ at com.sas.aml.service.CaseService.routeCases(CaseService.java:1069)}}
{{ at}}
com.sas.aml.service.CaseService$$FastClassBySpringCGLIB$$2aa60c68.invoke(<genera
ted>)
{{ at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)}}
The workaround is to assign the user to be a direct member of a business unit group in SAS Management Console.
To obtain a fix for this issue, contact SAS Technical Support.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Anti-Money Laundering | Microsoft® Windows® for x64 | 7.1 | 7.1 | 9.4 TS1M6 | 9.4 TS1M6 |
| 64-bit Enabled AIX | 7.1 | 7.1 | 9.4 TS1M6 | 9.4 TS1M6 | ||
| 64-bit Enabled Solaris | 7.1 | 7.1 | 9.4 TS1M6 | 9.4 TS1M6 | ||
| Linux for x64 | 7.1 | 7.1 | 9.4 TS1M6 | 9.4 TS1M6 | ||