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: 

RISK TERMINATOR error screen (GRC SP13)

Former Member
0 Kudos

Hi all,

I have RT configured and working since a month and everything was ok until last week, i mean, RT has been working fine (i had it configured only for PFCG) but now, when i create or modify a rol, RT lauchs the SoD check program and a few seconds later a new screen in R/3 apears with the following message "Risk Analysis failed2" with a button which says "continue". When i press that button i return to PFCG and i can continue with role creation but without know if that rol has sod conflicts or not.

i have some additional testing: I test with SU01 (activating in Risk terminator configuration transaction the option "SU01 Role Assignment Plug-In(YES)") and with SU01 transaction RT works fine !!!!!

I mean, with PFCG the R/3 shows me that message but with SU01 RT works perfect!!! Could any help me on that issue??

Thanks a lot

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi Chinmaya,

According to the note, this problem is only if the connector is Adaptative RFC but we have SAP JCO connector.

Anyway i restarted SLD but i keep getting the error

4 REPLIES 4

Former Member
0 Kudos

HI Ricardo,

Is the SLD working? Please take a look at note 1504679.

Thanks,

Chinmaya

Former Member
0 Kudos

Hi Chinmaya,

According to the note, this problem is only if the connector is Adaptative RFC but we have SAP JCO connector.

Anyway i restarted SLD but i keep getting the error

0 Kudos

Hi Ricardo,

What patch level are you on... There seem to be some probelms with the RAR web service which are fixed in SP13 PAtch 1 as per note 1168120. Also the note 1529096 may be relevant. I wish there was more info in this note.

Thanks!

Chinmaya

Former Member
0 Kudos

Thanks a lot!!!

The Technical team restarted GRC instance, application server,... and now it seems to be ok again. Apparently some element of the network was suspended last week and some service was inconsistent.

Thanks again!