Installation Services in all common environments
Log in history of users using SAL
The SAP basis is often perceived as a brake within projects or when introducing new technologies. This is partly due to the late consultation of the SAP basis on the issues of technical feasibility as well as the integration of new technologies and applications into the existing system landscape. By implementing the recommendations, the SAP basis is repositioning itself in parts within the IT organisation. The SAP basis has a clearly defined self-understanding (inward-looking perception) as well as a clear positioning and a defined task area within the IT organisation (outward-facing perception), as shown in Figure 5. By integrating the SAP basis into the development of the IT strategy, the digitisation strategy and a clear communication with the CIO, the SAP basis has the opportunity to deal with technologies and topics at an early stage. As a result, the SAP basis is prepared for requests from business units or other IT departments and has the opportunity to approach them proactively. The SAP basis is supported by an IT service and IT product catalogue, which describes the scope of the SAP basis. For internal communication and communication with external service providers, as well as other suppliers, outsourcing partners or outsourcing partners and cloud service providers, there are up-to-date and meaningful documentation and process descriptions. For the control, measurement and monitoring of external partners, Service Level Agreements and meaningful key figures are also available.
Understanding the structure and functioning of the system is particularly important for IT administration. It is not for nothing that "SAP Basis Administrator" is a career field in its own right. Instead of data and application development, the focus here is on providing the software environment on which the company's tools are created. SAP Basis is therefore comparable to the server and platform infrastructure and its administration in companies - as distinct from application and web development.
SAP Administration II
The logging of data changes in tables using transports should also be active. For this, the "RECCLIENT" parameter in your transport management system (Transakation STMS) must be set to "ALL" at all system levels.
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.
Use "Shortcut for SAP Systems" to accomplish many tasks in the SAP basis more easily and quickly.
The unprotected system does not have any limitations on the external services that may register, and there are no rules for running programmes.
If you have organised this, call the transaction SE06 in the 000 client and click on the button "System Modification".