Symptom
Connecting to a ODATA url in the on-premise system like http://<Hostname>:<Port>/sap/opu/odata/IWBEP/RMTSAMPLEFLIGHT_2/?sap-client=<cient_number> gives error Cause: Invalid odata connection! Getting odata metadata failed because of <HTTP/1.1 200 OK> Get $metadata response:<metadata.xml>Excpetion: Tag with name 'Edmx' was not found.
Environment
SAP Datasphere
Cause
Currently SAP Datasphere supports only ODATA url without the client information.
Resolution
Make the client in the on-premise system as a default client and make sure that ODATA url is published in the default client of the on-premise system.
See Also
- 3192250 - Generic Odata connection couldn’t be established
- How to set up a Generic OData connection in SAP Datasphere
Keywords
ODATA, Datasphere, on-premise, S/4 HANA, Generic ODATA connection, client,Excpetion: Tag with name 'Edmx' was not found , KBA , DS-BB-ODATA , To address issues related to Odata consumption API , Problem