Continuous improvement of system availability and performance
SM62 Event History
In addition to purely administrative tasks, SAP administrators are also responsible for communication. They cooperate with the company's internal support departments and work with them on ways to help users solve and avoid any problems and pitfalls when using SAP solutions. For internal purposes, the SAP administrator also prepares documentation and uses it to search for errors, the cause of which he or she tries to combat. If necessary, he or she communicates with decision-makers in the company in order to be able to implement improvements, adjustments and optimizations with regard to the SAP software.
In practice, it is quite possible that the target specifications defined in the security concept do not match the current actual status. Therefore, especially with regard to SAP security, it must always be checked whether the necessary SAP basic settings also correspond to the minimum level. Although a manual check is possible, it is very time-consuming because the necessary regularizations have to be read, interpreted and technically implemented. The Security Architect - part of the Xiting Authorizations Management Suite (XAMS) software solution developed by Xiting - offers you the possibility to precisely examine the current status of the SAP Basis settings with the help of the integrated check mode, whereby it is also possible to check several systems via RFC, starting from a central system. The scope of the check of system settings and system security includes not only the SAP Basis settings presented here, but also other SAP Basis settings. The scope of the check mode can be extended by self-defined check IDs.
SCOPE OF SERVICES OF SAP BASIS
By establishing a new role concept and building new roles, the SAP basis has the skills necessary to support new tasks and topics as well as to operate new technology and service forms. The relevant roles are listed below.
On www.sap-corner.de you will also find useful information about SAP basis.
I recommend that you schedule the background job PFCG_TIME_DEPENDENCY with the report RHAUTUPD_NEW. Scheduling the RHAUTUPD_NEW report with two variants has proven to be a best practice: Once a day before users log on for the first time (e.g. midnight or very early in the morning). This way the users are synchronized once a day. Once a month (or even once a week) with the option "Perform cleanup", so that obsolete profiles and user mappings are regularly cleaned up. Also handy: If the naming conventions of your roles allow it, you can also align the report according to different time zones. For example, I have a customer who runs the user synchronization for his users in the USA and Asia at different times, so that the daily business of the respective users is not disturbed.
Tools such as "Shortcut for SAP Systems" complement missing functions in the SAP basis area.
This scenario allows you to estimate and minimise the time and effort required to load support packages.
We set about creating detailed playbooks for all common scenarios - installations, portals, upgrades and migrations - and platforms.
To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.