HANA News Blog

RISE with SAP: Roles & Responsibilities

Jens Gleichmann • Mai 24, 2024

Essential comparison

For every possible RISE with SAP customer it is essential to know the difference of the status quo system construct (on-prem self managed / hosted or managed by a MSP) and the RISE offering with a lot of excluded tasks or tasks with additional costs. If you don't need this tasks, it might be a perfect solution, but our experience is that most customers need some of the services with extra costs.


There is a list called roles and responsibilities (public information) which is listing all the services which are defined as :

  • Standard services
  • SAP Cloud Application Services ("CAS") (can be performed by customer)
  • Optional Services (can only be performed by SAP; no CAS; additional costs)
  • Additional Services (can only be performed by SAP; no CAS; additional costs)
  • Excluded Tasks (can only be performed by the customer)
  • not offered


Some of this tasks are defined as "Excluded Tasks" which you may think they are unimportant and not business critical. But if you ask any of your architects, security officers or SAP basis colleagues they will tell you that the sizing, monitoring and patching of the server infrastructure (VM) / OS is more than important for a stable operating system. The customer is responsible for this tasks!

Now the question is why SAP is not offering such services as standard when this tasks are so important? At first they only apply to additional server instances to run non-SAP applications. This may only apply to a very small group of customers who need this.

But why the mentioned tasks are so important?

  1. Sizing

If the sizing of your instance does not fit to your workload needs, you will end up in a resource bottleneck which can lead to wait times or in the worst case to a failure due to OOM (Out of memory).


   2. OS patches and security updates / antivirus pattern updates

Since NIS2 is a omnipresent topic, these aspects fall under it. It is important that the systems are kept up to date and regularly maintained to close known security gaps. For essential establishments, fines of up to 10 million euros or 2% of annual worldwide turnover (whichever is greater) may be imposed. You'd think that should be important, right? In comparison to the systems running SAP applications, SAP is not offering an OS or AV pattern patching.


   3. OS Monitoring

The as for the patching is valid for the OS monitoring of non-SAP applications. It is an excluded task which is in the responsibilities of the customer! But how the customer with a cloud only strategy can monitor this? A lot of effort on customer side or another MSP which takes this as his responsibility.


Summary

For all customers consuming the standard service of running ERP or S/4HANA with RISE some standard monitoring is included. But please take into account that every special metric or KPI might be a special request for SAP and everyone understand a different depth when talking about monitoring. It can mean a 5s or a 60s sampling. What does it mean to monitor the disk or network utilization? IOPS? service time? throughput? package size? number of packages? Please be specific and compare apples to apples. Don't be surprised if you get not what you expected because you will get what you signed and paid for if you not ask for details.


Hardware operation tasks RISE
Operating system tasks

SAP HANA News by XLC

HANA OS maintenance
von Jens Gleichmann 27 Sept., 2024
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.
News for the hyperscaler AWS, GCP and MS Azure
von Jens Gleichmann 20 Sept., 2024
news instances with SAPS, memory and CPU values in comparison
Unforeseen cloud cost increases
von Jens Gleichmann 13 Sept., 2024
Unforeseen cloud cost increases - RedHat announced back in January this year that the costs for cloud partners will be changed effective April 1, 2024. They called it scalable pricing.
HANA 2.0 SPS08 Roadmap
von Jens Gleichmann 13 Sept., 2024
SAP HANA 2.0 SPS08 Roadmap Q4 2024
SUSE maintenance
von Jens Gleichmann 16 Aug., 2024
How to interpret the SUSE Lifecycle
RISE with SAP: Roles & Responsibilities
von Jens Gleichmann 24 Mai, 2024
For every possible RISE with SAP customer it is essential to know the difference of the status quo system construct (on-prem self managed / hosted or managed by a MSP) and the RISE offering with a lot of excluded tasks or tasks with additional costs. If you don't need this tasks, it might be a perfect solution, but our experience is that most customers need some of the services with extra costs.
Performance degradation after upgrade to SPS07
von Jens Gleichmann 29 Apr., 2024
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.
vm.swappiness settings
von Jens Gleichmann 24 März, 2024
The details of swapping in the context of SAP HANA
SUM tooling with target HANA
von Jens Gleichmann 18 März, 2024
Numerous IT projects such as S/4HANA projects or HANA migrations will go live over the Easter weekend. Mostly this tasks will be controlled by the SAP provided SUM tool. The SUM is responsible for the techn. migration/conversion part of the data. Over the past years it become very stable and as long as you face no new issues nearly every technical oriented employee at SAP basis team can successfully migrate also bigger systems. In former times you needed a migrateur with certification which is no longer required. As long as all data could be migrated and the system is up and running the project was successful. But what does the result look like? Is it configured according to the best recommendation and experience? Is it running optimized and tuned?No, this is where the problem begins for most companies. The definition of the project milestone is not orienting on KPIs. It is simply based on the last dialog of the SUM tool, which states that the downtime has ended and all tasks have been executed successfully.
Abstract SQL Plans
von Jens Gleichmann 13 Dez., 2023
The feature plan stability is not a new one, but can help you in case of an revision update/upgrade, if you recognize big performance degradations. But you have to activate this feature at least 1-2 weeks before the maintenance to capture the SQLs and the execution plan. You can compare the plan performance and apply the execution plan with the best performance. You can also use it as always on feature in daily operations. This may be required due to changes in data over time which may cause the query optimizer to propose different execution plans which may have a negative impact on performance and memory consumption of a query. An additional preparation step can be used to apply filters so that only specific queries are captured. In the background execution statistics are recorded so that the performance of the query can be measured and the best execution plan can
more
Share by: