SM30 Table maintenance
Process transports between systems
To best adapt your SAP system to the internal and external requirements of your organization, further table-related customizing is required. Here, SAP offers the possibility of logging changes to critical tables through table logging.
SAP Basis Support ensures secure operation of the SAP system landscape. For proper operation of the SAP system, the database and operating systems must be checked on a daily basis.
Time buffers for job chains lead to long runtimes
Today, most customers rely on an infrastructure abstraction layer, whether it's VMware or one of the cloud hypervisors. So base administrators need to know how to provision and manage systems in the cloud.
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.
To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.
In the case of client settings, you should ensure that the production client is protected against overwriting and that changes are only approved via the transport management system (TMS) to ensure traceability. In the interests of system security, changes to repository and client-independent objects should also not be permitted. The use of eCATT and CATT should also be at least restricted, as allowing them can lead to significant database changes.
Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".
The coverage of old core tasks (such as security or compliance) and new core tasks (such as cloud or mobility) must be increased in the sense of a holistic consideration.
This frees up SAP technology teams to build new skills.