on 2017 Jun 13 8:18 PM
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
Request clarification before answering.
Please see if the following resources help :
"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."
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For jco.client.mshost parameter leave only hostname part and delete port number or sapmsXXX part.
This will work then.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
31 | |
15 | |
10 | |
8 | |
7 | |
6 | |
6 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.