HANA News Blog

From Complexity to Clarity: Optimizing the R+R List for SAP Cloud ERP

Jens Gleichmann • 25. September 2025

Check out how to optimize the R+R List for SAP Cloud ERP

In transformation projects like SAP RISE / SAP Cloud ERP, the Roles & Responsibilities (R+R) list often serves as the backbone for collaboration between customer, partner, and SAP. Yet too often, this list is treated as a static document rather than a living framework. Sometimes nobody knows exactly what was defined by the time signing the contract. By continuously questioning, refining, and contextualizing R+R, organizations can reduce ambiguity, close expectation gaps, and create a solid foundation for accountability. But this has to be done before signing the contract and not after the going live.


Every single customer signed a PCE contract negotiated different parameters and bought different CAS packages - oh sorry since July “CAS (=Cloud application service)” are now called “Packaged Services”. Be aware that all needed Packaged Services are discussed and included in the contract. Otherwise there can be extra costs.



The current R+R list for the tailored option (v7 2025) consists of 1084 services (not counting empty lines or titles) with this distribution:


  • 59 pages (-4 pages for cover and legends) => 55 pages content
  • Service Management: 17 services
  • Managed Infrastructure: 73 services
  • HANA : 114 services
  • SAP HANA: Accelerator for SAP ASE (AFA): 11 services
  • DB (Excluding SAP HANA and Sybase IQ ): 19 services
  • DB2: 15 services
  • Basic (Core Technical Operations): 122 services
  • NW (NetWeaver Operations ABAP and Java): 52 services
  • SPROV (Server Provisioning (aka IaaS)): 36 services
  • CAS (Cloud Application Services): 19 services
  • Move (Movement Services for System Conversion and Transition): 13 services
  • X1 - X64 (3rd party software) : 593 services

Regarding X1 - X64 : 3rd party software is a bit misleading. Because this includes SAP software like BTP, SF, CALM, Content Server, ADS, ETD and many more.   

But first things first. If you made a deep dive into the R+R list and compare it to your current service catalog which you already have from your current MSP or you created your own internal one, you will notice that there are gaps. This means not only that some tasks costs extra. This means also a lot of services are not needed because there is no need for you to run Sybase or DB2 or you have no third party product which leads to the conclusion that 593 services are not valid for you.


But you not only have to check which services are valid in the R+R. You have also to check which services are not covered or even not listed. For this you have to work close together with all technical teams, if there is currently no service catalog or an outdated version.


Even if a service is covered means not that the amount of executions are also covered. For instance Service HANA_1_1.04 ("Partition tables (technical execution)") stated out "If required as a consequence of extensive table growth; One (1) execution in One (1) table per SID, per year included; any further requests will be charged separately" which means that you have to pay extra if there is more than one execution in one table per SID.   

Over the last years the list changed continuously which means not only that services were added. Also some of them were removed - yes not only marked as excluded - just removed. The valid list is the list which were transferred to you with your contract. Only this is valid for you.

Not covered means then excluded, removed or not listed. But who is responsible for this tasks? The customer has full responsibility to all tasks which are not covered. You still need experts who e.g.:


  • Design table partitioning strategy/architecture
  • Identify, analyze and optimize expensive SQL-statements to improve application performance
  • Design NSE strategy
  • provide commands to frequently page out old data / partitions (NSE)
  • run proactive Health Checks
  • run proactive index checks for index recommendations

Nearly all covered tasks have to be triggered via SR within provided time slots with lead times. The initiator is still the customer with full responsibilities.


Conclusion / Summary

You still need your SAP Basis experts or external partners even if you are use an SAP Cloud ERP offering. Please consider this in your cost calculation! You need to check this list multiple times with multiple experts to get all perspectives for the complete picture. My recommendation is to involve multiple experts for licensing , evaluation of the R+R, sizing, migration QA and for the operations. Four weeks aren't enough to validate all contract components. Find your blind spots and take the time you need to review all contract components.

SAP HANA News by XLC

