Modern ABAP Development: From Legacy Code to Clean ABAP & RAP

Introduction

Modern ABAP development has become a key requirement with the transition to S/4HANA and SAP BTP. The SAP ecosystem has undergone a massive transformation over the last decade. With the arrival of S/4HANA and the SAP Business Technology Platform (BTP), the role of an ABAP developer has evolved. It is no longer just about “making the code work”—it is about building sustainable, scalable, and cloud-ready solutions.

In this post, we’ll explore the pillars of modern ABAP development and demonstrate why transitioning from legacy patterns to modern syntax is a necessity for any forward-thinking business.

For organizations running S/4HANA systems, these changes are no longer optional — they directly impact performance, maintainability, and long-term system stability.

1. The Evolution of Syntax: “Old” vs. “New”

The release of ABAP 7.40 marked a turning point. If you are still using explicit data declarations at the top of your includes or manual loops for simple calculations, you are missing out on significant readability and performance gains.

Let’s look at a practical comparison. Imagine we need to fetch sales order data and calculate a total value.

The Legacy Approach (Pre-7.40)

This method is verbose and requires the developer to manage memory and types manually at every step.

ABAP

" 1. Explicit data declaration
DATA: lt_vbak TYPE TABLE OF vbak,
      ls_vbak TYPE vbak,
      lv_total TYPE netwr.

" 2. Fetching data
SELECT * FROM vbak INTO TABLE lt_vbak 
  WHERE erdat = sy-datum.

" 3. Processing with a manual loop
LOOP AT lt_vbak INTO ls_vbak.
  lv_total = lv_total + ls_vbak-netwr.
ENDLOOP.

WRITE: / 'Total Value:', lv_total.

The Modern Approach (ABAP 7.40+)

Modern ABAP uses Inline Declarations and Constructor Operators to make the code concise and functional.

ABAP

" 1. Inline declaration & Modern SELECT
SELECT netwr FROM vbak 
  WHERE erdat = @sy-datum 
  INTO TABLE @DATA(lt_netwr_tab).

" 2. Using the REDUCE operator for instant calculation
DATA(lv_total) = REDUCE netwr( 
                   INIT val = 0 
                   FOR wa IN lt_netwr_tab 
                   NEXT val = val + wa ).

WRITE: / 'Total Value:', lv_total.

Why the Modern Way Wins: It reduces “boilerplate” code. By using host variables (indicated by @) and functional operators like REDUCE, VALUE, or FILTER, the developer spends less time managing variables and more time solving business logic.

2. Shifting Logic to the Database: CDS Views

The old paradigm was “Bring the data to the Application Layer.” The S/4HANA paradigm is “Push the logic to the Database.”

Core Data Services (CDS) is the backbone of modern SAP development. It allows us to build rich data models that include associations and aggregations. By using CDS, you leverage the in-memory power of HANA, ensuring your applications remain lightning-fast even when processing millions of records.

3. The Gold Standard: ABAP RESTful Programming Model (RAP)

If you are building new Fiori apps or OData services, RAP is the path forward. It replaces older models like SEGW (Gateway) and provides a standardized way to build applications that are:

Draft-enabled: Allowing users to save progress automatically.
Cloud-Ready: Compatible with both on-premise S/4HANA and SAP BTP.
Highly Structured: Using “Managed” or “Unmanaged” scenarios to handle everything from fresh tables to legacy BAPIs.

4. Adopting “Clean ABAP” Principles

At Solvium, we believe that code is read far more often than it is written. Following “Clean ABAP” (inspired by Robert C. Martin’s Clean Code) is essential for long-term maintenance:

Small Methods: A method should perform one single task.
Meaningful Naming: Favor lv_sales_order_id over lv_vbeln.
Unit Testing: Utilizing ABAP Unit ensures that a bug fix today doesn’t break a critical process tomorrow.

Conclusion: Future-Proofing Your SAP Landscape

The transition from a “Classical Developer” to a “Modern Developer” requires a mindset shift. Whether it’s learning ABAP Cloud, mastering the BTP Environment, or refactoring legacy “spaghetti code,” the goal is the same: building agile, high-performance systems.

At Solvium, we specialize in bridge-building—helping companies transition their legacy SAP environments into the modern era using these very principles.

I’d be interested to hear how other teams are approaching this transition — especially when modernizing large legacy landscapes.