can the OData Interfaces be seen as alternative of RFC? Because it seems OData is only an interface for browser-based apps like UI5, but it cannot be used for API endpoints.
According to following reference, OData is not really REST-full since its not stateless due to the usage of cookies. Also the X-CSRF-Token is actually only designed for browser:
How do you see SAP's OData? Is there maybe differences between RAP-OData and the ODatas you create via Tx SEGW? Background is, I hear concerns in my company regarding security standards and that such interfaces actually cannot be used as API endpoints.
SAP offers APIs that are specifically built for application-to-application communication, see https://api.sap.com/alltypes.
The majority of these APIs are OData APIs, and for S/4HANA they can be seen as successors of RFCs and BAPIs for synchronous A2A communication.
Building your own web APIs with RAP offers many out-of-the-box benefits that you don't get when directly using the underlying SICF, especially for following security standards.
You can implement directly a web service and register it at SICF. Why using Odata? Makes things complicated and slow. The only reason for all that overhead (gateway...) is generating consulting demand.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.