SAP Basis SWPC Continue workflows after system crash - SAP Stuff

Direkt zum Seiteninhalt
SWPC Continue workflows after system crash
Maintenance and transport of application and system modifications
In order to ensure the stability of the systems and to reduce the risk through proprietary developments, release and patch management must be implemented. Standardised procedures can help to introduce proprietary developments, such as test strategies or service level agreements (SLAs). It is also important to align the productivity setting of customer applications with the maintenance windows and RTO (Recovery-Time-Objective).

Soft skills in particular also play an important role in this job description. Communication skills are very much in demand on a day-to-day basis, because SAP administrators are often in close contact with customers and have to respond to their wishes and questions. They also need the ability to work in a structured manner and to find creative solutions and decisions. Continuous training in the field is advisable in order not to lose touch.
Dumps, system logs
In the area of SAP Basis it is necessary to make temporary changes in the security settings of the clients and systems in the course of system updates. You can use the system changeability variable to specify whether changeability of cross-client data, such as programs or menus, as well as client-independent customizing is allowed.

"Shortcut for SAP Systems" makes it easier and quicker to complete a number of SAP basis tasks.


SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page: "www.sap-corner.de".

In the case of unprotected data communication paths between different client and server components of the SAP system that use the SAP protocol RFC or DIAG, the data exchange takes place in plain text and there is a risk that this can be read.

SAP Stuff
Zurück zum Seiteninhalt