Remote comparision of object - Dump RFC_NO_AUTHORITY for user TMSADM in remote system

[DanielB]

Hello,

if we try to do a remote comparision in version management of a object (i.e. a program), we get an error "no RFC authorization for function module RPY_PROGRAM_READ" in the source system and two dumps "RFC_NO_AUTHORITY" in the remote system (one time for function group "SEUEXIST" and one time for function group "SIFP").
As in SAP help described (Authorizations in Version Management) the user TMSADM has profile S_A.TMSADM in client 000, but included authorization "S_TMSADM_SHO" seems to be not enough.

Does the user TMSADM needs an additional S_RFC authorization for one of the function groups, cause I can't find a corresponding note? Can someone confirm this?

Thanks
Daniel

[Sandra_Rossi]

Why do you use the TMS remote destination? For instance choose another destination based on the source user which is trusted in the remote system, where you have all adequate authorizations. Ask your admin to do that.

[DanielB]

We like to keep it as simple as possible and to avoid additional support. If the user chooses remote comparision in the version management of an object and then click "fetch remote versions" two fields are shown:
- "Target system" (radio button "Target System Selection")
- "RFC Destination" (radio button "RFC Destination Selection")

In the first field user has to just type in the well known <SID> (current five values in F4 help). In the second field he has to choose the correct RFC destination, which is normally not well known (current over 20 values in the F4 help). So we want to use the 1st option with <SID>, but we get the error and the dumps.

[raymond_giuseppi]

Read first 3004154 - TMSADM Authorizations or CTS User Administration and Authentication, look for 'you should setup a trusted connection between the two systems and not add authorizations to TMSADM'

[jmodaal]

Hello,

the user TMSADM is typically used in the (generated) RFC connections for the TMS. It sound that you used these RFC connections for another purpose. Therefore, I would not expect to find an SAP note pointing to a missing authorization for TMSADM in your concrete use case. However, if you are going to continue using these RFC connections for other purposes you can have some trust in the shortdumps, and of course it could be solved by adding S_RFC with the given function groups. But I would recommend to use the generated RFC connections with user TMSADM for the TMS only and use other (new) RFC connections and other (new) users for other purposes.

Kind regards

Jan