Risk analysis failed in CUP

Hi,
We have same connector name in CUP and RAR but risk analysis failed and throws error "Risk analysis failed: ExceptionRisk Analysis failed"
have a look on detailed log as follows.
2012-01-03 17:54:54,044 [SAPEngine_Application_Thread[impl:3]_7] ERROR Ignoring exception : com.virsa.ae.service.messaging.MessageNotFoundException: Code: '9923', Locale: 'en'
com.virsa.ae.service.messaging.MessageNotFoundException: Code: '9923', Locale: 'en'
     at com.virsa.ae.service.messaging.MessageFormatter.formatAsText(MessageFormatter.java:103)
     at com.virsa.ae.commons.utils.JSValidationUtil.getMessage(JSValidationUtil.java:467)
     at com.virsa.ae.commons.utils.JSValidationUtil.formatMessage(JSValidationUtil.java:523)
     at com.virsa.ae.commons.utils.JSValidationUtil.formatMessage(JSValidationUtil.java:548)
     at jsp_common_import_export1321962467821._jspService(jsp_common_import_export1321962467821.java:60)
     at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:566)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.include(RequestDispatcherImpl.java:509)
     at com.sap.engine.services.servlets_jsp.server.jsp.PageContextImpl.include(PageContextImpl.java:176)
     at jsp_cfg_support1321962466399._jspService(jsp_cfg_support1321962466399.java:148)
     at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:566)
     at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
     at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
     at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at
Thanks,
nayana

Hi,
We have uploaded the latest xml files as per service pack still getting message risk analysis failed . Have a look on following log
and advice me.
2012-01-04 23:45:45,273 [SAPEngine_Application_Thread[impl:3]_32] ERROR com.virsa.ae.core.BOException: ExceptionRisk Analysis failed
com.virsa.ae.core.BOException: ExceptionRisk Analysis failed
     at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:199)
     at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1167)
     at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:381)
     at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:118)
     at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:295)
     at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
     at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.virsa.ae.service.ServiceException: ExceptionRisk Analysis failed
     at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.determineRisks(RiskAnalysisWS53DAO.java:591)
     at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:119)
     at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
     ... 24 more
Thanks,
nayana

