ABAP Code Remediation vs. ABAP Modernization

As SAP users modernize their businesses by migrating to the latest and greatest from SAP, namely S/4HANA , the topic of “ABAP code remediation” usually comes to the forefront. There’s no doubt you need to migrate your mission-critical custom applications to your new environment but is remediating your ABAP customizations to make it work exactly the same way in S/4HANA as it did in SAP ECC, is really the best way to use your effort, time, resources and money in a S/4HANA migration?  Dig a little deeper to learn what ABAP code remediation is and the alternatives you have.

Get a clear visibility to your ABAP custom code - download free dashboard


What is ABAP Code Remediation in SAP? 

Technically, ABAP code remediation means simply making an application that was functional on your old system work on your new one. Input and outputs are the same, and users see no difference in what the application does and how it supports their workflows. 

To remediate your apps, your development team will look at ABAP code running on your legacy ERP (SAP ECC) system and change the table statements to make it work in SAP S/4HANA or other environments. While ABAP code remediation may meet your immediate needs by giving your team continued access to the custom apps they need, remediation doesn’t improve the business, it is wasteful while just maintaining the status quo. Developers have to spend time and resources to remediate, but when they’re all done and successful, the business users get exactly the same experience as before.  

ABAP code remediation is like moving to a new home with all your existing appliances and furniture from your old home. However, if the moving cost, time, and effort are more than the actual cost of new appliances and furniture, would you still move everything? Most likely you’d move some selective things that are dear to you but definitely not move everything if you can buy new things for less cost, time, and money. Isn’t it better to move what is absolutely critical and that cannot be replaced but buy new modern appliances and furniture for less cost? 

Similarly, ABAP modernization allows you to take what’s necessary to your new SAP environment, and leave behind what doesn’t make sense from a labor and cost perspective.

SAP custom code impact | Pillir

 

Alternatives to ABAP Code Remediation

It’s important to recognize that ABAP code remediation isn’t your only option for migrating custom apps to a new SAP environment. Given the state of current technologies and recent advances, you have other alternatives to ABAP remediation, namely ABAP or legacy app modernization or simply application modernization.

Application modernization, as defined by Gartner can constitute one or more of the following changesABAP Code Remediation Vs. ABAP Modernization

  • Rehost: Moving an application from an on-premises, monolithic application into a cloud-native application hosted in the cloud. There is a common misconception in the SAP community that an ABAP customization has to stay and reside within the SAP system to perform adequately. However, depending on the ABAP customization like an ABAP report or a Z-Tcode, it can be split from your SAP core and hosted outside SAP ERP with absolutely no degradation in performance or flexibility. SAP calls it the side-by-side extension
  • Rebuild: Sometimes an ABAP customization may be very old but still very useful from a business functionality perspective. An S/4HANA migration may be the perfect opportunity to rebuild that customization to meet the new business requirements and needs. Most SAP customers might think rebuilding the ABAP logic may be as big of an effort as it was done earlier in ABAP. However, the advent of low-code/no-code tools has made rebuilding the apps a breeze. It not only addresses the new enhancements the business community may be asking for but also lowers the maintenance effort of keeping the old ABAP code
  • Refactor: In quite a few business use-cases, your stakeholders would prefer to run the custom program on a mobile phone, tablet, or in remote locations on a rugged device. Refactoring an ABAP customization to run better in a modern device during an upgrade might be the perfect opportunity the satisfy that business requirement the stakeholder has been asking for a while. 
  • Reimagine: Given the pandemic conditions around us, quite a few businesses are rethinking and reimagining the business process from the core. This is to meet the changing business requirements with changing business models. Reimagining your applications during a S/4HANA upgrade is the perfect time to put this in action. 
  • Replatform: This typically is a lift-n-shift strategy wherein the original application logic is maintained as it is but the platform is changed into a more modern platform. One could argue that remediation falls into this bucket which is true but you are still keeping it in ABAP within ERP, which retains the technical debt. Instead, you could re-platform and move it to the cloud, keeping the same functionality but eliminating the technical debt from ERP.

Get a clear visibility to your ABAP custom code - download free dashboard

The approaches to Application modernization can differ from use-case to use-case depending on its purpose. cost, value, effort, and risk. Sometimes it could be a combination of all of the above 5 R’s or maybe one of the R. In either case, each use-case merits its own approach to modernization.

However, irrespective of the modernization path, you have more options than a simple ABAP remediation during a S/4HANA migration. It does have to be the same inputs and outputs of the program but instead, you can truly modernize it that adds value to the business. 

The advent of low-code / no-code tools along with program conversion tools such as ABAP conversion tool and low-code platform from Pillir, lets you modernize your ABAP customization faster than you can think of and simpler than you can imagine at a cost much lower than your expectations.


Clean, Operationally Beneficial Custom Code, Now and Later 

Choosing the route of modernization via an SAP RAD platform rather than ABAP code remediation will provide your organization with benefits even after you complete your cloud transition. Ensuring applications are up to date is an ongoing process. You can compare it to keeping your garage clean and in order or working out and eating right to stay physically fit. Keeping apps optimized and code clean is not a one-and-done event; it’s continuous. Pillir’s RAD platform for SAP lets you make necessary updates to your apps quickly and easily, whenever you need to.

Planning your move to a new IT environment takes extensive planning – and some creativity – to ensure your team has the tools and functionality they need to operate efficiently. Part of that planning must be how you will address custom code, get the most ROI from modernizing it, and putting processes in place that will continue to help you control technical debt and address changes with agility. 

Final thoughts on ABAP Code Remediation

Pillir equips you to meet the challenges that SAP users face with ABAP code remediation. Contact us to learn how to modernize – and enhance – code as you transition to a new IT environment. 

Start innovating your business

Vaidya Aiyer

Vaidya Aiyer

Vaidya Aiyer is a leader, innovator, entrepreneur, and technology geek. He has the reputation a major leader and innovator in the low-code space, specifically regarding ERP modernization. His 25 years of ERP/SAP experience has propelled his company’s vision of accelerating modernization and digital transformation. Vaidya has also held executive positions at Lenovo, SEAL Innotech (enterprise mobility and Google Apps solutions), and Medtonic (lean manufacturing solutions). Pillir provides an innovative,ERP-focused, low-code/no-code, cloud-native platform called EdgeReady Cloud.