Redefine External OData Service with OData V4

[francesco_alborghetti]

Using SAP_GWFND 7.51, is it possible to redefine an OData Service in a way that it can consume an external OData service that supports only V4 OData version?

I am following the user guide for OData Services Consumption and Integration (https://help.sap.com/viewer/68bf513362174d54b58cddec28794093/7.5.10/en-US/ae7822518bc72214e10000000a44176d.html), but it does not work.

If this is not supported yet, does anybody knows if this is in the roadmap for ABAP Gateway?

Thanks

[Andre_Fischer · Accepted solution]

Hi Francesco,

no this is not possible.

It is also not planned to have the redefinition feature for OData V4.

It is rather planned to offer with the new upcoming Restful ABAP programming model that entities can be modeled via CDS but implemented using ABAP.

See also the session S4H140 at SAP TechEd

https://www.sap.com/documents/2017/12/b01b06f5-e37c-0010-82c7-eda71af511fa.html

https://www.youtube.com/watch?v=hPfgxxsCghY

(the last slides of the presentation)

Regards,

Andre

[francesco_alborghetti · Accepted solution]

Thanks a lot Andre!

I was thinking to propose to my customer a reverse proxy based architecture (with SAP Web Dispatcher), do you think it can support this use case (the final architecture will be SAPUI5 deployed on ABAP Gateway, OData V4 from external service and user that connect via Web Dispatcher)?

Francesco

[Andre_Fischer · Accepted solution]

Yes, this is definitively the better approach.

Using SAP Gateway only as an Odata proxy doesn't make much sense.

Using a web dispatcher in between is the recommend way also for SAP Fiori scenarios with Hana xsa & sap gateway.

BR

Andre

[Andre_Fischer · Accepted solution]

And maybe cors is a solution?

https://help.sap.com/viewer/1ca554ffe75a4d44a7bb882b5454236f/1709.000/en-US/149f40fa2c9b40599b2a61ee...