cancel
Showing results for 
Search instead for 
Did you mean: 

Can't read the metadata from S/4HANA Onprem system from Integration Suite

sbandara
Discoverer
0 Kudos

Hi All,

I am trying to build an OData API to expose OData service API_SALES_ORDER_SRV on S/4 HANA Onprem system.

My cloud connector has been configured as 

saps4dev400.<host>.local:sapmsDEV

I am trying to configure the OData channel to read the data from S4 Onprem system. In Processing tab, I am trying to configure the resource path using "Remote" as the connection source. My data looks like this.

1. Connection source = Remote

2. Address = http://sapeccdev.<host>.local:443//sap/opu/odata/sap/API_SALES_ORDER_SRV/$metadata 

3. Proxy Type = On Premise

4. Location = Blank

5. Authentication = Basic

Credential name = 'ABC' (I have created a security material to store user id and password.) I ma getting an error "Failed to connect to system"

sbandara_0-1711412840495.png

It would be great if someone could help me.

Kind Regards

Shantha

 

 

 

 

 

Ryan-Crosby
Active Contributor
0 Kudos
The data in the location field needs to match the location information stored in the cloud connector. I don't recall the exact view or field label, but it must be an exact match.

Accepted Solutions (1)

Accepted Solutions (1)

amontella96
Active Contributor
0 Kudos

hi @sbandara 

 i have checked a cloud integration to see where is this processing tab and I didnt find it so here me out:

- judging by your info ,  Address looks wrong because you use http against 443 AND there is a // instead of / in the middle

- if above doesnt fix your issue , can you paste a screenshot of this processing tab ?

When you configured your CC , did you declare correctly the resource of the mapping in "cloud to on-premise"  AND is virtual host reachable?

let me know and ill try to help you out, cheers!A

sbandara
Discoverer

Thanks for the response. The main issue was with the cloud connector configuration. I did not have access to look at the detailed config. Someone else fixed the issue. It is working now.  Yes "//" was a problem too. Thanks for the pointing out that.

Answers (0)