Similar Messages

  • Cup 5.3 Risk Analysis failed

    Hello GRC Gurus,
    SAP GRC AC CUP - 5.3
    Support Pack - 07
    When we perform risk analysis from CUP below mentioned error is coming
    Risk analysis failed: Exception from the service : Risk Analysis failed
    Please also find the System log as well
    2010-05-11 15:32:13,067 [SAPEngine_Application_Thread[impl:3]_34] DEBUG com.virsa.ae.service.sap.RiskAnalysisWS53DAO : getViolations() :   : into the method with userid : E66447, rolesToAdd : [Lcom.virsa.ae.service.sap.ws53.types.RoleToAddDTO;@48a4f072, rolesToDelete : [Lcom.virsa.ae.service.sap.ws53.types.RoleToDeleteDTO;@44a5f1a0, profilesToDelete : [Lcom.virsa.ae.service.sap.ws53.types.ProfileToDeleteDTO;@6a9a6295, mitigation : true, criticalAction : true, criticalRole : false, permissionDetail : false
    2010-05-11 15:32:13,109 [SAPEngine_Application_Thread[impl:3]_34] DEBUG  RiskAnalysisWS53DAO.java@166:getViolations() : riskAnaysisWS : [email protected]5ae0
    2010-05-11 15:32:13,115 [SAPEngine_Application_Thread[impl:3]_34] DEBUG  RiskAnalysisWS53DAO.java@170:getViolations() : webServicesURI : http://grcpdbci.mis.amat.com:54000/VirsaCCRiskAnalysisService/Config1?wsdl&style=document
    2010-05-11 15:32:13,117 [SAPEngine_Application_Thread[impl:3]_34] DEBUG  RiskAnalysisWS53DAO.java@175:getViolations() : username : virsaadm
    2010-05-11 15:32:13,119 [SAPEngine_Application_Thread[impl:3]_34] DEBUG  RiskAnalysisWS53DAO.java@183:getViolations() : setting socketTimeout to 900000 milli seconds
    2010-05-11 15:32:13,121 [SAPEngine_Application_Thread[impl:3]_34] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2010-05-11 15:32:13,123 [SAPEngine_Application_Thread[impl:3]_34] DEBUG  RiskAnalysisWS53DAO.java@310:getViolations() : RiskAnalysis___ Calling excute Risk Analysis, Wait for the Results... (Note: Make sure that Compliance Calibrator background daemons are started)
    2010-05-11 15:32:19,371 [SAPEngine_Application_Thread[impl:3]_34] DEBUG  RiskAnalysisWS53DAO.java@312:getViolations() : RiskAnalysis___ Got the Risk Analysis Results
    2010-05-11 15:32:19,373 [SAPEngine_Application_Thread[impl:3]_34] DEBUG  RiskAnalysisBO.java@197:findViolations() : RiskAnalysis___  Failed with Exception : Exception from the service : Risk Analysis failed
    2010-05-11 15:32:19,375 [SAPEngine_Application_Thread[impl:3]_34] DEBUG com.virsa.ae.service.ServiceException: Exception from the service : Risk Analysis failed
    com.virsa.ae.service.ServiceException: Exception from the service : Risk Analysis failed
         at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.determineRisks(RiskAnalysisWS53DAO.java:582)
         at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:119)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1073)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:300)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:109)
         at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:271)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    2010-05-11 15:32:19,378 [SAPEngine_Application_Thread[impl:3]_34] ERROR com.virsa.ae.core.BOException: Exception from the service : Risk Analysis failed
    com.virsa.ae.core.BOException: Exception from the service : Risk Analysis failed
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:199)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1073)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:300)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:109)
         at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:271)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.virsa.ae.service.ServiceException: Exception from the service : Risk Analysis failed
         at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.determineRisks(RiskAnalysisWS53DAO.java:582)
         at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:119)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
         ... 24 more
    Please help me on this ASAP
    Thanks,
    Jagat

    Please also go throug this system log as well
    2010-05-11 16:59:03,797 [SAPEngine_Application_Thread[impl:3]_50] ERROR Exception during EJB call, Ignoring and trying Webservice Call
    com.virsa.ae.service.ServiceException: Exception in getting the results from the EJB service : Exception in getting the results from the web service : Exception in initializing
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:295)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:419)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.determineRisks(RiskAnalysisEJB53DAO.java:522)
         at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:103)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1073)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:300)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:109)
         at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:271)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.virsa.ae.service.ServiceException: Exception in getting the results from the web service : Exception in initializing
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.execRiskAnalysis(RiskAnalysisEJB53DAO.java:309)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:277)
         ... 28 more
    Caused by: com.virsa.ae.service.ServiceException: Exception in initializing
         at com.virsa.ae.service.sap.SystemDAOFactory.getCCRiskAnalysisEJBClient(SystemDAOFactory.java:1967)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.execRiskAnalysis(RiskAnalysisEJB53DAO.java:304)
         ... 29 more
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of RiskAnalysis.
         at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:649)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
         at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
         at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at com.virsa.ae.service

  • Getting "Risk Analysis Failed " error while raising request from IDM

    Hi friends,
    Some of the User to Role mapping requests from IDM did not reach CUP (request ID = null) . When noticed the VDS log , we found the error from GRC webservice to be Risk Analysis Failed . We thought it might be an RAR issue , however , the request just got through CUP when submitted from GRC webservice directly . From RAR perspective also, everything looks ok .
    Please provide your thoughts as to whether this error is pertaining to some other issue or suggest me what I can check in Identity center to correct this .
    Thanks in advance for your help .

    The connector set up are all looking correct . However the requests are not getting raised in many cases .
    At one point we identified that , since our SAP systems have been migrated to DB2, some of the systems were down .
    So when the system is down we decided , Risk analysis is failing . however , now the systems are up and running and still the risk analysis is failing .

  • Risk Analysis failure in CUP

    Hi Experts,
    We have upgraded our sandbox from GRC Access Controls v5.2 to version v5.3 SP7. I am now getting the following error when doing CUP Risk Analysis to RAR:
    Risk analysis failed: Exception from the service : Risk Analysis failed
    Any ideas?
    The Connection Names are the same for CUP and RAR.
    Here is the CUP log for the error:
    2009-05-11 17:17:12,562 [SAPEngine_Application_Thread[impl:3]_36] ERROR com.virsa.ae.core.BOException: Exception from the service : Risk Analysis failed
    com.virsa.ae.core.BOException: Exception from the service : Risk Analysis failed
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:199)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1073)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:300)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:109)
         at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:271)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Caused by: com.virsa.ae.service.ServiceException: Exception from the service : Risk Analysis failed
         at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.determineRisks(RiskAnalysisWS53DAO.java:586)
         at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:119)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
         ... 24 more

    Hello All,
    I am having the same issue in CUP
    EXCEPTION_FROM_THE_SERVICERisk Analysis failed
    com.virsa.ae.core.BOException: EXCEPTION_FROM_THE_SERVICERisk Analysis failed.
    The Password for the web service has not expired or the URI is the same as the CCRiskanalysis service and as well the connectors have the same name in RAR & CUP.
    It worked till yesterday and stopped working suddenly. Any help is appreciated.

  • CUP 5.3 (SP12) Risk Analysis Errors in CUP

    Hello Experts,
    When I run risk analysis in CUP for user provisioning. I get an error message:
    Risk analysis failed: Exception in getting the results from the web service : Service call exception; nested exception is: java.lang.Exception: Incorrect content-type found 'text/html'
    Connector names are the same across all the components. We have a CUP test environment with SP11, and we did not have this kind of errors. I virtually tried everything I could.
    If you can, please assist me.
    HM

    Hello HM, 
    I had this error when I first upgraded to SP12 but I don't know if it is a SP issue or not.
    My CUP --> RAR SOD Analysis works for me on SP12.
    You might try double checking the following:
    1. Check all CUP configuration Web Service parameters in CUP --> Configuration --> 1) Risk Analysis & 2) Mitigation.
    2. Check that you uploaded the latest UME roles that were delivered with SP12.
    3. Check the UME user that is configured in CUP for risk analysis to make sure the password is still correct and that it has enough assigned roles.
    4. Make sure you uploaded all the required XML configuration files to CUP --> Configuration --> Initial System Data.

  • Risk anlaysis failed in CUP

    Hi Everyone
    I am trying to run risk analysis in CUP ( GRC AC 5.3) but I am getting the follwoing error
    Risk analysis failed: Exception from the service : Invalid System
    my connector works fine, and I have also changed the intial pasword for the websuer used in the Risk analysis tab in Configuration
    Webuser have admin rights .
    I guess I need have the same name for the connector as in RAR ... will try to chaneg and give it a try .
    I mean the connector name in CUP and System Id for the connector in RAR should be the same right?
    did anayone face simialr issue ?
    any help would be appreacited .
    Regards
    PKK

    Hi Harleen
    I ceelted all the role attributes created all from scratch and editied the import file accordingly
    we are on GRC aC 5.3 and SP level 7
    belwo is log , might split into two
    2009-03-24 14:10:15,997 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  NavigationEngine.java@85:execute() : Current Module: |CFG| Conversation: |cnvConfigImportRoles| Screen: |scrConfigImportRoles|
    2009-03-24 14:10:15,997 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  NavigationEngine.java@105:execute() :  Module#CFG#Conversation#cnvConfigImportRoles#Screen#scrConfigImportRoles#Action#saveConfigImportRoles#
    2009-03-24 14:10:15,997 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  NavigationEngine.java@261:execute() : Handler found:class com.virsa.ae.configuration.actions.ImportRolesAction
    2009-03-24 14:10:15,997 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  ImportRolesAction.java@56:execute() : INTO the method
    2009-03-24 14:10:16,091 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@2752:getAELocaleCodeMapKeyAsLocaleId() : INTO the method
    2009-03-24 14:10:16,091 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameCUSTOM_FIELD_NAME,pLocaleId1
    2009-03-24 14:10:16,106 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,106 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,106 [SAPEngine_Application_Thread[impl:3]_28] ERROR  RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system  High
    2009-03-24 14:10:16,106 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,106 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,106 [SAPEngine_Application_Thread[impl:3]_28] ERROR  RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system  Low
    2009-03-24 14:10:16,106 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,106 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,106 [SAPEngine_Application_Thread[impl:3]_28] ERROR  RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system  High
    2009-03-24 14:10:16,106 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,106 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,106 [SAPEngine_Application_Thread[impl:3]_28] ERROR  RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system  Low
    2009-03-24 14:10:16,106 [SAPEngine_Application_Thread[impl:3]_28] ERROR  RoleFileImportImpl.java@838:insertOrUpdateRoleDetails() : Error in Business Sub Process may be Business Sub Process not exists in the system  BE_MM
    2009-03-24 14:10:16,122 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,122 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,122 [SAPEngine_Application_Thread[impl:3]_28] ERROR  RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system  Meduim
    2009-03-24 14:10:16,122 [SAPEngine_Application_Thread[impl:3]_28] ERROR  RoleFileImportImpl.java@838:insertOrUpdateRoleDetails() : Error in Business Sub Process may be Business Sub Process not exists in the system  BE_MM
    2009-03-24 14:10:16,122 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,122 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,122 [SAPEngine_Application_Thread[impl:3]_28] ERROR  RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system  Low
    2009-03-24 14:10:16,122 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,122 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,122 [SAPEngine_Application_Thread[impl:3]_28] ERROR  RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system  Meduim
    2009-03-24 14:10:16,122 [SAPEngine_Application_Thread[impl:3]_28] ERROR  RoleFileImportImpl.java@838:insertOrUpdateRoleDetails() : Error in Business Sub Process may be Business Sub Process not exists in the system  BE_SD
    2009-03-24 14:10:16,138 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,138 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,138 [SAPEngine_Application_Thread[impl:3]_28] ERROR  RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system  Meduim
    2009-03-24 14:10:16,138 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,138 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,138 [SAPEngine_Application_Thread[impl:3]_28] ERROR  RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system  Meduim
    2009-03-24 14:10:16,138 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,138 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,138 [SAPEngine_Application_Thread[impl:3]_28] ERROR  RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system  High
    2009-03-24 14:10:16,138 [SAPEngine_Application_Thread[impl:3]_28] ERROR  RoleFileImportImpl.java@838:insertOrUpdateRoleDetails() : Error in Business Sub Process may be Business Sub Process not exists in the system  BE_SD
    2009-03-24 14:10:16,138 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,138 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,138 [SAPEngine_Application_Thread[impl:3]_28] ERROR  RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system  Meduim
    2009-03-24 14:10:16,153 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,169 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,169 [SAPEngine_Application_Thread[impl:3]_28] ERROR  RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system  Meduim
    2009-03-24 14:10:16,169 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,169 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,169 [SAPEngine_Application_Thread[impl:3]_28] ERROR  RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system  Meduim
    2009-03-24 14:10:16,169 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,169 [SAPEngine_Application_Thread[impl:3]_28] DEBUG  AECacheUtil.java@924:getCacheObject() : INTO the method : pCacheNameSYSTEMS,pLocaleId1
    2009-03-24 14:10:16,169 [SAPEngine_Application_Thread[impl:3]_28] ERROR  RoleFileImportImpl.java@822:insertOrUpdateRoleDetails() : Error in Critical Level may be Critical Level not exists in the system  Meduim
    2009-03-24 14:10:16,169 [SAPEngine_Application_Thread[impl:3]_28] ERROR 
    Regards
    PKK

  • Risk analysis failed: Exception from the service : Invalid System

    I'm trying to get the risk analysis performed for CUP requests.  When I'm in the process of creating a request, and I add roles to the request and then click on the risk analysis button, I get the above error.
    I checked the URI that I've included in the Risk Analysis section of the configuration and I believe it is correct:
    http://<server>:<port>/VirsaCCRiskAnalysisService/Config1?wsdl&style=document
    I've selected 5.3 web service, and I have provided a user ID that has admin rights.
    What do you think is the reason this error is being thrown?
    The error in the log is:
    2009-11-19 15:04:31,821 [SAPEngine_Application_Thread[impl:3]_39] ERROR com.virsa.ae.core.BOException: Exception from the service : Invalid System
    com.virsa.ae.core.BOException: Exception from the service : Invalid System
    Thanks,
    Santosh

    Frank,
    Thanks for your response.  I was thinking along these lines already and so I have tried to do as you suggest.  However it didn't work and the log indicated that it didn't like my connector name (even though the connector name is now the same as in RAR).
    Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'SANDBOX' in the SLD. No such JCO destination is defined in the SLD.
    However, I looked at one of the online post installation checklists for CUP and I gathered that it might be necessary to have the JCo itself renamed at the backend to reflect the name used in RAR, and that should populate into my connector list within CUP (when you click on the magnifying glass).
    I'm waiting to try that out, but I'm not sure about any secondary impact of making a change to the JCo name.
    Let me know what you think about that move.
    Thanks,
    Santosh

  • Risk analysis failed: ExceptionInvalid System

    Hi Gurus,
    When I am doing risk analysis in CUP for work flow request I am getting following error"Risk analysis failed: ExceptionInvalid System"
    And system log is as follows"
    011-12-18 15:52:02,729 [SAPEngine_Application_Thread[impl:3]_2] ERROR
    com.virsa.ae.service.messaging.MessageNotFoundException: Code: '9940', Locale: 'en'
    com.virsa.ae.service.messaging.MessageNotFoundException: Code: '9940', Locale: 'en'
         at com.virsa.ae.service.messaging.MessageFormatter.formatAsText
    (MessageFormatter.java:103)
         at com.virsa.ae.search.po.RequestHistoryPO.getDisplayString(RequestHistoryPO.java:112)
         at jsp_show_audit_info1323336819278._jspService
    (jsp_show_audit_info1323336819278.java:110)
         at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
         at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service
    (JSPServlet.java:566)
         at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service
    (JSPServlet.java:190)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork
    (RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.include
    (RequestDispatcherImpl.java:509)
         at com.sap.engine.services.servlets_jsp.server.jsp.PageContextImpl.include
    (PageContextImpl.java:163)
         at jsp_request_review1323336807965._jspService(jsp_request_review1323336807965.java:703)
         at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
         at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service
    (JSPServlet.java:566)
         at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service
    (JSPServlet.java:190)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork
    (RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward
    (RequestDispatcherImpl.java:377)
         at com.sap.engine.services.servlets_jsp.server.jsp.PageContextImpl.forward
    (PageContextImpl.java:199)
         at jsp_request_review_controller1323336806543._jspService
    (jsp_request_review_controller1323336806543.java:18)
         at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
         at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service
    (JSPServlet.java:566)
         at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service
    (JSPServlet.java:190)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork
    (RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward
    (RequestDispatcherImpl.java:377)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service
    (AEFrameworkServlet.java:461)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork
    (RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward
    (RequestDispatcherImpl.java:377)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service
    (AEFrameworkServlet.java:461)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet
    (HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest
    (HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet
    (RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet
    (RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer
    (RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle
    (RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at
    com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process
    (ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Thanks,
    Nayana

    Hi,
    Have you already checked this thread??
    Error on calling RAR from CUP
    Cheers,
    Diego.

  • Risk Analysis Failing in ERM 5.3

    Hi All -
    I would appreciate some assistance with pin-pointing an issue that I'm having with running Risk Analysis on roles in ERM. Currently I have RAR configured with the appropriate rule set and generating the expected risk/sod conflicts for users & roles. I have also added the appropriate Web Service Info. in th Misc section under the configuration tab (url, user, pwd) for all sections associate with RAR integration.
    Now when I run a risk analysis on a particular role in RAR i get the correct conflicts however when I get the Risk Analysis stage with ERM I receive the following Error:
    Risk analysis failed; Cannot assign NULL to host variable 5. setNull() can only be used if the corresponding column is nullable. The statement is "INSERT INTO VT_RE_RSK_OBJRULES (OBJCODE, OBJDESC, OBJFLDCODE, OBJFLDDESC, VALFRMID, VALTOID, COND, RSKVIOLID) VALUES(?, ?, ?, ?, ?, ?, ?, ?)".
    I also get this error when trying to run Mass Maintenance --> Risk Analysis:
    Risk anaysis for role "XX:XXXXX" failed
    Before I was getting error: "Risk Analysis performed successfully; No Risk Found" so I referenced SAP Note 1265964 and applied all solution steps.
    Lastly here is the error log:
    2010-01-14 14:59:28,768 [SAPEngine_Application_Thread[impl:3]_31] ERROR com.virsa.re.role.actions.RiskAnalysisAction
    java.lang.Throwable: Cannot assign NULL to host variable 5. setNull() can only be used if the corresponding column is nullable. The statement is "INSERT INTO VT_RE_RSK_OBJRULES (OBJCODE, OBJDESC, OBJFLDCODE, OBJFLDDESC, VALFRMID, VALTOID, COND, RSKVIOLID)  VALUES(?, ?, ?, ?, ?, ?, ?, ?)".
         at com.virsa.re.bo.impl.RiskAnalysisBO.saveObjViolations(RiskAnalysisBO.java:906)
         at com.virsa.re.bo.impl.RiskAnalysisBO.performObjLvlRiskAnalysis(RiskAnalysisBO.java:824)
         at com.virsa.re.bo.impl.RiskAnalysisBO.performRiskAnalysisOnSystem(RiskAnalysisBO.java:214)
         at com.virsa.re.role.actions.RiskAnalysisAction.performRiskAnalysisOnMultipleRoles(RiskAnalysisAction.java:609)
         at com.virsa.re.role.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:112)
         at com.virsa.framework.NavigationEngine.execute(NavigationEngine.java:273)
         at com.virsa.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:230)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
         at com.virsa.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:286)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
         at com.virsa.comp.history.filter.HistoryFilter.doFilter(HistoryFilter.java:43)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:384)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Any help would be greatly appreciate it - Thanks in Advance!

    GOing to repost

  • Risk analysis failed; Risk Analysis failed

    Hi,
    Risk analysis failed in RE at object level but its working fine at transaction level, Any suggetion
    Thanks

    Hi,
    Issue persist for only one solution rest all working fine, here is the log
    -- Request dump for Action Path is scrLeftNav.linkConfigSysLog
    2009-02-20 16:49:17,521 [SAPEngine_Application_Thread[impl:3]_19] DEBUG recordHistory:0::true#
    2009-02-20 16:49:17,521 [SAPEngine_Application_Thread[impl:3]_19] DEBUG -- End Request dump for Action Path is scrLeftNav.linkConfigSysLog
    2009-02-20 16:49:17,521 [SAPEngine_Application_Thread[impl:3]_19] DEBUG Current Module: |RE| Conversation: |cnvRole| Screen: |scrRiskAnalysis|
    2009-02-20 16:49:17,521 [SAPEngine_Application_Thread[impl:3]_19] DEBUG  Module#RE#Conversation#cnvRole#Screen#scrLeftNav#Action#linkConfigSysLog#
    2009-02-20 16:49:17,521 [SAPEngine_Application_Thread[impl:3]_19] ERROR Requested navigation control not found
    java.lang.Throwable: Action not found - linkConfigSysLog
         at com.virsa.framework.ScreenDefn.getActionDefn(ScreenDefn.java:62)
         at com.virsa.framework.NavigationEngine.execute(NavigationEngine.java:125)
         at com.virsa.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:230)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
         at com.virsa.comp.history.filter.HistoryFilter.doFilter(HistoryFilter.java:43)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:384)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    2009-02-20 16:49:17,521 [SAPEngine_Application_Thread[impl:3]_19] DEBUG Processing interrupted Caused by Redirecting to error recovery page
    com.virsa.framework.InterruptProcessingException: Redirecting to error recovery page
         at com.virsa.framework.NavigationEngine.execute(NavigationEngine.java:140)
         at com.virsa.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:230)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
         at com.virsa.comp.history.filter.HistoryFilter.doFilter(HistoryFilter.java:43)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:384)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG
    -- Request dump for Action Path is scrTopNav.cfg
    2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG -- End Request dump for Action Path is scrTopNav.cfg
    2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG Current Module: |RE| Conversation: |cnvRole| Screen: |scrRiskAnalysis|
    2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG  Module#RE#Conversation#cnvRole#Screen#scrTopNav#Action#cfg#
    2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG Changing Screen: FROM: scrRiskAnalysis TO scrTopNav
    2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG com.virsa.framework.Context : clearScreenRep :   : 4 entries cleared from screen repositiory
    2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG Handler found:class com.virsa.re.actions.SuccessAction
    2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG forwarding to:CFG.cnvBusProc.scrBusProc.cfgSearchBusProc.do
    2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG
    -- Request dump for Action Path is CFG.cnvBusProc.scrBusProc.cfgSearchBusProc
    2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG -- End Request dump for Action Path is CFG.cnvBusProc.scrBusProc.cfgSearchBusProc
    2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG Current Module: |RE| Conversation: |cnvRole| Screen: |scrTopNav|
    2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG  Module#CFG#Conversation#cnvBusProc#Screen#scrBusProc#Action#cfgSearchBusProc#
    2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG Changing Module: FROM: RE TO CFG
    2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG com.virsa.framework.Context : clearConversationRep :   : 18 entries cleared from conversation repositiory
    2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG com.virsa.framework.Context : clearScreenRep :   : 0 entries cleared from screen repositiory
    2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG Handler found:class com.virsa.re.configuration.action.BusinessProcessAction
    2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG In LockedObjBO.deleteLockedObjBySession(String sessionID) starts.....
    2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG In LockedObjBO.deleteLockedObjBySession(String sessionID) ends.....
    2009-02-20 16:49:18,475 [SAPEngine_Application_Thread[impl:3]_14] DEBUG forwarding to:/cfg_bus_proc_search.jsp

  • Risk Analysis in a CUP request

    Is there any way to run a Risk Analysis in a CUP request on different Rule Sets?
    Letu2019s say you have 3 different Rule Sets like US - EU u2013 Global defined in RAR. Each one includes its own risks. In a CUP
    request, it shows risks based on the u201CVirsaCCRiskAnalysisServiceu201D defined in your CUP config.
    In our case we use the global Rule Set but the problem is for an EU request you can have US risks appearing that must be mitigated even if those risks are not relevant for EU.
    It would be great if we could link the attributes Company or Functional Area directly to a specific rule set.
    Please help/comment on this issue.
    Regards

    Hi,
    When we perform risk analysis on the request, ruleset for the risk analysis for CUP request is picked from RAR default values.
    RAR-> Configuration-> Default Values-> Default rule set for risk analysis.
    This rule set is picked by CUP to perform the risk analysis.
    With the current design it is not possible to link  the attributes Company or Functional Area directly to a specific rule set.
    Kind Regards,
    Srinivasan

  • AE Risk analysis failed

    Hi experts!
    I'm running risk analysis from AE... and after a while the result is this message: "Risk analysis failed: Exception from the service : Risk Analysis failed"
    The connector IDs are the same and the web services configured is "http://server:port/VirsaCCRiskAnalysisService/Config1?wsdl&style=document"
    Could any body help me please.

    I am getting the same error while running AE with AEApprover role.
    ERROR com.virsa.ae.core.BOException: Exception from the service : Risk Analysis failed
    com.virsa.ae.core.BOException: Exception from the service : Risk Analysis failed
    What could be the issue?
    Thanks
    Siri

  • CUP : RISK ANALYSIS FAILED for Multi systems

    Greetings,
    Risk Analysis through CUP is failing on a request containing multi system access.
    There are 2 systems requested on the same CUP request form. At the stage of Risk analysis is to be performed the risk analysis errors out as the risk analysis is performed on the entire request across both the systems, After the receiving the error when an individual system is selected the RA is performed with out any failure on both the systems independent of each other
    I have check already check the below and they seem working fine without any issue
    1. The admin passwords have been checked in both the systems (backend) as well as in the UME.
    2. The risk analysis web service works as expected and there is no failure.
    3. The connectors have the same name both in CUP & RAR no difference
    4. SAPJCO connectors are appropriately setup in the SLD for both the systems and they work when tested out.
    5. The URI is setup correct and no issue identified there.
    6. Both the systems request have the same stage/path and the custom approver determination appropriately setup
    When the approver tries to approve the request Risk analysis is setup as a mandatory task and when the RA is performed the system takes the default "ALL" and errors out, when you choose a specific system and perform you get the required results without any failure. Below is the java dump for the error.
    Please let me know if I have missed anything?
    Line: -
    2011-03-09 10:16:11,264 [SAPEngine_Application_Thread[impl:3]_28] ERROR java.lang.VerifyError: com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;
    java.lang.VerifyError: com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.execRiskAnalysis(RiskAnalysisEJB53DAO.java:305)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:277)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:419)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.determineRisks(RiskAnalysisEJB53DAO.java:527)
         at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:103)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1108)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:335)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:112)
         at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:295)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:219)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    2011-03-09 10:16:11,278 [SAPEngine_Application_Thread[impl:3]_28] ERROR Exception during EJB call, Ignoring and trying Webservice Call
    com.virsa.ae.service.ServiceException: Exception in getting the results from the EJB service : com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:295)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:419)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.determineRisks(RiskAnalysisEJB53DAO.java:527)
         at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:103)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1108)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:335)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:112)
         at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:295)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:219)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Caused by:
    java.lang.VerifyError: com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.execRiskAnalysis(RiskAnalysisEJB53DAO.java:305)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:277)
         ... 28 more
    2011-03-09 10:19:32,401 [SAPEngine_Application_Thread[impl:3]_28] ERROR com.virsa.ae.core.BOException: EXCEPTION_FROM_THE_SERVICERisk Analysis failed
    com.virsa.ae.core.BOException: EXCEPTION_FROM_THE_SERVICERisk Analysis failed
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:199)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1108)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:335)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:112)
         at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:295)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:219)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Caused by:
    com.virsa.ae.service.ServiceException: EXCEPTION_FROM_THE_SERVICERisk Analysis failed
         at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.determineRisks(RiskAnalysisWS53DAO.java:587)
         at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:119)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
         ... 24 more
    Edited by: Angara Rao on Mar 9, 2011 5:15 PM

    Greetings,
    Risk Analysis through CUP is failing on a request containing multi system access.
    There are 2 systems requested on the same CUP request form. At the stage of Risk analysis is to be performed the risk analysis errors out as the risk analysis is performed on the entire request across both the systems, After the receiving the error when an individual system is selected the RA is performed with out any failure on both the systems independent of each other
    I have check already check the below and they seem working fine without any issue
    1. The admin passwords have been checked in both the systems (backend) as well as in the UME.
    2. The risk analysis web service works as expected and there is no failure.
    3. The connectors have the same name both in CUP & RAR no difference
    4. SAPJCO connectors are appropriately setup in the SLD for both the systems and they work when tested out.
    5. The URI is setup correct and no issue identified there.
    6. Both the systems request have the same stage/path and the custom approver determination appropriately setup
    When the approver tries to approve the request Risk analysis is setup as a mandatory task and when the RA is performed the system takes the default "ALL" and errors out, when you choose a specific system and perform you get the required results without any failure. Below is the java dump for the error.
    Please let me know if I have missed anything?
    Line: -
    2011-03-09 10:16:11,264 [SAPEngine_Application_Thread[impl:3]_28] ERROR java.lang.VerifyError: com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;
    java.lang.VerifyError: com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.execRiskAnalysis(RiskAnalysisEJB53DAO.java:305)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:277)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:419)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.determineRisks(RiskAnalysisEJB53DAO.java:527)
         at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:103)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1108)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:335)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:112)
         at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:295)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:219)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    2011-03-09 10:16:11,278 [SAPEngine_Application_Thread[impl:3]_28] ERROR Exception during EJB call, Ignoring and trying Webservice Call
    com.virsa.ae.service.ServiceException: Exception in getting the results from the EJB service : com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:295)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:419)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.determineRisks(RiskAnalysisEJB53DAO.java:527)
         at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:103)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1108)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:335)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:112)
         at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:295)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:219)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Caused by:
    java.lang.VerifyError: com/virsa/cc/xsys/ejb/RiskAnalysis.execRiskAnalysis(Lcom/virsa/cc/xsys/webservices/dto/WSRAInputParamDTO;)Lcom/virsa/cc/xsys/webservices/dto/RAResultDTO;
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.execRiskAnalysis(RiskAnalysisEJB53DAO.java:305)
         at com.virsa.ae.service.sap.RiskAnalysisEJB53DAO.getViolations(RiskAnalysisEJB53DAO.java:277)
         ... 28 more
    2011-03-09 10:19:32,401 [SAPEngine_Application_Thread[impl:3]_28] ERROR com.virsa.ae.core.BOException: EXCEPTION_FROM_THE_SERVICERisk Analysis failed
    com.virsa.ae.core.BOException: EXCEPTION_FROM_THE_SERVICERisk Analysis failed
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:199)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doRiskAnalysis(RiskAnalysisAction.java:1108)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.doAnalysis(RiskAnalysisAction.java:335)
         at com.virsa.ae.accessrequests.actions.RiskAnalysisAction.execute(RiskAnalysisAction.java:112)
         at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:295)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:431)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
         at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:461)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:219)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    Caused by:
    com.virsa.ae.service.ServiceException: EXCEPTION_FROM_THE_SERVICERisk Analysis failed
         at com.virsa.ae.service.sap.RiskAnalysisWS53DAO.determineRisks(RiskAnalysisWS53DAO.java:587)
         at com.virsa.ae.service.sap.RiskAnalysis53DAO.determineRisks(RiskAnalysis53DAO.java:119)
         at com.virsa.ae.accessrequests.bo.RiskAnalysisBO.findViolations(RiskAnalysisBO.java:182)
         ... 24 more
    Edited by: Angara Rao on Mar 9, 2011 5:15 PM

  • How to verify Risk Analysis done for CUP request?

    We are on GRC 5.3 SP 13.
    Is there a way to verify whether a Risk Analysis was performed during a stage for a CUP request?
    We have a CUP request that should have generated a SOD Risk when it was processed.  However the closed request shows no risk or mitigations on it.  The approvers say they ran a Risk Analysis, and the workflow stage does have that set as mandatory.  Also, you do get SODs if you run a User Analysis for this userid in RAR directly, so it looks like the request should have had them also.
    Is there any way to verify whether a Risk Analysis was actually performed in the CUP request workflow stage?
    At this point I don't know if this is a problem with the CUP Risk Analysis, or if the user just didn't run one and the system let that  slip thru somehow.
    Thanks.

    I bellieve you can log into RAR>RAR Debugger>View Server Log>You can search on Analysis.  If your are getting any errors they will also show up here. 
    Example: 
    INFO: Foreground : Analysis starts:
    Mar 9, 2012 3:44:23 PM com.virsa.cc.xsys.meng.ObjAuthMatcher <init>
    FINEST: ObjAuthMatcher constructed: 0ms, #singles=11, #ranges=0, #super=0
    Mar 9, 2012 3:44:23 PM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
    INFO: Foreground : Analysis done: 55550000 elapsed time: 49 ms
    Mar 9, 2012 3:44:23 PM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
    INFO: Foreground : 1 out of 1 (100%) done
    Mar 9, 2012 3:44:23 PM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
    INFO: Foreground : All Analysis done,  elapsed time: 64 ms , memory usage: free=782M, total=2048M
    Mar 9, 2012 3:44:23 PM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis

  • Risk Analysis fails -  role does not exist or has no authorizations

    Dear all,
    We have added our productive client to the ERP Logical system.
    Then we extracted static and object data from backend and uploaded it to AC.
    We are not able to preform an analasys.
    On role level we get the error message: Warning: ZBC_ALL does not exist or has no authorizations
    When checking in debugger we do find autorizations!
    Actions:12
    LAS     2     ZBC_ALL     ZBC_ALL     T-LV210004     S00     
    LAS     2     ZBC_ALL     ZBC_ALL     T-LV210004     SBWP     
    LAS     2     ZBC_ALL     ZBC_ALL     T-LV210004     SM35     
    LAS     2     ZBC_ALL     ZBC_ALL     T-LV210004     SM36     
    LAS     2     ZBC_ALL     ZBC_ALL     T-LV210004     SMXX     
    LAS     2     ZBC_ALL     ZBC_ALL     T-LV210004     SO01     
    LAS     2     ZBC_ALL     ZBC_ALL     T-LV210004     SP02     
    LAS     2     ZBC_ALL     ZBC_ALL     T-LV210004     SU3     
    LAS     2     ZBC_ALL     ZBC_ALL     T-LV210004     SU51     
    LAS     2     ZBC_ALL     ZBC_ALL     T-LV210004     SU52     
    LAS     2     ZBC_ALL     ZBC_ALL     T-LV210004     SU53     
    LAS     2     ZBC_ALL     ZBC_ALL     T-LV210004     SU56
    Objects/AuthKeys:9
    LAS     ZBC_ALL     2     ZBC_ALL     S_BTCH_ADM||BTCADMIN     15     1     4     *          false
    LAS     ZBC_ALL     2     ZBC_ALL     S_WFAR_OBJ||ACTVT     36     1     22     03          false
    LAS     ZBC_ALL     2     ZBC_ALL     S_ADMI_FCD||S_ADMI_FCD     8     1     1     ' '          false
    LAS     ZBC_ALL     2     ZBC_ALL     S_DATASET||ACTVT     21     1     8     34          false
    LAS     ZBC_ALL     2     ZBC_ALL     S_DATASET||ACTVT     21     1     8     33          false
    LAS     ZBC_ALL     2     ZBC_ALL     S_DEVELOP||ACTVT     1     1     9     03          false
    LAS     ZBC_ALL     2     ZBC_ALL     S_BDC_MONI||BDCAKTI     48     1     2     DELE          false
    LAS     ZBC_ALL     2     ZBC_ALL     S_BDC_MONI||BDCAKTI     48     1     2     FREE          false
    LAS     ZBC_ALL     2     ZBC_ALL     S_BDC_MONI||BDCAKTI     48     1     2     LOCK          false
    LAS     ZBC_ALL     2     ZBC_ALL     S_BDC_MONI||BDCAKTI     48     1     2     REOG          false
    LAS     ZBC_ALL     2     ZBC_ALL     S_BDC_MONI||BDCAKTI     48     1     2     IMPO          false
    LAS     ZBC_ALL     2     ZBC_ALL     S_BDC_MONI||BDCAKTI     48     1     2     EXPO          false
    LAS     ZBC_ALL     2     ZBC_ALL     S_BDC_MONI||BDCAKTI     48     1     2     AONL          false
    LAS     ZBC_ALL     2     ZBC_ALL     S_BDC_MONI||BDCAKTI     48     1     2     ABTC          false
    LAS     ZBC_ALL     2     ZBC_ALL     S_OC_ROLE||OFFADMI     37     1     14     *          false
    LAS     ZBC_ALL     2     ZBC_ALL     S_PROGRAM||P_GROUP     5     2     17     *          false
    LAS     ZBC_ALL     2     ZBC_ALL     S_PROGRAM||P_ACTION     5     1     17     VARIANT          false
    LAS     ZBC_ALL     2     ZBC_ALL     S_PROGRAM||P_ACTION     5     1     17     SUBMIT          false
    LAS     ZBC_ALL     2     ZBC_ALL     S_PROGRAM||P_ACTION     5     1     17     BTCSUBMIT          false
    LAS     ZBC_ALL     2     ZBC_ALL     S_C_FUNCT||CFUNCNAME     12     2     7     *          false
    LAS     ZBC_ALL     2     ZBC_ALL     S_C_FUNCT||ACTVT     12     1     7     16          false
    Total:21 lines
    Total:9 Auth Key Map (key=PG) entries
    Total: 9 Obj Map (key=AK) entries
    What could cause the problem?
    Fast respons = karma
    Kind Regards,
    Vit

    Hi Vit,
    Did you run any job after you added one system to logical systems.
    Please import role : ZBC_ALL   through incremental role sync job for the system you have entered in ERP logical landscape .
    Once it is completed , then schedule batch risk analysis Job for this role.
    Then schedule Management report update .
    run Role Level analysis again and check .
    Thanks
    Jasmine

