Hi @CheriyanSam,
If my memory doesn't betray me, the service "OData Provisioning" was only available on Neo - which is being discontinued. And it was targeting customers that didn't have a SAP Gateway (FES) system running on-prem.
If you are moving to the cloud, it is most likely that you are going for an S/4HANA Private edition. In that case, the private edition already comes with the means for you to publish OData services without the need of a SAP Gateway system. It all runs on the same box.
However, to comply with the ABAP Cloud guidelines (https://community.sap.com/t5/enterprise-resource-planning-blogs-by-sap/abap-cloud/ba-p/13557273) you will have to rely on published APIs and CDS Views in order to "keep the core clean".
This means that you will have two options:
1) Keep the developed OData services the way they are during the migration - and later you will have to figure out how to move them to the new ABAP Cloud guidelines.
2) User ABAP Cloud guidelines to "repurpose" the OData services by adhering to the published APIs and exposed CDS Views. If non are available, use BTP to develop your OData service by consuming other standard APIs in your S/4HANA system. Adopt new ways of thinking about how you do your data integration with other systems, like using the Event-Driven Architecture - which allows you to capture ERP's events and send them to a queue for later processing in BTP.
You can easily develop new OData services on BTP using CAP (Cloud Application Programming Model). This will allow you to leverage Java and NodeJS knowledge together with CDS syntax to easily define services based on local data (cloud database) or using Cloud SDK. This SDK allows you to easily consume any S/4HANA published API and it is fully integrated with BTP features like destinations.
Hope this helps.
Ivan
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.