Question Re: SCP: Cloud Connector and basic RFC destination in Technology Q&A

SCP: Cloud Connector and basic RFC destination

Former Member — Tue, 13 Jun 2017 19:18:41 GMT

Hello Experts,

I am trying set up an RFC destination from SCP but get the error message "Backend is not available in the list of defined system mappings in Cloud connector" when checking for availability of destination connection.

In the cloud connector, I was able to set up RFC without any issues and the result was reachable.

Now in the SCP, when I try to create a new destination with exactly the same RFC details as created in SCC, I get the "Backend is not available in the list of defined system mappings in Cloud connector".

I already referred to the following note:

'2433274: Backend is not available in the list of defined system mappings in cloud connector' and have done exactly as instructed.

What am I doing wrong here?

Best,

Mahadevan

Re: SCP: Cloud Connector and basic RFC destination

luciano_leitedasilva — Mon, 06 Nov 2017 13:30:18 GMT

Hi,

Did you fix this issue? I am facing the same error.

Regards,

Luciano

Re: SCP: Cloud Connector and basic RFC destination

NTeunckens — Mon, 06 Nov 2017 13:51:26 GMT

Please see if the following resources help :

SAP-KBA 2447136 : link
Answer to a Question, indicating the : link

"Apparently the URI of the virtual domain had a underscore in it and that is not permitted or for some reason breaks the validation on checking connection but the system allows you to put it that way and also it shows that the cloud connector is available in the Cloud Platform Cockpit. I've change the virtual URI in the cloud connector for something without "_" or spaces and the connection checking was successfull."

Re: SCP: Cloud Connector and basic RFC destination

former_member415088 — Fri, 27 Jul 2018 09:28:54 GMT

For jco.client.mshost parameter leave only hostname part and delete port number or sapmsXXX part.

This will work then.