Maybe you are looking for

  • Is it possible to set a default Calendar in iCal?

    I use a calender that is served by Kerio. I want to set that as the default, so that when I create a new entry (as in Apple-N) it uses the set calendar, and not the first one in the list in iCal, which is a local file. I cannot delete the local ical

  • Bex Report issue - transaction data of type Char not dispalyed complete

    Hi BI Expers , I have one issue related to Bex reports here I have complete data loaded in DSO , there is one field Job Title which is having a length of 60 char . When I am executing the report in Bex Analyzer , the value for Job Title is getting tr

  • Double clicking on an Icon to display a frame....

    Hi! I have an icon whereby when double clicked on should display a frame. To display the icon, I have it as an ImageIcon placed on a label, which works fine. But my problem now is what kind of listener can I add to this label, if any that will cause

  • IPod Replacement Program, incomplete Address?

    Hi, I submitted a incomplete address to apple, therefore I think that might be why UPs could not successfully deliver the empty box to my house, what do I do, call Apple's support? or is there any other way I can correct my home address? The empty bo

  • I am now "Oracle Database 11g Administrator Certified Associate"

    Hi after very hard work I am now Oracle Database 11g Administrator Certified Associate. I attended courses (Admin I and SQL Fundamentals) 3 years ago. My Oracle knowhow is only the scope OCA 11g and have no Java know-how. What should I do next? - 1Z0