SAP Solution Manager 7.2 SP 18+19: Destination does not exist or does not work

Issue

You recently upgraded to SAP Solution Manager 7.2 SP 18 or 19. Now you are facing the issue, that you are not able to control transport requests anymore using the Cross Connector app. You are receiving an error message telling you, that a TMS destination does not exist or does not work.

Root cause

This issue is caused by a Bug in SAP standard. The BADI cts_badi_foreign_system is now having two active implementations (one for LMDB integration and one for ATC integration) which are conflicting with eachother.

Solution

As solution, you have to implement or update SAP note 3247142 as mentioned in SAP note 3487953. This SAP note will deactivate the ATC BADI implementation on SAP Netweaver 7.40 systems.

Alternatively or in parallel you have to implement or update SAP note 2649366. This SAP note will correct the behaviour of the SAP Solution Manager BADI implementation now respecting other BADI implementations.

It is sufficient to implement one of these two SAP notes. However we recommend to implement both.

Cross Reference

Maybe you did an upgrade to SAP Solution Manager 7.2 SP 18 or 19 long time ago, but you are facing the issue from now. This could be the case if you are evaluating CC5 in your SAP Solution Manager with demo clients of your SAP Solution Manager and if you performed an upgrade to the newest version of our app recently. In the past destination NONE was partially used for transport management activities in other clients of the controlling SAP Solution Manager system. With the newest version we are alway using the right TMW RFC destinations even for clients of the SAP Solution manager system itself.

Maybe you were not performing an upgrade to SAP Solution Manager SP 18 or 19, but you are as well facing this issue. This could be the cause if you updated some SAP notes (maybe central note of SAP Solution Manager or ChaRM) and you herewith downported the bug.

In all cases mentioned above, please implement SAP note 3247142 & 2649366 as mentioned in SAP note 3487953 to solve this issue.