SAP Basis Performance tuning - SAP Corner

Direkt zum Seiteninhalt
Performance tuning
Support of SAP modules
The database layer is used to store all company data and consists of the database management system (DBMS) and the data itself. In each NetWeaver system there is a database server on which the SAP database is located. It provides all other applications with the necessary data. The data is not only data tables, but also applications, system control tables and user data. All basic components ensure that the user has fast and reliable access to this data.

Because hybrid landscapes are seen as the operating model of the future, it is necessary to develop monitoring strategies for this. What is important is an end-to-end view based on the process and not just an individual view of the systems, services or components involved. This supports the requirement of a company-wide interface function of the SAP basis.
Maintenance of profiles and operation modes
The entry screen gives a brief overview of the status of the last queued. In case of incomplete support packages, the last (aborted) step of the SPAM will be displayed. System: Check the correct function of the transport tools using Tool Transport Tool. Make sure there is enough space (the size of the OCS files multiplied by 2) in the transport directory (see the R/3 profile parameter DIR_TRANS with the AL11 transaction or the SE38 transaction and the report RSPARAM). Make sure that there is enough space, especially in the subdirectories trans/EPS/in and trans/data. Use the latest SPAM update. Verify that the SPAM update offered in the SAPNet - R/3 frontend or the SAPNet - Web Frontend is newer than the one available in your system. You can see the version of the SPAM update available in your system in the title bar of the SPAM image. We recommend that you always run the latest SPAM update first [page 14] to avoid problems when playing. The insertion of a SPAM update is analogous to the insertion of support packages. There must be no incomplete support packages in your system. To do this, under Folder in the SPAM, select Aborted Support. Packages and select View. Support packages should not be displayed. The status light should be green. If not, view the detailed status and log information for all support packages in the system. Select Jump Status or Jump Log. Load Activities Support Package [page 15] Define Queue [page 17] Insert Queue [page 20] If necessary: Sync Modifications [Page 22] Verify Protocols [Page 23] Confirm Queue [Page 24].

The result table USERTCODE contains the transaction codes of the SAP users. Afterwards you simply have to output the complete list via "Object > Output complete list". Then save the list via "System > List > Save > Local file". The column Account contains the SAP user. This way you can see the used transactions grouped by SAP user.

"Shortcut for SAP Systems" simplifies tasks in the area of the SAP basis and complements missing functions of the standard.

By using a code scanner, it is now possible for every developer to scan for complex security patterns during the extended check of his program, which tell him whether he has built vulnerabilities into his program.

The website www.sap-corner.de offers many useful information about SAP basis.


It must be specified which users can get special rights.
SAP Corner
Zurück zum Seiteninhalt