RFC Error for TMSADM After Executing RSRFCCHK

Question

Hi,
I'm using ECC6 and running RSRFCCHK to check our RFC destinations. Everything is working fine except that I'm getting an RFC no authority error for function group SYST for TMSADM. I've reset the buffer by using RSET and even executed report RSUSR405 but the error still occurs on both times. I did try giving it access to function group SYST and it work perfectly. However, I don't know why it's causing the error in the first place and this is what I would like to figure out first. I'm hesitant to give it the access without knowing the reason why.
Has anyone encountered this error before? Can anyone help on how to solve this problem?
Thanks,
JB
Edited by: JB Ramos on May 6, 2009 7:12 AM

Answer 1

It is not necessarily an error for an RFC call to fail... To ensure that the TMSADM has the correct authority you should not need to reset the buffers. Logon to client 000 of your transport domain controller (should ideally be production...) and reset the user TMSADM in transaction STMS via the "Extras" menu. That should be sufficient.
RSRFCCHK is using a function module from the group SYST to obtain information about the connections. But those connections do not have to include FM's from SYST to perform that which they are designed to do and if I remember correctly then for the TMSADM it does not.
Specifically in this case, the TMSADM user performs some logistical tasks in the STMS but requests of the human person operating the STMS that they should logon themselves when performing tasks which are considered "critical" - or at least sufficiently critical that the TMSADM should not be able to complete it on it's own. An example would be to Import a transport request.
As the TMSADM is not sufficiently authorized to perform these functions, the system calls for the dialog user to "remote login" to the system when the TMS attempts to do the task. This is a function module in SYST called something like RFC_REMOTE_LOGIN or similar.
Cheers,
Julius