Knowledge & Trends

Clean core with SAP RAP: future-proof ABAP development

Jun 2026 | Blog

Blogartikel – Clean Core im SAP-Alltag

Have you ever looked at your custom SAP developments and wondered whether the next support package or the S/4HANA upgrade will end in chaos? In many companies, there’s understandable nervousness ahead of system releases. The reason: rigid modifications in the ABAP code, built up over years, block updatability and drive up support costs.

With the SAP RAP (RESTful Application Programming Model), you tie the innovative power of your business team to an upgrade-safe IT architecture. You keep your digital core clean (Clean Core) and noticeably reduce maintenance effort in day-to-day business.

From the old ABAP monolith to a modern ABAP Cloud architecture

In the classic SAP world, business logic, database, and user interface were often inseparably fused together. What worked in the old ERP system becomes an innovation killer under S/4HANA.

SAP RAP breaks up these old structures. As a modern development standard, it strictly separates data modeling (via Core Data Services) from the UI layer and the actual business logic. The result: applications that are cloud-ready and modular from the ground up. Whether you develop on-premise or on the SAP Business Technology Platform (BTP), the architecture stays the same.

The right implementation: why the “managed scenario” is almost always the first choice

One of the most important architecture decisions in day-to-day project work is choosing the right implementation type. This is often where the wheat is separated from the chaff, because the decision largely determines the maintenance effort later on:

1. The managed scenario (the gold standard)

When you set up processes from scratch, the SAP RAP framework does all the work for the standard data operations (CRUD). The best part: the powerful draft handling (automatic interim saving when connections drop) and the automated locking logic for exclusive data access come completely out of the box here. That saves countless hours of development time and eliminates typical support tickets from frustrated users.

2. The hybrid models (a bridge for legacy systems)

What happens when existing logic or old BAPIs have to be integrated? Experienced consultants don’t jump straight into the fully self-managed unmanaged scenario. Instead, we use intermediate stages such as managed with additional save or managed with unmanaged save. That way you get the full convenience of the framework (such as automatic locking in the standard) and hook the old legacy logic in cleanly only at the moment of saving.

3. The unmanaged scenario (the last resort)

Only when the framework’s standard process absolutely doesn’t fit the requirements is development done fully unmanaged. Here, full control, but also the entire programming effort for locks and draft logic, lies in the developer’s hands.

UI at the push of a button and easy extensibility with Fiori Elements

A huge lever for the efficiency of your IT project is the tight integration of RAP with Fiori Elements. Using so-called UI annotations directly in the CDS view, the user interface can be generated automatically in no time. For standard requirements, you often no longer need a separate front-end developer.

Should the requirements of the business department grow, the architecture can be extended at any time thanks to the integrated extensibility concept. New fields or additional validations can be added cleanly, without putting the existing standard process at risk.

Best Practices

▷ Follow the “managed first” principle

Always try to use the managed scenario or its hybrid save extensions (additional/unmanaged save). Every line of code the framework takes on for you is a line you won’t have to patch later.

▷ Make consistent use of draft handling

Enable draft handling for transactional apps right at the start in the managed approach. It dramatically increases user acceptance and protects against data loss in day-to-day business.

▷ Build up CDS know-how in your team

Since SAP RAP is fundamentally built on Core Data Services, performance stands or falls with the quality of the data model. Invest in training early on.

▷ Keep UI annotations close to the data

Use the ability to define UI structures directly in the backend via metadata extensions. That keeps your Fiori landscape clean and easy to maintain.

Conclusion

Less support frustration, more innovation speed with SAP RAP.

Switching to the SAP RESTful Application Programming Model is not just an IT plaything, but a strategic investment. By leaving standard functions such as locking logic and draft handling to the framework, you relieve your developers of routine tasks. SAP RAP safeguards your custom developments, keeps the core clean, and ensures that your system continues to run in a stable, high-performing way even after the next SAP upgrade.

Author: Alisa Reckinger | Last updated: 06/30/2026