What is SAP Basis?
A positive aspect of standardisation and automation is the increase in the quality of tasks, since manual errors can be almost excluded. It also increases the speed at which certain tasks can be performed. This is accompanied by a reduction in the proportion of administrative activity and thus in the proportion of the operation of the system landscape.
A trick often used by administrators is to allow for time buffers before starting the next job. The buffer times are necessary because it is not possible to predict exactly how long a job will take to complete, since the duration depends on many incalculable parameters. Since it makes little sense to run backups and SAP jobs at the same time, these tasks are usually done one after the other rather than in parallel. In more complex environments, data backup durations, time buffers and job runtimes add up to such an extent that the time available is no longer sufficient to perform all activities within the available time corridor. Tools that work with status dependencies and then automatically start the next job when its predecessor job has been processed without errors can help here.
Solution: Performing a user comparison
Support Packages from SAPNet - Web Frontend or Collection CDs are available in a compressed format. Note that you must unpack the support packages before processing. Download the support packages from the SAPNet - Web Frontend or mount the appropriate CD. Log in with the following user: Operating system users UNIX
adm AS/400 OFR Windows NT adm Go to the following subdirectory in your system: Operating system UNIX and AS/400 usr/sap/trans/tmp Windows NT :\usr\sap\TRANS\TMP Unzip the archive containing the support packages with the following command: Operating system command UNIX CAR -xvf / / / _CAR AS/400 CAR '-xvf /QOPT/ / / _CAR' Windows NT CAR -xvf :\ \ CHIVE>.CAR Put the unpacked support packages in the EPS inbox of your transport directory: Operating system EPS-Inbox of the transport directory UNIX /usr/sap/trans/EPS/in AS/400 /usr/sap/trans/EPS/in Windows NT :\usr\sap\trans\EPS\in Now bring the support packages into your system with Support Package Upload. You will see a list of uploaded support packages that are now known with all their attributes in the SAP system and can be handled in the right way by the SAP Patch Manager. Select Back to return to the SPAM entry screen.
Due to the technology diversity, including in the SAP product portfolio, the support by a single silo unit SAP basis is almost impossible. Likewise, there are many activities that are located for historical reasons in the SAP basis and in parallel in the non-SAP area. In this respect, the separation between SAP and Non-SAP must be examined and, if possible, eliminated by standardisation, integration and centralisation. For example, the issue of output management can be set up in a team that has knowledge in the SAP printing area as well as in the non-SAP printing area and has contact points in the SAP basis. From the SAP basis, tools must be made available to the non-SAP areas to support them in their work in the SAP environment.
"Shortcut for SAP Systems" simplifies tasks in the area of the SAP basis and complements missing functions of the standard.
Do you know of any other solutions for improving ABAP code security or have you already gained experience with the products mentioned above? I look forward to your comments!
This means that certain tasks must be considered not only in the context of the SAP basis, but also in the overall context.