Performance tuning
The administration of SAP Basis
The Queue determines which support packages are inserted into your system in which order by the SAP Patch Manager. If the queue is not yet fully defined, you must define the queue from the available support packages. If the Queue is already fully defined, it is only displayed; they no longer have the ability to change the selection. However, you can delete the queue completely with Queue [page 37]. Note that your system is inconsistent when you delete the queue after objects have been imported (for example, after an error in the DDIC_IMPORT step and following). The deletion in these SPAM steps should only be used for troubleshooting and you should repeat the insertion of the support packages as soon as possible. The SPAM transaction ensures that only support packages that match your system are displayed in the queue. Support packages intended for another release or an uninstalled add-on will not appear in the queue, even if they are loaded into your SAP system. For more information, see Rules for the Queue [page 19]. You must define the queue before you insert support packages. Prerequisites You have loaded the appropriate support packages with the SPAM into your SAP system [page 15]. Procedure To define a queue, select View/Define SPAM on the entry screen of the transaction. The Select Component dialogue box appears. You will see the list of installed software components (e.g. SAP_BASIS, SAP_HR, SAP_BW, Add-On). Select the desired component. You see the available queue. This queue contains the support packages available for the selected component in your system, and any required Conflict Resolution Transports (CRT), as well as associated Add-On Support Packages. You can: If the queue you see matches your wishes, you can accept the queue with Queue confirm and leave this selection window.
This step prompts you to customise your modifications to Repository objects by calling the transaction SPAU. EPILOGUE In this step the insertion is completed. Among other things, it is checked that the queue has been fully processed. SPAM: Troubleshooting The SAP Patch Manager performs several steps during the recording. If errors occur, SPAM will interrupt the playback to ensure consistency of the recording. After fixing the error, you can resume playback. When you cancel, a dialogue box appears with the information on which step and why the editing failed. This dialogue box is also available when you select Jump Status and then Queue, Support Package or SPAM Update (View Support Package Status (page 29)). Depending on the processing step in which the error occurred, the dialogue box will provide you with additional specific assistance to correct the error. You may also need to reset the status of a Support Package [page 36]. If you are having problems downloading Support Packages from the SAPNet - R/3 frontend, please see Note 34376. If you are having problems working with SPAM, read the note 17381This note gives you an overview of known problems and their solutions. For a list of the most important information about Online Correction Support (OCS), see Note 97620, which is updated regularly. If you are unable to resolve your issue with the information provided or with the following information, then record a problem message in the SAPNet - R/3 frontend with the information from the error dialogue box and send it to the BC-UPG-OCS topic group. Note 97660 when capturing the problem message. See also: Generation Error [Page 30].
MaxDB
PROJECT HISTORIES: THE SAP basis OF TOMORROW An entry in the Forum Infrastructure and Operations within the DSAGNet drew attention to the problem of the SAP basis as described above. This led to a lively discussion, which attracted a lot of interest from the members of the DSAM. Building on the interest and need for action of the member companies, a project was initiated by the DSAG as well as by the SAP, which should deal with the future of the SAP basis. Several companies were invited to participate and their willingness to participate actively was questioned in a DSAG survey. The first project meeting took place within the framework of the DSAG Annual Congress in Bremen in 2015. As a result, regular events took place at the SAP office in Freiberg am Neckar and St Leon-Rot, with the participation of up to 15 companies. In the project "the SAP basis of Tomorrow", current questions of the companies as well as the question of the SAP basis of the future were discussed and worked out with regard to the IT landscape, processes and organisational structure. A master's thesis was initiated to document and prepare the results as well as to examine the topic in scientific terms in parallel with the project. This was made at the University of Applied Sciences Würzburg-Schweinfurt as part of the Master's programme in Information Systems with Prof. Dr. Karl Liebschnitel and submitted for evaluation at the end of March 2016.
Due to the variety of tasks and the high complexity, I find my job extremely exciting. There are very many constellations of SAP systems and databases. Each installation, migration and update brings new aspects and challenges. It is precisely these challenges that are important to me, so that I can continue to learn and develop professionally on a daily basis.
"Shortcut for SAP Systems" is a PC application that simplifies or even facilitates many activities in the SAP basis.
For example, SAP administration with WebAS with ABAP and Java, system configuration and system updates, importing patches and corrections, and updating users and authorizations.
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.
For more information, see Note 40584.