COMPLY WITH ORDER OF OPTIMISATION
SWU0 Simulation of an event
In many companies, the SAP system is the linchpin of everyday business. To ensure that the system is available at all times, an SAP Basis team ensures its smooth operation.
The SAP basis requires a separation layer to upstream and downstream IT departments, which is clearly defined. In the direction of the infrastructure, for example, this can be the upper edge of the operating system. This distinction must also be drawn in the direction of application development. Here there are various services offered today by the SAP basis, which are more closely related to application, such as control of background processing, transport or also the automation of certain activities. In principle, it is necessary to examine which tasks can continue to be carried out in the SAP basis due to the requirements and which can be given in expert units.
Development guidelines
In addition to acute project support, our SAP Basis team can also serve as co-managers. With co-management, your SAP administrator and an abilis employee share the day-to-day tasks.
To configure the SAL, please use transaction RSAU_CONFIG (formerly SM19) as of SAP Release 7.50. It is recommended to activate the cross-user logging with minimum settings and to record all audit classes for users with extensive authorizations, such as SAP standard and emergency users. These settings should always be configured on a cross-client basis.
Tools such as "Shortcut for SAP Systems" are extremely useful in basic administration.
The transactions are stored in blocks of the chain.
Why is an emergency user approach important? There are several scenarios in which the use of an emergency user with extended rights is useful: In urgent cases, it is often necessary to be able to quickly make changes to the system that are outside the user's actual field of activity.