Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
EmersonATosin
Explorer
3,185

Introduction

Hello, SAP Community!

In this blog post, I’ll share my perspective on the future of current ABAP Developers. We'll discuss emerging trends, new technologies, and even some established ones that aren't getting the attention they deserve. I'll also touch on outdated paradigms, evolving approaches, and the new profile of the so-called “SAP Developer,” as we often find ourselves working beyond ABAP.

To organize this, I'll use the MoSCoW prioritization technique, widely used in project management. This method categorizes priorities as Must Have, Should Have, Could Have, and Won’t Have.

Main Part

1. ABAP 7.5+ (Should Have)

As surprising as it may seem, ABAP 7.5+ is still underused or partially utilized in 2024. While listing all its benefits would make this blog too lengthy, I’d like to highlight two key advantages:

  • More readable code.
  • Compatibility with modern extensions and technologies (e.g., EML).

Migrating isn’t easy, but it can be done gradually. For those looking for guidance, I recommend Smart Logic Academy’s content: Smart Logic Blog.

2. ABAP OO (Should Have)

Object-Oriented ABAP is far from new, yet it’s still not a widely adopted paradigm. The time to embrace it is now! SAP’s new products—and especially the S/4HANA Public Cloud Edition—often require or encourage the use of classes and methods. This is even more critical in BTP ABAP Environment, where procedural coding isn’t an option.

Remember: simply replacing FORM/PERFORM with classes/methods isn’t enough. Learn the essence of OO programming: inheritance, polymorphism, and encapsulation.

3. Eclipse ADT (Should Have)

Eclipse ADT is the IDE of the new SAP Developer. Some objects can only be created in this environment.

While transitioning from SE80/SE38 can be challenging, the benefits far outweigh the initial struggles. For those working on S/4HANA Public Cloud Edition or BTP ABAP Environment, Eclipse ADT is mandatory. Even for older ERP versions, experimenting with Eclipse can speed up your development process.

For insights, follow @ThFiedler .

4. ABAP Cloud (Could Have)

ABAP Cloud is SAP’s vision for the future. If you're working with S/4HANA On-premise 2022, S/4HANA Cloud (Public or Private), or BTP ABAP Environment, ABAP Cloud isn’t just an option—it’s often the only option.

This model aligns with SAP’s clean core philosophy and facilitates seamless upgrades by using released objects for cloud compatibility.

Start your journey here: SAP ABAP Learning Journey.

5. New Extensibility Model + Clean Core (Could Have)

Extensibility is critical in S/4HANA On-premise 2022 and Cloud Editions. SAP’s new architecture emphasizes extensibility through tiers, released objects, and best practices like developer extensibility, key user extensibility, and side-by-side extensibility.

Learn more here: Clean Core Extensibility Learning Journey.

6. SAP BTP (Could Have)

Understanding SAP BTP is essential, especially for its impact on SAP developers. Familiarize yourself with its services, architecture, and integration with ABAP Environment.

Here’s a great resource: Discover SAP BTP.

7. Code Pushdown (Must Have)

Techniques like CDS Views and AMDP are still underutilized, despite their clear advantages in optimizing performance. Using SQL Script to push processing to the database minimizes application-layer workload and enhances scalability.

Explore this topic further in the ABAP Learning Journey.

8. Clean Code, ATC, and ABAP Unit Tests (Must Have)

Quality is non-negotiable. Utilize tools like ATC and follow the Clean ABAP Style Guide for consistent and efficient code. Automating tests with ABAP Unit can improve code reliability while saving time during regression testing.

9. RAP (Should Have)

The ABAP RESTful Application Programming Model (RAP) is SAP’s framework for building enterprise apps and services. It combines CDS, OData, and modern programming concepts into a unified model.

For Public Cloud and BTP ABAP Environment, RAP is mandatory since SEGW is unavailable. 

For insights, follow @Andre_Fischer 
Start here: Building Apps with RAP.

10. Interface Knowledge (Could Have)

Modern projects demand an understanding of synchronous/asynchronous interfaces, inbound/outbound communication, and protocols like HTTP, REST, SOAP, and OData. Familiarity with Postman and API Hub (api.sap.com) is highly recommended.

11. Adobe Forms (Could Have)

Adobe Forms remains SAP’s go-to tool for form printing. Stay updated with features like fragments, Adobe LiveCycle Designer, and Adobe Service on BTP.

12. Certifications (Could Have)

Certifications validate your expertise, benefit your career, and strengthen your company’s position as an SAP partner. Consider the ABAP Cloud Certification:
ABAP Cloud Certification.

13. Fiori Elements (Could Have)

Low-code tools like Fiori Elements simplify app development. Master the floorplans, deployment options, tiles, catalogs, and integration with RAP.

Start here: Fiori Elements Learning Journey.

14. Other Technologies (Won’t Have)

While tools like CAP, SAP Integration Suite, and Work Zone are valuable, focus first on ABAP and RAP. Being excellent at core skills while diversifying into others is key.

15. AI in SAP Development (Could Have)

AI tools can significantly enhance your productivity. Whether analyzing requirements, automating tests, or writing code, tools like SAP Joule can become invaluable copilots.

Conclusion

For some, this roadmap may seem daunting, but embracing these skills is essential to remain relevant as an SAP Developer. Start your learning journey now and take advantage of the abundant free, high-quality resources available.

By mastering these 15 topics, you'll position yourself as an SAP Developer of the future!







 

 

7 Comments
Labels in this area