SAP Basis What happens if an SAP job terminates unexpectedly? - SAP Stuff

Direkt zum Seiteninhalt
What happens if an SAP job terminates unexpectedly?
Operating systems and databases
A trick often used by administrators is to allow for time buffers before starting the next job. The buffer times are necessary because it is not possible to predict exactly how long a job will take to complete, since the duration depends on many incalculable parameters. Since it makes little sense to run backups and SAP jobs at the same time, these tasks are usually done one after the other rather than in parallel. In more complex environments, data backup durations, time buffers and job runtimes add up to such an extent that the time available is no longer sufficient to perform all activities within the available time corridor. Tools that work with status dependencies and then automatically start the next job when its predecessor job has been processed without errors can help here.

But when it comes to the intricacies of large SAP environments, Ansible quickly reaches its limits. If you want to use Ansible to implement simple automations - starting and stopping SAP environments, for example - you have to put up with a lot of manual effort and complicated scripts.
Authorizations
All the roles that contain the string "ADM" are considered critical, as they usually refer to administrative roles. When identifying critical SAP permissions, profiles and roles, it should be noted that SAP does propose a concept for names, but this is not always taken into account by applications or its own developments.

"Shortcut for SAP Systems" makes many tasks in the area of the SAP basis much easier.


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".

On the other hand, a self-created e-learning offer offers the possibility to design it completely by itself and tailor it to the company's own needs.

SAP Stuff
Zurück zum Seiteninhalt