"Get destination" does not work in CNV_MBT_TDMS step "Define RFC Dest."

[mario_marschall]

We just installed TDMS and I am trying to set up the RFC destinations between our systems. Since we will be using many different systems and clients and my company is very sensitive about using standard namespaces we want to try to define our own destinations and use them via the "Get destination" function.

So I've built a destination in SM59 (I called it TDMS_EZA371_EZA371 in case this matters) and entered a user with SAP_TDMS_USER role assigned. When I try to use this destination a popup appears saying "Definition of destination MBT_Z_PR498CC_SUB_PCL is not complete. Server name is initial.". What does this mean? The server name in the destination is totally fine and a connection test in SM59 works alright. Is this a bug or am I doing something wrong?

Kind regards

Mario

[Sandeep_Kumar]

When I try to use this destination a popup appears saying "Definition of destination MBT_Z_PR498CC_SUB_PCL is not complete. Server name is initial.". What does this mean? The server name in the destination is totally fine and a connection test in SM59 works alright. Is this a bug or am I doing something wrong?

The technical names for the destinations are created automatically in accordance with the following naming convention:

MBT_<Subproject Name>_<System Role>

In your case you may create sub-projects with the names which you wish to (TDMS_EZA371_EZA371) and then the RFC detiantion name will be MBT_TDMS_EZA371_EZA371_PCL etc..

[mario_marschall]

Sure, this much I get. But according to the Operation Guide it should be possible to not have the system generate destinations and use existing destinations via function "Get destination" instead. That's what I'm trying to accomplish as we are planning to use many different projects at the same time and we don't want to have the system generate new connections for every new task, but re-use existing destinations.

[Sandeep_Kumar]

In this case you can ignore the pop-up message and try to synchronise the RFC destinations, it should work.

[mario_marschall]

That's what I figured. But it does not work, when I close the popup I would expect the name of my custom destination to appear on the Definition-tab instead of the standard name. But in fact nothing changes at all. I just tried to go through all destinations ignoring the popup and hit "apply" afterwards and all that happened was the same popup. Synchronizing is not possible either since the administrative data is not synchronized yet, whatever that means...

[Sandeep_Kumar]

well that seems to be a bug ... you can raise an OSS ticket with SAP and the colleagues should be able to help.