SAP BUILD Destination

[anilkumar_raina]

In order to consume data from s/4 hana backend we have to create Destination per backend API as each destination needs URL for service document for odata in backend sap system. Downside of this approach is we will end up creating tons of destinations to access data which does not look right approach at all.

Is there workaround to define one generic destination to access all odata services created in backed sap system (s/4 hana).

[Dan_Wroblewski]

You can see here in the documentation how to set up destination for a catalog so it will expose all services you have permission to. I am told it is straight forward for on-premise but I have not been able to get it to work yet for S/4HANA Cloud.

https://help.sap.com/docs/build-apps/service-guide/sap-systems?locale=en-US

[gregorw]

I agree with Anil, one destination per service does really mess up things.

From the provided documentation it's not getting clear to me what needs to be configured.

I know about the OData V2 Service Catalog that is available in the path:

/sap/opu/odata/IWFND/CATALOGSERVICE;v=2/ServiceCollection

you can test an example at:

https://sapes5.sapdevcenter.com/sap/opu/odata/IWFND/CATALOGSERVICE;v=2/ServiceCollection

maybe the documentation can be improved to show that for an S/4HANA On Premise. Also OData V4 should be covered. The Endpoint there is documented at Service Catalog

[Jagadeesh21]

Can't we use RFC destination, instead of Odata ??