Skip to Content
Technical Articles
Author's profile photo PARTHA GOSWAMI

Mapping ABAPer (WRICEF) into SAP BTP (Business Technology Platform)

Now-a-days.. when many customers wants to go for SAP BTP (Business Technology Platform), mainly to Keep-the-Core-Clean, many ABAPers are struggling to understand the mapping of the regular object developments which used to be done in onPrem ABAP environment.

So, in this short blog, let’s discuss how the ABAPers can map themselves into SAP BTP world.

And as an ABAPer we used to deal with W R I C E F object developments, let’s map in BTP with the same terminologies, which would help to understand the developments in BTP easily.

In the sequence..

πŸ“Œ1. Workflow πŸ–‡

You might be using SWDD SWO1, SWUS or SBWP to build, test and manage your business workflows in OnPrem ECC or S/4 HANA.

In BTP, it’s Cloud Workflow with Business rules, you can have advanced level process visibility on top of that.
You can use workflow inbox application services for all workflow administrations at Central place.

 

πŸ“Œ2. Report 🧾

You are very much familiar with SE38, SE80, SE37, SE10 to write code, test and deploy for customer specific report and applications.

In BTP, you will be connecting to OnPrem ECC or S4 system using API or SDI.

Then Build business logics with CDS based data models and CAPM NodeJS services.

Then use, UI5 for analytical or list report.

Or even you can go for SAC.. for advanced level reporting and dashboards on top of those data models.

 

πŸ“Œ3. Interfaces πŸ”—

Which generally known for IDoc, Proxy, SOAP, RFC kind of developments in OnPrem ECC or S/4 HANA.

In BTP, we have various options…
And API business hub almost includes everything,..
OData, Rest API, SOAP all..

You can directly consume those from your CAPM NodeJS applications.

Or if you want low-code based process integration, use CPI, where you will be having options for lots of standard adapters.

Even you can use SDI for efficient data integration.

Or use event mesh for real-time integrations.

 

πŸ“Œ4. Conversions 🎭

When we have new SAP system, we generally load the data first, we use LSMW, BDC, AL11 file upload kind of solutions.

For standard data load, the process will be same.
At the same time, in BTP, when you build side-by-side Extensions you will need the data in HANA cloud, there you can go for SDI.

 

πŸ“Œ5. Enhancements πŸ’¨

You must have used User Exit, Customer Exit, BAdi to fulfill your customers, custom business requirements.

Of course, we will not have the same options for BTP, because here our main goal is to keep the core system clean.

So, we will do the side-by-side Extensions, mainly using CAP, RAP, HANA cloud, API, SDI and so on.

 

πŸ“Œ6. Forms πŸ“°

In BTP, it’s Adobe form service, almost the same.
You can generate print and interactive forms using Adobe document services (ADS).
You can call this service from your application using REST APIs to render the documents and you can manage the form-template in template store.

 

These are the generic adoption types from regular SAP development perspectives.

But when you will come into BTP world, endless possibilities will be open for you, for your organization’s digital transformation.

And… If you want me to post more contents like this, pls like and share it !

And if you have any questions or suggestions, put it in comments section.

Thank you… Bye…!

Assigned Tags

      7 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Pankaj Yadav
      Pankaj Yadav

      Hey PARTHA GOSWAMI ..
      Nicely explained.. in few words..

      Author's profile photo Satyajit Narkhede
      Satyajit Narkhede

      Nice information PARTHA GOSWAMI

      Author's profile photo Prasenjit Bist
      Prasenjit Bist

      I did not get the point what is there to be confused and what is the need to map. Even if one wants to to kill some free time the traditional reports are now lists, the enhancements one does are either in-app or the side by side , workflows in traditional sense areΒ  going to become flexible ones. The interfaces are quite different from traditional ABAP. I would rather advise over come the WRICEF mentality and embrace the new way and new lingo because mapping them does not makes any sense IMHO.

      Author's profile photo Sergio Ferrari
      Sergio Ferrari

      Hi PARTHA GOSWAMI , thanks so much for your post.

      You inspired me and I shared my point of view and the results of my analysis to the SAP ACTIVATE in the blog Is the WRICEF term still appropriate in the days of SAP RISE? that you may want to comment with your suggestions and integrations.

      You rock!

      #no-wricef

      Author's profile photo Julian Charles
      Julian Charles

      Hi PARTHA GOSWAMI it is Very clean and detail explanation Thank you so much for the post.

      Author's profile photo jeelani kattubadi
      jeelani kattubadi

      Hi PARTHA GOSWAMI, Nicely explained. Thank you Β for the post

      Author's profile photo Jelena Perfiljeva
      Jelena Perfiljeva

      Not to be negative or anything but I kind of agree with Prasenjit Bist here. This "mapping" really makes little sense and I'd argue is not accurate (like "mapping" apples to oranges) and, well, simply pointless.

      If someone is trying to, say, make a jump from classic ABAP to "the Cloud", then they should be thinking about new programming models. Not "what is the Cloud equivalent of ABAP report". Sorry, it's just not the right mindset IMHO.

      And, more importantly, SAP BTP (and other technology out there) has so much more to offer that did not even exist in SAP before. That's kind of a big part.