No result /report when weu00B4re running a risk analysis in background

Dear forum,
We are running several risk analysis in background (from configuration tab) and we cannot see any result
in the column called "result". However, when we run a offline analysis (from informer tab) we can see that the column "result" is containing a file.
Hope you can help us.
Thanks in advance.

Running risk analysis in background from the configuration tab does not produce a report by design.  This background job is really just performing a system maintenence activity and is not intended for report generation.  This background job preps data for performing offline analysis as well as the underlying data that supports the management reports in the informer tab (among other things).  Generally, anything in the configuration tab is system maintenance related.
It sounds like you're attempting to perform typical analysis of end user access, not system maintenance activities.  The informer tab is what you need to be using to perform the analysis.
Within the informer tab, whether you choose to perform online analysis or offline analysis, a report result is always generated.  In my experience, there has not been a compelling reason to use offline analysis capabilities within the informer tab.  Online analysis (real-time analysis of the SAP system rather than the offline data from the last configuration tab background risk analysis) is naturally always current, which is a plus.

Similar Messages

  • Faield to run Batch Risk Analysis BG JOB in RAR

    Dear Expert,
    While doing batch risk analysis (Including all User/Role/Profile  Action and Permission level analysis with Management Report), often we are getting the following error , that we found from the log.
    Feb 7, 2009 8:32:23 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine riskAnalysis
    WARNING:  Job ID:188 : Failed to run Risk Analysis
    java.lang.Exception: Cannot extract data from system (ECQCLNT360); for more details, refer to ccappcomp.n.log
         at com.virsa.cc.xsys.meng.MatchingEngine.matchActRisks(MatchingEngine.java:118)
         at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java:1104)
         at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:297)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchRiskAnalysis(BatchRiskAnalysis.java:1047)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1369)
         at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:402)
         at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:264)
         at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:240)
         at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:80)
         at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:436)
         at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1225)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
         at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         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:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Feb 7, 2009 8:32:23 AM com.virsa.cc.xsys.bg.BatchRiskAnalysis performBatchRiskAnalysis
    WARNING: Error: while executing BatchRiskAnalysis for JobId=188 and object(s):T-EQ462534: Skipping error to continue with next object: Cannot extract data from system (ECQCLNT360); for more details, refer to ccappcomp.n.log
    Feb 7, 2009 8:32:23 AM com.virsa.cc.xsys.bg.BgJob updateJobHistory
    FINEST: --- @@@@@@@@@@@ Updating the Job History -
    2@@Msg is Error while executing the Job for Object(s) :T-EQ462534:Cannot extract data from system (ECQCLNT360); for more details, refer to ccappcomp.n.log
    Feb 7, 2009 8:32:23 AM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert
    INFO: -
    Background Job History: job id=188, status=2, message=Error while executing the Job for Object(s) :T-EQ462534:Cannot extract data from system (ECQCLNT360); for more details, refer to ccappcomp.n.log
    Feb 7, 2009 8:32:23 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine riskAnalysis
    INFO:  Job ID:188 : Exec Risk Analysis
    Feb 7, 2009 8:32:23 AM com.virsa.cc.xsys.riskanalysis.AnalysisEngine performActPermAnalysis
    INFO:  Job ID:188 : Analysis starts: T-EQ462535
    Feb 7, 2009 8:32:24 AM com.virsa.cc.comp.VirsaXSR3_02Interface execute
    WARNING: VIRSAXSR3_02: Cannot execute BAPI AuthForProf
    com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException
         at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:107)
         at com.virsa.cc.comp.VirsaXSR3_02Interface.execute(VirsaXSR3_02Interface.java:279)
         at com.virsa.cc.comp.wdp.InternalVirsaXSR3_02Interface.execute(InternalVirsaXSR3_02Interface.java:1341)
         at com.virsa.cc.comp.wdp.InternalVirsaXSR3_02Interface$External.execute(InternalVirsaXSR3_02Interface.java:1376)
         at com.virsa.cc.comp.BackendAccessInterface.executeBAPIModel(BackendAccessInterface.java:3393)
         at com.virsa.cc.comp.BackendAccessInterface.execBAPI(BackendAccessInterface.java:407)
         at com.virsa.cc.comp.BackendAccessInterface.executeBAPI(BackendAccessInterface.java:302)
         at com.virsa.cc.comp.wdp.InternalBackendAccessInterface.executeBAPI(InternalBackendAccessInterface.java:4227)
         at com.virsa.cc.comp.wdp.InternalBackendAccessInterface$External.executeBAPI(InternalBackendAccessInterface.java:4692)
         at com.virsa.cc.dataextractor.bo.DataExtractorSAP.getObjActions(DataExtractorSAP.java:213)
         at com.virsa.cc.dataextractor.bo.DataExtractorSAP.getObjActions(DataExtractorSAP.java:105)
         at com.virsa.cc.xsys.meng.MatchingEngine.getObjActions(MatchingEngine.java:770)
         at com.virsa.cc.xsys.meng.MatchingEngine.matchActRisks(MatchingEngine.java:112)
         at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java:1104)
         at com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:297)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchRiskAnalysis(BatchRiskAnalysis.java:1047)
         at com.virsa.cc.xsys.bg.BatchRiskAnalysis.performBatchSyncAndAnalysis(BatchRiskAnalysis.java:1369)
         at com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:402)
         at com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:264)
         at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:240)
         at com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:80)
         at com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:436)
         at com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1225)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
         at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         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:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Could you please let me know why does it happening ? During installation of the system I have done Performance Optimization according SAP Notes. Instead of this again and again we are facing this problem.
    But If I do Batch Risk Analysis One by One, let say First we have done User Analysis with Mgmt Report next has been done Role Analysis then profile, according to that we got the successfull result.
    Thanks & Regards
    Pavel Das
    PwC India
    +919874886293

    Dear Alpesh,
    Good to hear you from sdn.
    Yes, It works properly when I have scheduled some of the profile and some of the Roles along with Management Report.
    It does not work when I have shecduled all the Roles and Profile together.
    So what would be your suggestion for Batch Risk Analysis ?
    Thanks
    Pavel

  • RAR: Error message while running role risk analysis.

    Hi All,
             We are implementing RAR 5.3. When running permission level risk analysis we get the following error message:
    "Error while executing the Job:Cannot assign a blank-padded string to host variable 1.u201D
    This happens only at permission level for just one single role and for all the composite roles that contain this one.
    The rules were generated without any issue and we cannot find anything unusual on that particular single role.
    Any ideas of what could be the cause of this error?

    Hi Iliya:
              Please find below the job log with the detailed error description:
    Mon Dec 15 10:06:37 GMT-02:00 2008 : -----------------------Scheduling Job =>233---------------------------------------------------------------
    Mon Dec 15 10:06:37 GMT-02:00 2008 : --- Starting Job ID:233 (RISK_ANALYSIS_ADHOC) - mm:user10
    Mon Dec 15 10:06:37 GMT-02:00 2008 : ----------- Background Job History: job id=233, status=1, message=mm:user10 started
    Mon Dec 15 10:06:37 GMT-02:00 2008 :  Job ID:233 : Exec Risk Analysis
    Mon Dec 15 10:06:37 GMT-02:00 2008 : Start Analysis Engine->Risk Analysis .....  memory usage: free=1571M, total=1962M
    Mon Dec 15 10:06:38 GMT-02:00 2008 : Rule Loader Syskey => *
    Mon Dec 15 10:06:38 GMT-02:00 2008 : No of Systems=1
    Mon Dec 15 10:06:51 GMT-02:00 2008 : Action rules cache loaded: memory used in cache=56M, free=1512M, total=1962M
    Mon Dec 15 10:06:51 GMT-02:00 2008 :  Job ID:233 : Rules loaded,  elapsed time: 13694 ms
    Mon Dec 15 10:06:57 GMT-02:00 2008 :  Job ID:233 :
    Mon Dec 15 10:06:57 GMT-02:00 2008 :  Job ID:233 : Analysis starts: MM:USER10
    Mon Dec 15 10:07:16 GMT-02:00 2008 : Auth Map cache reloaded successfully
    Mon Dec 15 10:07:32 GMT-02:00 2008 : Cannot assign a blank-padded string to host variable 1.com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:85)
    com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:124)
    com.sap.sql.types.VarcharResultColumn.setString(VarcharResultColumn.java:66)
    com.sap.sql.jdbc.common.CommonPreparedStatement.setString(CommonPreparedStatement.java:511)
    com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.setString(PreparedStatementWrapper.java:355)
    com.virsa.cc.xsys.util.ObjTextReader.lookupByKey(ObjTextReader.java:353)
    com.virsa.cc.xsys.util.ObjTextReader.getFieldValueDesc(ObjTextReader.java:261)
    com.virsa.cc.xsys.riskanalysis.AnalysisEngine.insertPermReportLines(AnalysisEngine.java:2286)
    com.virsa.cc.xsys.riskanalysis.AnalysisEngine.outputPermissionViolation(AnalysisEngine.java:1858)
    com.virsa.cc.xsys.riskanalysis.AnalysisEngine.performActPermAnalysis(AnalysisEngine.java:1182)
    com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:243)
    com.virsa.cc.xsys.riskanalysis.AnalysisEngine.riskAnalysis(AnalysisEngine.java:207)
    com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:305)
    com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:183)
    com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:154)
    com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:81)
    com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:434)
    com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1223)
    com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
    com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
    com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:480)
    com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
    com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
    com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
    com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
    com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
    com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
    com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
    com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
    com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
    com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    java.security.AccessController.doPrivileged(Native Method)
    com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Mon Dec 15 10:07:32 GMT-02:00 2008 : Cannot assign a blank-padded string to host variable 1.com.virsa.cc.xsys.bg.BgJob.runJob(BgJob.java:309)
    com.virsa.cc.xsys.bg.BgJob.run(BgJob.java:183)
    com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.scheduleJob(AnalysisDaemonBgJob.java:154)
    com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob.start(AnalysisDaemonBgJob.java:81)
    com.virsa.cc.comp.BgJobInvokerView.wdDoModifyView(BgJobInvokerView.java:434)
    com.virsa.cc.comp.wdp.InternalBgJobInvokerView.wdDoModifyView(InternalBgJobInvokerView.java:1223)
    com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
    com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
    com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:480)
    com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
    com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
    com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
    com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
    com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
    com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
    com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
    com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
    com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
    com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
    javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    java.security.AccessController.doPrivileged(Native Method)
    com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
    com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Mon Dec 15 10:07:32 GMT-02:00 2008 : Job ID: 233 Status: Error
    Mon Dec 15 10:07:32 GMT-02:00 2008 : ----------- Background Job History: job id=233, status=2, message=Error while executing the Job:Cannot assign a blank-padded string to host variable 1.
    Mon Dec 15 10:07:32 GMT-02:00 2008 : -----------------------Complted Job =>233---------------------------------------------------------------
    Regards.
    Leandro.

  • Org Rule anlaysis when performing mitigation from risk analysis report do not mitigate the user from management summary report message!

    Hi,
    When in the User Level>Mitigation screen this comment appears  (*). When taking the path to  ‘summary’(a) or ‘detail’ (b) doesn't change when we select the button  MITIGATE RISK (**).  What was the intent of the below message?
    What is the intent of the message ?

    Hi Pranjal,
    please see note: http://service.sap.com/sap/support/notes/1972382
    Regards,
    Alessandro

  • Risk analysis Report Error in GRC AC 10.0

    Dear GRC,
    I had problem with Risk analysis Report in GRC Access Request form
    When i run the Risk analysis report on Action Level , Permission Level , Critical Action Level and Critical Permission Level then report showing as "No Violations" but if i run the Risk analysis report only on Critical Action Level and Critical Permission Level then report showing too many Violations.
    I maintained Action Level , Permission Level , Critical Action Level and Critical Permission Level as default risk analysis type in SPRO Configuration Parameters settings.
    i am not understanding why system behaves like this. Could you please help me on this.
    System Details : GRC AC 10.0 , SP-12
    Thanks a lot for swift response.
    Best Regards,
    RK

    Hi GRC Team,
    Please help me on this. I am waiting for your replay.
    Regards,
    KR

  • Ad-hoc Risk Analyses returning incorrect Risk Levels against Risks

    We have recently made changes to our ruleset and uploaded them in Development and Production. We have noticed whilst running Ad-Hoc Risk Analyses that the Production system is showing Risks as Medium when they are either critical or high. For example Risk ZA12 is a High risk but the Risk analyses is showing this Risk as a Medium risk.However in Develpment risks are displaying as expected when we run Adhoc risk analyses. We have deleted previous ruleset, uploaded the new ruleset, generated rules and run all the Sync jobs to no avail. In Addition i have gone into NWBC and double checked if the Ruleset had been generated (Rule Setup>Generated Rules>Access Rule Summary) and i can confirm that the risks are appearing as expected here). Oddly even the Management Reports (Reports and Analytics) seem to have the correct Risk Ratings against the violations.
    Strange!

    Hi Kevin
    Many thanks for your post, we did run a full BRA but no luck unfortunately. Some Risks still reporting as Medium when they should be Critical or High. Oddly it is reporting correctly against some risks just not for all!
    Cheers
    Hussain

  • 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

  • CC Risk Analysis.

    Hi,
    I am having problem in doing risk analysis in CC. I have created required JCO connection to backend system.
    When i run the risk analysis on a particular system. Job show status is completed, but i get message "No match/conflict found". This is not at all possible.
    When go through the log, i find one line saying "FINEST: No action rules for * "
    I am not able to crack this problem.
    Please suggest.
    Thanks & Regards,
    Pravin

    Hi,
    it is possible to have funcitons against multiple systems. I would have expected it to overwrite tables only if you upload the other files - functions BP and functions file, but loading only the funct act. and func permission file against another connected (for which we don`t have entries in the tables yet) should have worked just fine in your case. I did this before, maybe we`re missing something.
    Are you sure you loaded only those files and not other files?
    There`s one other way to do this but you have to be aware what`s already in the tables.
    There are two tables that have to be edited. VIRSA_CC_FUNCACT and VIRSA_CC_FUNCPRM.
    You can download those tables, see the structure and add the entries for the missing systems, then upload them again. This method though, requres a lot endeavour and precision. Maybe it`ll be better to just load everything again from the beggining and this time not to miss to load the functions against all systems. If you go for this you might hit the problem of entries that are already in the system and the new upload won`t work because of that. Then you can erase the content of all tables (DB guys know how to do it) and then load everything from scratch.
    Your choice depends on where you are with the implementation.
    I hope that helps.
    Regards,
    Iliya

  • Adding Timestamp to Report when it was Last Run.

    This is a general Reporting requirement we need to include in some of our Reports.
    Is there any way we can display "Timestamp" anywhere in report indicating when it ran sucessfully priviously.
    If it is not possible please let me know how can I add current timestamp in report when I run it.
    Here is what I did for now:
    I have added 'Started Time' option as 'Display Date and Time' under Title Edit View.
    Please let me know if there is any other way to put timestamps for your report.
    Regards,
    Abhay

    Hi,
    You can also put this in a column as and use the 'NOW()' function. No matter how you do this though it will always be based on the server locale and not the users regional locale which is a bit of a shame and usually renders this useless.
    Thanks
    Oli @ Innoveer

  • RAR Risk Analysis Issue in Background Mode - "Failed to Display Result"

    Hi,
    I have strange problem in RAR.
    When I run risk analysis for 20 users in background mode, the job got successful but the spool file is empty. But at the bottom of page there is a message:  "Failed to Display Result".
    The Job log is showing the following message couple of times:
    WARNING: ./virsa/bgJobSpool/19.i (No such file or directory)
    java.io.FileNotFoundException: ./virsa/bgJobSpool/19.i (No such file or directory)
         at java.io.FileInputStream.open(Native Method)
         at java.io.FileInputStream.<init>(FileInputStream.java:129)
         at java.io.FileInputStream.<init>(FileInputStream.java:89)
         at java.io.FileReader.<init>(FileReader.java:62)
    But When I try to run for few users (like 6 memebrs where selection criteria is AUDIT*) in same way, the spool details got displayed this time. But the log is showing strange error messages this time:
    Nov 15, 2010 3:53:53 PM com.virsa.cc.common.util.ExceptionUtil logError
    SEVERE: null
    java.lang.NullPointerException
         at com.virsa.cc.comp.wdp.IPublicBackendAccessInterface$IAuthForUserInputElement.wdGetObject(IPublicBackendAccessInterface.java)
         at com.sap.tc.webdynpro.progmodel.context.NodeElement.getAttributeAsText(NodeElement.java:888)
    Nov 15, 2010 3:53:55 PM com.virsa.cc.dataextractor.bo.DataExtractorSAP getObjPermissions
    FINEST: getObjPermissions: elapsed time=1436ms
    Nov 15, 2010 3:53:55 PM com.virsa.cc.common.message.util.MessagingHelper getMessage
    INFO:
    ********msg: 'com.virsa.cc.common.message.dao.dto.MessageDTO@34d834d8'
    Any ideas please?

    Hi Alpesh,
    You are correct. The issue is due to multi node environment.
    But when I tried to define a custom spool folder path: usr/sap/<SID>/<Instance No>/log/virsa/bgJobSpool (in RAR - Miscellaneous - spool files location for background jobs) & run the risk analysis report in background mode, still RAR is saving the spool files in default location only.
    Can you suggest me if I am wrongly defining the location of folder?
    Should we define the complete location of the folder i.e starting with drive letter or path starting with user/* is sufficient?
    Regards,
    Dasarad

  • Role Based Risk Analysis Report

    Hello All,
    When I executed the Risk Analysis report for a role with SOD Risk Level = ALL and Report type = SOD at Authorization Object level, the results come back as "NO CONFLICT FOUND".  this is the correct response.
    However, I executed the Risk Analysis report for the same role with SOD Risk Level = HIGH and Report type = SOD at Authorization Object level, the results come back SOD conflicts based on the conflicting transactions.  Is there a bug with analyzing roles using this option?
    Also, when I click on the Detail Report button, I received object data that does not appear correct.
    Please Help.  Thanks.
    Edited by: Michael Johnson on Apr 8, 2009 8:54 PM

    Hi Babiji,
    Are you using any specific tools for SOD's? If you are using GRC tool, then it can be done using compliance calibrator Role level Risk analysis.In addition to what Sneha has said,
    To find out the conflicting roles in CC version 5.2 the path is INFORMER->Risk Analysis->Role level.In Virsa 4.0 you have the option of carrying out risk anaysis at role level by executing the t-code /N/VIRSA/ZVRAT.
    In section Analysis type, choose Roles and enter the list of roles.
    In section SOD Risk level, choose the appropriate risk.
    Then choose the appropriate report type and report format before executing it.
    This will display all the roles with the levels of risk associated with it and then you can mitigate these as per your organizational policies & procedures.
    Thanks,
    Saby..

  • AC 5.3 RAR - combined risk analysis reports for regular auth. and SPM auth.

    Dear All,
    we have users that have regular day-today authorization and also FF authorization.
    Does the Batch Risk Analysis takes into account both authorizations when doing the risk analysis for those users ? will we see it in the reports ?
    Thanks
    Yudit

    ok, so basically the answer is no, in the RAR components we do not have risk analysis for the combinations of the roles assigned to the user and to his FF ID.
    in that case, at what stage does the system checks for those combined risks ?
    is it checked when we manage the risk analysis phase in the CUP request that is asking to assign the FF ID to the user ?
    thanks
    Yudit

  • GRC Risk analysis reports are not checking all possible risk conflicts set up in the rule set that lead to risks.

    Dear All,
    After running the risk analysis it shows only the first conflict for a risk in the rule set (Rule ID 0001). We have already Generated SOD ruleset. Also during migration from 5.3 to AC10.1 all the rulesets were imported properly.
    What could be reason??
    Thanks for your help.
    Regards,
    Abhisshek

    Abhisshek,
    there is already a thread with the same question:  Dear all I only get result for one rule id and not with others what should be an issue?
    Regards,
    Alessandro

  • Running Risk analysis at User Level(CC)

    Hi
    Please Clear my query, wat is the difference between running the risk analysis at userlevel Violation count by Risk and Violation count by Permission.
    violation count by Permission, the total number of violations are 377,569.
    Violation count by Risk,the total number of violations are 11,716.
    Thanks & Regards

    Hi Karuna,
    When you perform Risk Analysis at User level and choose violation count by Permission/Risk. Here are the details of each analysis:
    1. Violation Count by Risk
    This analysis will display the count of how many SOD risks associated with the users existing in each business process like FI, HR, MM, PR, SD.
    It will display as a bar graph or pie chart. If you choose each of the business processes and drill down to the particular SOD risk,P001 then you can display how many users have that risk, P001
    2. Violation Count by Permission
    This analysis will display the count of SOD violations at the action/permission level associated with the users existing in each business process.
    If you choose the conflicting functions inside each SOD risk, and then expand on the permission tab you will understand why the huge number of violations it is showing.
    In the Risk information screen, in Conflicting Functions, click the AP02 u2013 Process Vendor Invoices link to display the SAP transaction codes and the authorization objects. There are 26 different transactions in SAP to Process Vendor Invoices and another 185 authorization object values u2013 all come preconfigured out of the box.
    Choose the Permission tab. Expand Action F-42. Open an authorization object to show field values. By looking at all possible permutations of actions/permissions of one business function with all actions/permissions of the second business function, you can understand how the system arrives at the number of violations.
    Hope this will help you understand better.
    Regards,
    Kiran Kandepalli.

  • GRC ERM not running a risk anlaysis

    Hey,
    I'm having some trouble getting ERM to run a risk analysis... RAR and ERM are sitting on the same server. However, I still have a user ID with RAR and ERM admin rights,, but ERM is not communicating properly with RAR. ERM is also not showing an error in the job log.I keep attempting to get ERM to run a risk analysis, but it seems like its running in a loop. Has anyone else ran into this issue? Here is the log.
    2010-11-15 00:04:49,494 [Thread-98] DEBUG #@#@#@# Mon Nov 15 00:04:49 CST 2010 - Running BackgroundJobScheduler  #@#@#@#
    2010-11-15 00:04:49,494 [Thread-98] DEBUG  Name of scheduler is 7892352
    2010-11-15 00:04:49,494 [Thread-98] DEBUG Number of schedular Threads ========== 3
    2010-11-15 00:04:49,494 [Thread-98] DEBUG getJobsTobeScheduled query ======  SELECT  A.JOB_ID JOBID,A.TASK_ID,A.JOB_DESC,A.START_DATE,A.END_DATE,A.NEXT_IN_DATE,A.CLUSTER_NODE, A.STATUS_ID,A.JOB_TYPE,A.WEEK_DAYS,A.REC_INTERVAL,A.ACTIVE_RECORD,A.USER_ID, B.TASK_DESC,B.TASK_HNDLR, B.TASK_HNDLR_TYP,C.STATUS_DESC  FROM  VT_GBL_SCHEDULER A, VT_GBL_TASKS B, VT_GBL_JBSTCODES C  WHERE  A.TASK_ID = B.TASK_ID  AND A.STATUS_ID = C.STATUS_ID  AND A.ACTIVE_RECORD IN ('1','YES','yes','Y','y')  AND C.STATUS_DESC IN ('Ready','Completed','Error','Aborted','Waiting')  AND A.NEXT_IN_DATE <= ?  AND B.LNGID = 1  ORDER BY JOBID
    2010-11-15 00:04:49,494 [Thread-98] DEBUG  scheduler is checking NextInDate with 2010-11-15 00:04:00.0
    2010-11-15 00:04:49,494 [Thread-98] DEBUG Jobs list Size ==== 0
    2010-11-15 00:04:49,494 [Thread-98] DEBUG Thread ===== Thread[Thread-98,5,SAPEngine_Application_Thread[impl:3]_Group]
    2010-11-15 00:04:49,494 [Thread-98] DEBUG Thread  Name===== Thread-98
    2010-11-15 00:04:49,494 [Thread-98] DEBUG Thread interruptedfalse
    2010-11-15 00:05:49,508 [Thread-98] DEBUG #@#@#@# Mon Nov 15 00:05:49 CST 2010 - Running BackgroundJobScheduler  #@#@#@#
    2010-11-15 00:05:49,508 [Thread-98] DEBUG  Name of scheduler is 7892352
    2010-11-15 00:05:49,508 [Thread-98] DEBUG Number of schedular Threads ========== 3
    2010-11-15 00:05:49,508 [Thread-98] DEBUG getJobsTobeScheduled query ======  SELECT  A.JOB_ID JOBID,A.TASK_ID,A.JOB_DESC,A.START_DATE,A.END_DATE,A.NEXT_IN_DATE,A.CLUSTER_NODE, A.STATUS_ID,A.JOB_TYPE,A.WEEK_DAYS,A.REC_INTERVAL,A.ACTIVE_RECORD,A.USER_ID, B.TASK_DESC,B.TASK_HNDLR, B.TASK_HNDLR_TYP,C.STATUS_DESC  FROM  VT_GBL_SCHEDULER A, VT_GBL_TASKS B, VT_GBL_JBSTCODES C  WHERE  A.TASK_ID = B.TASK_ID  AND A.STATUS_ID = C.STATUS_ID  AND A.ACTIVE_RECORD IN ('1','YES','yes','Y','y')  AND C.STATUS_DESC IN ('Ready','Completed','Error','Aborted','Waiting')  AND A.NEXT_IN_DATE <= ?  AND B.LNGID = 1  ORDER BY JOBID
    2010-11-15 00:05:49,508 [Thread-98] DEBUG  scheduler is checking NextInDate with 2010-11-15 00:05:00.0
    2010-11-15 00:05:49,508 [Thread-98] DEBUG Jobs list Size ==== 0
    2010-11-15 00:05:49,508 [Thread-98] DEBUG Thread ===== Thread[Thread-98,5,SAPEngine_Application_Thread[impl:3]_Group]
    2010-11-15 00:05:49,508 [Thread-98] DEBUG Thread  Name===== Thread-98
    2010-11-15 00:05:49,508 [Thread-98] DEBUG Thread interruptedfalse
    2010-11-15 00:06:49,523 [Thread-98] DEBUG #@#@#@# Mon Nov 15 00:06:49 CST 2010 - Running BackgroundJobScheduler  #@#@#@#
    2010-11-15 00:06:49,523 [Thread-98] DEBUG  Name of scheduler is 7892352
    2010-11-15 00:06:49,523 [Thread-98] DEBUG Number of schedular Threads ========== 3
    2010-11-15 00:06:49,523 [Thread-98] DEBUG getJobsTobeScheduled query ======  SELECT  A.JOB_ID JOBID,A.TASK_ID,A.JOB_DESC,A.START_DATE,A.END_DATE,A.NEXT_IN_DATE,A.CLUSTER_NODE, A.STATUS_ID,A.JOB_TYPE,A.WEEK_DAYS,A.REC_INTERVAL,A.ACTIVE_RECORD,A.USER_ID, B.TASK_DESC,B.TASK_HNDLR, B.TASK_HNDLR_TYP,C.STATUS_DESC  FROM  VT_GBL_SCHEDULER A, VT_GBL_TASKS B, VT_GBL_JBSTCODES C  WHERE  A.TASK_ID = B.TASK_ID  AND A.STATUS_ID = C.STATUS_ID  AND A.ACTIVE_RECORD IN ('1','YES','yes','Y','y')  AND C.STATUS_DESC IN ('Ready','Completed','Error','Aborted','Waiting')  AND A.NEXT_IN_DATE <= ?  AND B.LNGID = 1  ORDER BY JOBID
    2010-11-15 00:06:49,523 [Thread-98] DEBUG  scheduler is checking NextInDate with 2010-11-15 00:06:00.0
    2010-11-15 00:06:49,523 [Thread-98] DEBUG Jobs list Size ==== 0
    2010-11-15 00:06:49,523 [Thread-98] DEBUG Thread ===== Thread[Thread-98,5,SAPEngine_Application_Thread[impl:3]_Group]
    2010-11-15 00:06:49,523 [Thread-98] DEBUG Thread  Name===== Thread-98
    2010-11-15 00:06:49,523 [Thread-98] DEBUG Thread interruptedfalse
    2010-11-15 00:07:49,537 [Thread-98] DEBUG #@#@#@# Mon Nov 15 00:07:49 CST 2010 - Running BackgroundJobScheduler  #@#@#@#
    2010-11-15 00:07:49,537 [Thread-98] DEBUG  Name of scheduler is 7892352
    2010-11-15 00:07:49,537 [Thread-98] DEBUG Number of schedular Threads ========== 3
    2010-11-15 00:07:49,537 [Thread-98] DEBUG getJobsTobeScheduled query ======  SELECT  A.JOB_ID JOBID,A.TASK_ID,A.JOB_DESC,A.START_DATE,A.END_DATE,A.NEXT_IN_DATE,A.CLUSTER_NODE, A.STATUS_ID,A.JOB_TYPE,A.WEEK_DAYS,A.REC_INTERVAL,A.ACTIVE_RECORD,A.USER_ID, B.TASK_DESC,B.TASK_HNDLR, B.TASK_HNDLR_TYP,C.STATUS_DESC  FROM  VT_GBL_SCHEDULER A, VT_GBL_TASKS B, VT_GBL_JBSTCODES C  WHERE  A.TASK_ID = B.TASK_ID  AND A.STATUS_ID = C.STATUS_ID  AND A.ACTIVE_RECORD IN ('1','YES','yes','Y','y')  AND C.STATUS_DESC IN ('Ready','Completed','Error','Aborted','Waiting')  AND A.NEXT_IN_DATE <= ?  AND B.LNGID = 1  ORDER BY JOBID
    2010-11-15 00:07:49,537 [Thread-98] DEBUG  scheduler is checking NextInDate with 2010-11-15 00:07:00.0
    2010-11-15 00:07:49,537 [Thread-98] DEBUG Jobs list Size ==== 0
    2010-11-15 00:07:49,537 [Thread-98] DEBUG Thread ===== Thread[Thread-98,5,SAPEngine_Application_Thread[impl:3]_Group]
    2010-11-15 00:07:49,537 [Thread-98] DEBUG Thread  Name===== Thread-98
    2010-11-15 00:07:49,537 [Thread-98] DEBUG Thread interruptedfalse
    2010-11-15 00:08:49,552 [Thread-98] DEBUG #@#@#@# Mon Nov 15 00:08:49 CST 2010 - Running BackgroundJobScheduler  #@#@#@#
    2010-11-15 00:08:49,552 [Thread-98] DEBUG  Name of scheduler is 7892352
    2010-11-15 00:08:49,552 [Thread-98] DEBUG Number of schedular Threads ========== 3
    2010-11-15 00:08:49,552 [Thread-98] DEBUG getJobsTobeScheduled query ======  SELECT  A.JOB_ID JOBID,A.TASK_ID,A.JOB_DESC,A.START_DATE,A.END_DATE,A.NEXT_IN_DATE,A.CLUSTER_NODE, A.STATUS_ID,A.JOB_TYPE,A.WEEK_DAYS,A.REC_INTERVAL,A.ACTIVE_RECORD,A.USER_ID, B.TASK_DESC,B.TASK_HNDLR, B.TASK_HNDLR_TYP,C.STATUS_DESC  FROM  VT_GBL_SCHEDULER A, VT_GBL_TASKS B, VT_GBL_JBSTCODES C  WHERE  A.TASK_ID = B.TASK_ID  AND A.STATUS_ID = C.STATUS_ID  AND A.ACTIVE_RECORD IN ('1','YES','yes','Y','y')  AND C.STATUS_DESC IN ('Ready','Completed','Error','Aborted','Waiting')  AND A.NEXT_IN_DATE <= ?  AND B.LNGID = 1  ORDER BY JOBID
    2010-11-15 00:08:49,552 [Thread-98] DEBUG  scheduler is checking NextInDate with 2010-11-15 00:08:00.0
    2010-11-15 00:08:49,552 [Thread-98] DEBUG Jobs list Size ==== 0
    2010-11-15 00:08:49,552 [Thread-98] DEBUG Thread ===== Thread[Thread-98,5,SAPEngine_Application_Thread[impl:3]_Group]
    2010-11-15 00:08:49,552 [Thread-98] DEBUG Thread  Name===== Thread-98
    2010-11-15 00:08:49,552 [Thread-98] DEBUG Thread interruptedfalse
    2010-11-15 00:09:49,566 [Thread-98] DEBUG #@#@#@# Mon Nov 15 00:09:49 CST 2010 - Running BackgroundJobScheduler  #@#@#@#
    2010-11-15 00:09:49,566 [Thread-98] DEBUG  Name of scheduler is 7892352
    2010-11-15 00:09:49,566 [Thread-98] DEBUG Number of schedular Threads ========== 3
    2010-11-15 00:09:49,566 [Thread-98] DEBUG getJobsTobeScheduled query ======  SELECT  A.JOB_ID JOBID,A.TASK_ID,A.JOB_DESC,A.START_DATE,A.END_DATE,A.NEXT_IN_DATE,A.CLUSTER_NODE, A.STATUS_ID,A.JOB_TYPE,A.WEEK_DAYS,A.REC_INTERVAL,A.ACTIVE_RECORD,A.USER_ID, B.TASK_DESC,B.TASK_HNDLR, B.TASK_HNDLR_TYP,C.STATUS_DESC  FROM  VT_GBL_SCHEDULER A, VT_GBL_TASKS B, VT_GBL_JBSTCODES C  WHERE  A.TASK_ID = B.TASK_ID  AND A.STATUS_ID = C.STATUS_ID  AND A.ACTIVE_RECORD IN ('1','YES','yes','Y','y')  AND C.STATUS_DESC IN ('Ready','Completed','Error','Aborted','Waiting')  AND A.NEXT_IN_DATE <= ?  AND B.LNGID = 1  ORDER BY JOBID
    2010-11-15 00:09:49,566 [Thread-98] DEBUG  scheduler is checking NextInDate with 2010-11-15 00:09:00.0
    2010-11-15 00:09:49,566 [Thread-98] DEBUG Jobs list Size ==== 0
    2010-11-15 00:09:49,566 [Thread-98] DEBUG Thread ===== Thread[Thread-98,5,SAPEngine_Application_Thread[impl:3]_Group]
    2010-11-15 00:09:49,566 [Thread-98] DEBUG Thread  Name===== Thread-98
    2010-11-15 00:09:49,566 [Thread-98] DEBUG Thread interruptedfalse
    2010-11-15 00:10:49,581 [Thread-98] DEBUG #@#@#@# Mon Nov 15 00:10:49 CST 2010 - Running BackgroundJobScheduler  #@#@#@#
    2010-11-15 00:10:49,581 [Thread-98] DEBUG  Name of scheduler is 7892352
    2010-11-15 00:10:49,581 [Thread-98] DEBUG Number of schedular Threads ========== 3
    2010-11-15 00:10:49,581 [Thread-98] DEBUG getJobsTobeScheduled query ======  SELECT  A.JOB_ID JOBID,A.TASK_ID,A.JOB_DESC,A.START_DATE,A.END_DATE,A.NEXT_IN_DATE,A.CLUSTER_NODE, A.STATUS_ID,A.JOB_TYPE,A.WEEK_DAYS,A.REC_INTERVAL,A.ACTIVE_RECORD,A.USER_ID, B.TASK_DESC,B.TASK_HNDLR, B.TASK_HNDLR_TYP,C.STATUS_DESC  FROM  VT_GBL_SCHEDULER A, VT_GBL_TASKS B, VT_GBL_JBSTCODES C  WHERE  A.TASK_ID = B.TASK_ID  AND A.STATUS_ID = C.STATUS_ID  AND A.ACTIVE_RECORD IN ('1','YES','yes','Y','y')  AND C.STATUS_DESC IN ('Ready','Completed','Error','Aborted','Waiting')  AND A.NEXT_IN_DATE <= ?  AND B.LNGID = 1  ORDER BY JOBID
    2010-11-15 00:10:49,581 [Thread-98] DEBUG  scheduler is checking NextInDate with 2010-11-15 00:10:00.0
    2010-11-15 00:10:49,581 [Thread-98] DEBUG Jobs list Size ==== 0
    2010-11-15 00:10:49,581 [Thread-98] DEBUG Thread ===== Thread[Thread-98,5,SAPEngine_Application_Thread[impl:3]_Group]
    2010-11-15 00:10:49,581 [Thread-98] DEBUG Thread  Name===== Thread-98
    2010-11-15 00:10:49,581 [Thread-98] DEBUG Thread interruptedfalse
    2010-11-15 00:11:49,595 [Thread-98] DEBUG #@#@#@# Mon Nov 15 00:11:49 CST 2010 - Running BackgroundJobScheduler  #@#@#@#
    2010-11-15 00:11:49,595 [Thread-98] DEBUG  Name of scheduler is 7892352
    2010-11-15 00:11:49,595 [Thread-98] DEBUG Number of schedular Threads ========== 3
    2010-11-15 00:11:49,595 [Thread-98] DEBUG getJobsTobeScheduled query ======  SELECT  A.JOB_ID JOBID,A.TASK_ID,A.JOB_DESC,A.START_DATE,A.END_DATE,A.NEXT_IN_DATE,A.CLUSTER_NODE, A.STATUS_ID,A.JOB_TYPE,A.WEEK_DAYS,A.REC_INTERVAL,A.ACTIVE_RECORD,A.USER_ID, B.TASK_DESC,B.TASK_HNDLR, B.TASK_HNDLR_TYP,C.STATUS_DESC  FROM  VT_GBL_SCHEDULER A, VT_GBL_TASKS B, VT_GBL_JBSTCODES C  WHERE  A.TASK_ID = B.TASK_ID  AND A.STATUS_ID = C.STATUS_ID  AND A.ACTIVE_RECORD IN ('1','YES','yes','Y','y')  AND C.STATUS_DESC IN ('Ready','Completed','Error','Aborted','Waiting')  AND A.NEXT_IN_DATE <= ?  AND B.LNGID = 1  ORDER BY JOBID
    2010-11-15 00:11:49,595 [Thread-98] DEBUG  scheduler is checking NextInDate with 2010-11-15 00:11:00.0
    2010-11-15 00:11:49,595 [Thread-98] DEBUG Jobs list Size ==== 0
    2010-11-15 00:11:49,595 [Thread-98] DEBUG Thread ===== Thread[Thread-98,5,SAPEngine_Application_Thread[impl:3]_Group]
    2010-11-15 00:11:49,595 [Thread-98] DEBUG Thread  Name===== Thread-98
    2010-11-15 00:11:49,595 [Thread-98] DEBUG Thread interruptedfalse

    Hello Phillip
    Can we double check the connector that is being used to communicate between system ?
    Kindly check note no : 1136690 - Failed to perform Risk Analysis in ERM.In this note error message is different but still it would good option to double check connector name .
    Also I would like to know which version/Service pack  of GRC you are using .
    I would recommend to Import the latest Initial .XML files into the application.
    Importantly, these .XML files have to be in-SYNC with the Support Pack level of the ERM application installed.
    Example: You have ERM 5.3 SP10, make sure you download the Initial Data files for the same Support Pack, SP10 from SAP Service Market Place (SMP).
    Location on SMP:
    Downloads =>SAP Support Packages =>Entry by Application Group =>SAP Solutions for Governance, Risk and Compliance =>SAP GRC Access Control =>SAP GRC ACCESS CONTROL =>SAP GRC ACCESS CONTROL 5.3 =>Entry by Component =>JAVA-Components.
    Look for the folder or link "SAP GRC ACCESS CONTROL 5.3 TXT".
    This folder contains the Initial Data files for all the Business Objects Access Control applications. Extract the files for ERM (folder name RE) and import into the ERM application as a Post Installation step.
    Steps to Import the files:
    Go to Configuration =>Initial System Data. Import the files with appropriate option:
    1. RE_init_clean_and_insert_data.xml - "Clean and Insert" option.
    2. RE_init_append_data.xml - "Append" option.
    Do let us update about the status of this issue ?
    Thanks & Regards
    Asheesh

Maybe you are looking for