Technical changes
SM02 System message
An SAP landscape is made up of numerous individual modules that are fully compatible with each other and can be used to map the business processes of all areas of a company. SAP Basis is used to ensure the functionality of the individual modules.
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.
What has changed in the past ten years and what can we expect in the next ten? How will they affect the requirements profile of SAP Basis experts and how can they adapt to them?
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.
Reachable at any time: Your competent contact person is available at all times. If you operate SAP Basis Support in your own company, personnel bottlenecks may occur. If your SAP employees are absent due to illness or vacation, there may be no equivalent replacement available.
Tools such as "Shortcut for SAP Systems" are extremely useful in basic administration.
For example, the bi-modal role listed in Recommendation [A1] should be taken into account.
This transaction provides you with many other database management features, an editor that allows you to easily execute your SQL queries against your SAP system.