SAP Basis Continuous improvement of system availability and performance - SAP Basis

Direkt zum Seiteninhalt
Continuous improvement of system availability and performance
Attendance of the course "SAP HANA - Introduction
We take over the complete maintenance management for you and ensure that your SAP installation is always up to date. As a certified SAP Gold Partner and PCoE (Partner Center of Expertise), we can provide you with all the SAP licenses you need. We advise you on the possible licensing models and only provide you with the licenses you actually need.

This advanced SAP administration training course provides confidence in in-depth administration tasks on your SAP system. For example, SAP administration with WebAS with ABAP and Java, system configuration and system updates, importing patches and corrections, and updating users and authorizations. Furthermore, the program includes the setup of printers, knowledge of system security and system monitoring as well as transport functions. Not to forget the help system and data backup in your SAP systems.
If regulations for the standardisation of SAP systems or tasks and procedures are in place, they must also be consistently complied with and their compliance must also be verified. In case of non-compliance, for example due to project influences or technological problems, the exception must be returned to the standard in a timely manner. Resources must be made available for this.

To influence the ABAP/Dynro generation, select Additions in the entry screen of the SPAM. Function Menu Path Turn Generation on or off Settings Ignore generation errors during the commit. Ignore error in SPAM steps If an error is detected in one step, the transaction SPAM stops processing until the error is resolved. You can always check with Status to see in which step and for what reason the abortion took place. Types of errors There are the following types of error messages: Security checks of the transaction SPAM A typical example is the OBJECTS_LOCKED_? step. The SPAM transaction interrupts processing when objects are still locked in jobs to be overwritten by the queue. Error messages of the programmes tp and R3trans The cause of error can always be found in the corresponding transport log. A typical example is the TEST_IMPORT step. This checks to see if there are unconfirmed repairs to objects overwritten by the queue. The affected objects are listed in the Testimport log. Incorrect setup of the Change and Transport System Common errors are the lack of appropriate rights to the files of the Change and Transport System or the use of old programme versions of tp or R3trans. Verify that the transport tools are working correctly with Transp Tool. Check Tool. A typical example is the DISASSEMBLE step. If adm does not have write permissions for the /usr/sap/trans/data (UNIX) directory, SPAM will cancel DISASSEMBLE with CANNOT_DISASSEMBLE_R_DATA_FILE. The transaction SPAM requires that the Change and Transport System [External] is set up correctly. For more information on known problems, see Notes 97630 and 97620.

Tools such as "Shortcut for SAP Systems" are extremely useful in basic administration.

The application servers provide the services for running SAP applications.

You reset the status of the queue, play the SPAM update first and then the queue.
Zurück zum Seiteninhalt