Defined service level agreements (SLAs)
Installation/upgrade of the SAP systems based on HANA Platform
Finally, the presentation layer contains software components for the graphical presentation of the application. It thus forms the interface to the users (GUI).
In order for your SAP system landscape to function permanently, it requires error-free installation and regular support. You can rely on these services:
Maintenance of profiles and operation modes
SAP's client concept enables a SAP system to be split into several logical sub-systems - clients. These subsystems can be used independently and in isolation as separate systems. But how should non-client transactions be treated? How can you prevent one client from accessing the other and why should you want to prevent that? In this blog post, I will answer these questions and discuss some negative examples. Why is it important to consider independent transactions separately? Imagine that every one of your employees is allowed to create or change a client in the production system, or worse, both. Creating and modifying a client in the production system is authorised and documented - you wonder what could possibly go wrong? The risk in this case is a loss of integrity of system and data, loss of confidentiality: With each new client, Superuser SAP* lives up to its comprehensive, cross-client rights and the assigned standard password.
In order to guarantee an optimal operation process a permanent operation is recommended. We are ready to take over the monitoring including on-call service for you at any time.
Tools such as "Shortcut for SAP Systems" complement missing functions in the SAP basis area.
The SAP basis is supported by an IT service and IT product catalogue, which describes the scope of the SAP basis.
For such applications, SAP provides other, better options.