cancel
Showing results for 
Search instead for 
Did you mean: 

SUP 2.2.2 -> Error=com.sybase.dataservices.OHException -You are not allowed to execute the RFC function ********************

Former Member
0 Kudos

Hello all,

I am facing one issue where authorization error is coming up only for one RFC in SUP. One of the RFC's with scheduling cache policy is unable to fetch the entries from R/3 system and throwing a below authorization error in SCC Logs.

"Error=com.sybase.dataservices.OHException was thrown by transaction com.sybase.djc.transaction.TransactionContext.*AnonymousTransaction*\ncom.sybase.dataservices.OHException: You are not allowed to execute the RFC function -"****RFC***************"


Please share your thoughts on this issue. What could be the reason of this authorization error specifically for one RFC's in SUP and other RFC's  are working perfectly. Test connection is successful as well in SUP Connection.

Thanks.

Best,

Prateek

Accepted Solutions (0)

Answers (1)

Answers (1)

Jitendra_Kansal
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Prateek,

Just want to confirm, are you able to preview MBO (in SUP mobile workspace) that has been created for the same RFC/BAPI  for which you are facing above issue?


Make sure you verify it with same backend user.

Also, can you also verify whether any new row gets created in the mbo table (for same bapi) in sup cache database?

Regards,

JK

PS: I am not an ABAPer. Seems some issue at BAPI level. You may check with your backend team.

CC: