Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

SAP Adapter has a problem, SOD violations will not be checked

Former Member
0 Kudos

Hi,

In our ides server whenever i click save button in su01 i get the following error ,

"SAP Adapter has a problem, SOD violations will not be checked !

Please check with your system Administrator

Technical Info:

Error when opening an RFC connection "

we didn't have this problem before . can anybody help me to resolve the issue

Also I am getting this error only if I click save in su01. in other t code. I don't get this error

Thanks in Advance

Edited by: gajula jhansi on Apr 11, 2011 11:28 AM

3 REPLIES 3

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

It means you are using Risk Terminator to check SoD violations while changing/creating user from Su01. Check whether SAP Adapter is running in GRC or not. If it is running then check in SM59 whether RFC created for Risk Terminator is working or not.

Thanks

Sunny

0 Kudos

Hi

we are getting Error when opening an RFC connection after change the role . please let me know how to verify Risk terminator is enabled in Su59 Screen.

Former Member
0 Kudos

You need to restart your sap adapter in GRC front end from configurations tab-->Sap adapter >choose the one for your back end system> if it's grayed out or even green still, click on it and let it restart and turn green again.

Then you go back to your backend ECC system and in SM59 , choose the RFC connection for the Risk Terminator (the one you have saved in the Risk Terminator transaction /VIRSA/ZRTCNFG in backend system).. and test the connection. It should pass the connection test if your adapter is working and set up correctly. Then when you do save in SU01 or make changes in PFCG and have Risk Terminator activated for the backend system, it will check the SOD violations against those transactions from RAR front end.

If you don't want Risk Terminator to check for SOD violations in front end RAR, then you need to set your settings to 'NO' for all in the Risk Terminator transaction. You can get all this info in the GRC config guide for RAR and SPM area.

Regards,

Alley