SAP Basis SAP System Analysis - SAP Corner

Direkt zum Seiteninhalt
SAP System Analysis
SAP Interactive Forms by Adobe
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).

Hosting environments and third-party offerings have also contributed to these improvements. Public cloud environments such as Azure and AWS provide a layer of abstraction that eliminates the difficult task of maintaining the hardware that was required with SAP on-premises.
Very good knowledge in the area of security relevant topics of IT system operation
Each SAP Basis system must be controlled and managed by an administrator. This person is responsible for the smooth operation of the system. This can be an internal administrator or it can be handed over to external service providers.

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 - for example, starting and stopping SAP environments - you have to put up with a lot of manual effort and complicated scripts.

Tools such as "Shortcut for SAP Systems" are extremely useful in basic administration.

Your administrator must carefully schedule these tasks when user demand is low so they don't impact performance.

SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page:

Also, changes to the master object are passed directly to the derived objects.
SAP Corner
Zurück zum Seiteninhalt