Hi,
I'm struggling to call SOAP service in the on-premise system using Service Consumption Model and Communication Arrangement.
I generated SCM for SOAP service SalesOrderERPByIDQueryResponse_In_V3.

Created outbound service

Created communication scenario:

Path prefix is maintained on both service and scenario.
Created Communication system based on Cloud destination and Communication arrangement:

Path is also there.
I'm calling the service via generated proxy:
destination = cl_soap_destination_provider=>create_by_comm_arrangement(
comm_scenario = 'ZCOM_SO'
service_id = 'ZSO_SPRX' ).
DATA(proxy_so) = NEW zco_sales_order_erpby_idquery( destination = destination ).
DATA(request_so) = VALUE zsales_order_erpby_idquery_syn( ).
proxy_so->sales_order_erpby_idquery_resp(
EXPORTING
input = request_so
IMPORTING
output = DATA(response_so) ).<br>
The result is HTTP 404. I checked the logs on cloud connector and it looks like it's calling the root server url.
Path prefix is ignored and not included in the request.
I tried different URL settings in the Destination URL in BTP cockpit and here are the findings:
1) http://server:44301/
Comm. arrangement saved without error but proxy calls root url
2) http://server:44301
Cannot save arrangement - error HTTP: No access URL specified for binding Binding

3) http://server:44301/sap/bc/srt/scs/sap/ecc_salesordererpidqr3
Proxy works fine but it means I have to maintain one destination for each web service which is an overkill.
Thomas Wiegand I saw you answer under https://answers.sap.com/questions/13614657/add-in-path-prefix-on-soap-url.html but it doesn't seem to work purely based on Comm. arrangement path unless it's maintained in the destination also.