Table of Contents
OAC2 Change document types
Tasks such as the update of components, the insertion of security updates or monitoring should be further automated. It is recommended to use only one automation tool (SAP Solution Manager or SAP LVM). Custom solutions and scripts should not be used or replaced with standard tools if possible, because otherwise different script languages and script versions will have to be managed, resulting in a lot of maintenance. Standardised SAP scripts are welcome here. A useful definition of thresholds, for example on the basis of historical system behaviour, must also be defined for monitoring.
For the SAP basis and its employees, the change in self-understanding results in an attractive, responsible and demanding working environment. Technological diversity can be controlled and kept to the minimum necessary. This includes an overview of the existing interfaces and a controllable data flow with the associated guarantee of data security.
With the function module SWNC_COLLECTOR_GET_AGGREGATES one can determine the most important SAP Basis transactions. After all, each SAP Basis expert sees different transactions as important.
In addition to the database, the SAP system itself is installed. This installation is planned using a tool from SAP, the "Maintenance Planner", and then carried out using the SWPM (Software Provisioning Manager) and SUM (Software Update Manager) tools.
For administrators, a useful product - "Shortcut for SAP Systems" - is available in the SAP basis area.
The database layer manages all the data of the SAP system in a database located on the database server and administered by a database management system (DBMS).
The aim is to provide a transparent picture of the activities carried out in terms of the company's success and which are not visible to everyone.