The OData or EDMX specification file was not found at the destination

[Kiranmayeesv]

Hi,

I'm trying to consume odata from BTP build process automation. I have created the destination using the odata url I've created in sap s4 on premise system and the connection is successful.
When I'm trying to create action using odata destinations in build, I'm getting the error 
"The OData or EDMX specification file was not found at the destination"

Can anyone please help me with understanding why I'm getting this and also if there are any other solutions to consume odata in BTP build process automation, let me know.

Regards,
Kiranmayee S V

[JACoetzee]

Hi Kiranmayee,

Have you resolved this issue? I have the same issue at the moment.

Thanks,
Jhani

[Kiranmayeesv]

Hi Jhani,
I haven't found the solution yet, If you've got it could you please help me out?

Thanks,
Kiranmayee

[JACoetzee]

Hi Kiranmayee, 

I played around with the Destinations, not really sure what made it work in the end, but attached is the destination setup I have at the moment. 

Hope this helps...
Jhani

[Yves123]

Even with the above additional properties i'm facing this issue. Is there another solution?

[SANJEEVE]

Here are a few steps to troubleshoot and resolve this issue:  Check the Metadata URL: Ensure that the metadata URL is correctly configured in your destination settings The URL should end with /$metadata  Authorization: Verify that the user credentials used in the destination have the necessary permissions to access the OData service and its metadata  Metadata Format: Ensure that the metadata is in the correct format (EDMX/XML) SAP Build Process Automation expects the metadata in a specific format, and any deviation can cause this error  Network Connectivity: Make sure there are no network issues or firewall restrictions preventing access to the metadata URL  Destination Configuration: Double-check the destination configuration in the SAP BTP cockpit Ensure all required properties are correctly set, such as sapapplicationdevelopmentactionsenabled and sapprocessautomationenabled If these steps do not resolve the issue, you can consider alternative solutions to consume OData in SAP Build Process Automation:  Using SAP BTP ABAP Environment: Create a custom entity and call backend RFC function modules or API classes from SAP S/4HANA Then, create a service binding and use the metadata URL to create actions in SAP Build  Using OpenAPI: Convert the OData metadata to OpenAPI format using tools like OData-to-OpenAPI and then use the OpenAPI specification in SAP Build  Using Cloud Application Programming (CAP) Model: Expose the OData service via CAP and consume it in SAP Build Process Automation