Why Databases Need Optimizer Statistics – With a Focus on SAP HANA
von Jens Gleichmann 28. Mai 2025
In the world of modern database management systems, query performance is not just a matter of hardware—it’s about smart execution plans. At the core of generating these plans lies a critical component: optimizer statistics. This article explores why databases need optimizer statistics, with particular emphasis on SAP HANA, while drawing parallels with Oracle, Microsoft SQL Server (MSSQL), and IBM DB2.
HANA OS maintenance
von Jens Gleichmann 27. Mai 2025
Please notice that when you want to run HANA 2.0 SPS07, you need defined OS levels. As you can see RHEL7 and SLES12 are not certified for SPS07. The SPS07 release of HANA is the basis for the S/4HANA release 2023 which is my recommended go-to release for the next years. Keep in mind that you have to go to SPS07 when you are running SPS06 because it will run out of maintenance end of 2023.
HANA performance degradation after upgrade to SPS07+SPS08
von Jens Gleichmann 27. Mai 2025
With SPS06 and even stronger in SPS07 the HEX engine was pushed to be used more often. This results on the one hand side in easy scenario to perfect results with lower memory and CPU consumption ending up in faster response times. But in scenarios with FAE (for all entries) together with FDA (fast data access), it can result in bad performance. After some customers upgraded their first systems to SPS07 I recommended to wait for Rev. 73/74. But some started early with Rev. 71/72 and we had to troubleshoot many statement. If you have similar performance issues after the upgrade to SPS07 feel free to contact us! Our current recommendation is to use Rev. 74 with some workarounds. The performance degradation is extreme in systems like EWM and BW with high analytical workload.
The HANA Optimizer is one of the core components of the HANA database. It determines how SQL is exec
von Jens Gleichmann 25. Mai 2025
A database optimizer behaves similarly to the navigation system in your car. You use various parameters to determine which route you want to take to reach a particular destination. Potential additional costs for tolls and ferries also play a role, as do other limitations such as the vehicle's height, length, and width. From these input parameters, the navigation system determines the optimal route based on current traffic information (traffic volume, construction sites, congestion, accidents, closures, etc.), weather conditions, and the length of the route. This means that with exactly identical input parameters, different routes, costs, and thus different travel times can arise depending on the given conditions.
Is NSE worth the effort or is the better question: Do you know your cost per GB of RAM?
von Jens Gleichmann 18. April 2025
Most of our presentations on data tiering projects end with these typical questions: How much we will save? How fast can it be implemented? Is the effort worth it over time? My counter question: "Do you know how much 1 GB of memory costs your company per month or year?" => how much memory we have to save to be beneficial?
Buch: SAP HANA Deepdive
von Jens Gleichmann und Matthias Sander 30. März 2025
Unser erster Buch mit dem Titel "SAP HANA Deepdive: Optimierung und Stabilität im Betrieb" ist erschienen.
More time to switch from BSoH to S/4HANA
von Jens Gleichmann 7. Februar 2025
Recently handelsblatt released an article with a new SAP RISE option called SAP ERP, private edition, transition option. This option includes a extended maintenance until the end 2033. This means 3 years more compared to the original on-prem extended maintenance. This statement was confirmed by SAP on request of handelsblatt, but customers receive more details, such as the price, in the first half of the year. This is a quite unusual move of SAP without any official statement on the news page. Just to raise more doubts? Strategy? However a good move against the critics and the ever shorter timeline. Perhaps it is also a consequence of the growing shortage of experts for operating and migrating the large number of systems.
Optimize your SAP HANA with NSE
von Matthias Sander 15. Januar 2025
When it comes to optimizing SAP HANA, the balance between performance and cost efficiency is critical. I am happy to share a success story where we used the Native Storage Extension (NSE) to significantly optimize memory usage while being able to adjust the sizing at the end. The Challenge: Our client was operating on a 4 TB memory SAP HANA system, where increasing data loads were driving up costs and memory usage. They needed a solution to right-size their system without compromising performance or scalability. The client wanted to use less hardware in the future. The Solution: We implemented NSE to offload less frequently accessed data from memory. The activation was customized based on table usage patterns: 6 tables fully transitioned to NSE 1 table partially transitioned (single partition) 1 table transitioned by specific columns
SAP HANA NSE - a technical deepdive with Q&A
von Jens Gleichmann 6. Januar 2025
SAP NSE was introduced with HANA 2.0 SPS04 and based on a similar approach like data aging. Data aging based on a application level approach which has a side effect if you are using a lot of Z-coding. You have to use special BADI's to access the correct data. This means you have to adapt your coding if you are using it for Z-tables or using not SAP standard functions for accessing the data in your Z-coding. In this blog we will talk about the technical aspects in more detail.
The SAP Enterprise Cloud Services Private Cloud Customer Center (PC3) - a new digital delivery
von Jens Gleichmann 5. Januar 2025
The SAP Enterprise Cloud Services Private Cloud Customer Center (PC3) - a new digital delivery engagement model dedicated to manage service delivery for RISE with SAP S/4HANA Cloud, private edition customers.
more