cancel
Showing results for 
Search instead for 
Did you mean: 

ERM 5.3 SP10 - Unable to generate roles

Former Member
0 Kudos

Hi All,

We have a brand new GRC ERM instance with SP10. We've been able to import a role, go through WF but are not able to generate the role on the backend.

The connector is setup, the user has more than enough access but the role does not seem to be getting pushed to the backend... The message is "Failure : null"

Any ideas? Any help is much appreciated.

The ERROR log is as follows:

2010-01-12 12:49:49,292 [SAPEngine_Application_Thread[impl:3]_6] ERROR java.lang.NullPointerException

java.lang.Throwable: java.lang.NullPointerException

at com.virsa.re.bo.AuthDataHelper.getConsolidatedFieldList(AuthDataHelper.java:1015)

at com.virsa.re.bo.impl.AuthorizationDataBO.getRefinedFieldValList(AuthorizationDataBO.java:1047)

at com.virsa.re.bo.impl.AuthorizationDataBO.getRoleAuthData(AuthorizationDataBO.java:1000)

at com.virsa.re.bo.impl.AuthorizationDataBO.getAuthData(AuthorizationDataBO.java:899)

at com.virsa.re.service.sap.dao.GenerateRoleDAO.generateRoleWithoutChild(GenerateRoleDAO.java:210)

at com.virsa.re.bo.impl.GenerateRoleBO.generateRoleOnConnector(GenerateRoleBO.java:172)

at com.virsa.re.role.actions.GenerateRoleMultipleSystemsAction.generateOtherRole(GenerateRoleMultipleSystemsAction.java:442)

at com.virsa.re.role.actions.GenerateRoleMultipleSystemsAction.generateRolesAfterRiskSuccess(GenerateRoleMultipleSystemsAction.java:372)

at com.virsa.re.role.actions.GenerateRoleMultipleSystemsAction.execute(GenerateRoleMultipleSystemsAction.java:95)

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(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)

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi All, I eventually was able to connect and generate the role by deleting it in ERM, re-importing from the R/3 backend, starting a new workflow and then generating it.

Not sure why, but at least it works now...

Former Member
0 Kudos

Hello Dylan,

One of the reasons for this to happen is if you have mentioned in your ERM Configuration -"Allow Role Generation with violation as - NO ", and the role you are trying to Generate are having violations.

Regards,

Hersh.

http://www.linkedin.com/in/hersh13