Trouble when adding / modifying authorization objects in a role through ERM

[Former Member]

Hi everyone!!!

We're having some issues when configuring ERM, we followed the Post-Installation guides and we are done with the config part, but when we try to do an example creating a role, we're getting an error message when attempt to add the authorization data.

When we look at the log, we find this message: /VIRSA/GET_ACTGROUP_TIMESTAMP function template not found on RD1

This is the last log...

2010-11-05 17:03:42,515 [SAPEngine_Application_Thread[impl:3]_30] ERROR /VIRSA/GET_ACTGROUP_TIMESTAMP function template not found on RD1

java.lang.Throwable: /VIRSA/GET_ACTGROUP_TIMESTAMP function template not found on RD1

at com.virsa.re.service.sap.dao.SAPRoleTimestampDAO.getRoleChangedDetails(SAPRoleTimestampDAO.java:136)

at com.virsa.re.bo.impl.ConcurrentAccessRoleBO.isRoleChangedInPFCG(ConcurrentAccessRoleBO.java:228)

at com.virsa.re.role.actions.AuthAuthorizationDataAction.pageLoad(AuthAuthorizationDataAction.java:6865)

at com.virsa.re.role.actions.AuthAuthorizationDataAction.execute(AuthAuthorizationDataAction.java:213)

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

Plz help us, we can't find any information about this error.

Regards

Connie

[Former Member · Accepted solution]

HI Conn

You need to patch(SPAM) your basis component in backed i.e RD1 here .It should definalty solve your problem .

I also had same issue in past and same workaround fixed it . Keep us updated about the progress .

Thanks & Regards

Asheesh

[Former Member]

Hi,

I am very interested on the reply giving by Raghu related to "Ensure that the date/time settings are also the same in both the servers.

".

Which servers do you mean? Wich date/time settings? Is this a critical configuration setting that needs to be done?

Many thanks in advance. Kind regards,

Imanol

[Former Member]

Hi Imanol,

Server times are important in GRC. especially firefighter. The server time on GRC on the backend system should be the same, otherwise it is known to cuase problems.

Regards,

Chinmaya

[Former Member]

Hi,

Settings need to be checked-

1. Connectors must be identical for all components for a particular system and test connection should be successful.

2. Unicode should be checked for RAR connector.

3. Patch Level should be same on GRC and Backend and all backend post-installation activites must be completed - (BC set activation, Program etc)

4. RAR Objects Import must be done.

5. ERM Background jobs must be completed before doing Role Creation- Transaction/Object/Field sync, Org Value sync and activity sync.

If above activities are done, no issues should occur in tcode/Object assignment in role.

Regards,

Sabita

[Former Member]

Hi everyone!!!

Thanks for your responses!

Let me tell you all of them were useful, we learned a lot and it was really helpful to double check config just to be sure we didn't miss anything.

Finally the problem was in deed the Patch Level, it wasn't the same on GRC and Backend and now we can see PFCG!!

Thanks again!!

Regards

Connie

[Former Member]

upgrade VIRSANH to latest SP, seems BAPI is missing in Backend system.

regards,

Surpreet

[Former Member]

Hi Connie,

The issue is with the post configuration. Can you check the connection settings again and if you see the unicode option checked, uncheck it.

Also, have you configured the PFCG (used SU25 to fill in the customer tables.) Ensure that the date/time settings are also the same in both the servers.

This should resolve the issue.

Hope this helps!!

Regards,

Raghu

[Former Member]

Is RD1 the backend ABAP system here?

Thanks,

Chinmaya

[Former Member]

Hi Chinmaya!

Yes it is, Development enviroment.

We have SAP ECC 6.0 and GRC AC 5.3

Thnks!

Connie

[Former Member]

In that case you need to make sure VIRSANH in the backend and in JAVA need to be at the same support pack level. Also you said you are using ECC. So in that case I believe SAP_HR must be one of the installed components. So have you installed VIRSAHR as well?

Regards,

Chinmaya