With good documentation in place, the solution offers good technical support to its usersCPU architecture is an area where the solution currently has some issues. Improvement in CPU architecture could improve the performance side and the adherence to the parameters set by SAP. As suggested by SAP, we should do HANA mini checks on a daily or weekly basis. All the parameters related to HANA should be equal to improve performance. So, some of the parameters I can see on the SAP side are related to memory, and so we have to check on each landscape whether the parameters related to SAP are properly set or not. Regarding the right CPU from AWS and SAP recommended nodes, we have to check whether the performance is good or not because we have to give this almost on HANA since, on some side, we have to be swapping that on voice level also, and so that screening part is a requirement from OS/DB side. In short, we have to check all parameters. My solution is IOPS related to EC2. So I have just done a very good optimization. I have seen some parameters related to Linux that is from SAP side, where the problem is very fast, and CPU load is very low. So that is an OS/DB recommendation parameter from the SAP that it should be set over there on all systems. As a basic start, we have to check OS/DB recommendation settings, and everything should be kept on. Those experienced in SAP S4HANA need not worry about any part. I think overlay IP should be linked to gateway web architecture. It should be in a proper way to the community for the security part. Apart from that, we have to follow Amazon and SAP books. There have to be some adjustments made from the finance and GRC side. So, we have to check some of the functional sides and whether these parameters are properly set in for SAP s1 in terms of logistics, MRV, and some of the code. I can recommend that SAP's 86 custom code should be a proper way to develop a very good experience going online for the custom tools. So, it would be good to improve such features and everything. Also, the system should not be at any end of support since it will impact its performance. I have faced some of the, you know, clients, where they have some end of support, comes into 7209, and they just back it up. I need to get some extended support from the SAP, and some software should be there. So before the end of maintenance, everybody has to awaken all the features of the solution. On a daily production side, we can do this maintenance activity, whether it may be outdated or not outdated, and support patches should be done properly.
