SAP Basis Practitioners for practitioners - SAP Stuff

Direkt zum Seiteninhalt
Practitioners for practitioners
Root cause analysis
The SAP basis requires a separation layer to upstream and downstream IT departments, which is clearly defined. In the direction of the infrastructure, for example, this can be the upper edge of the operating system. This distinction must also be drawn in the direction of application development. Here there are various services offered today by the SAP basis, which are more closely related to application, such as control of background processing, transport or also the automation of certain activities. In principle, it is necessary to examine which tasks can continue to be carried out in the SAP basis due to the requirements and which can be given in expert units.

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.
SAP BASIS OPERATIONS
When I began my career administering SAP ERP on Oracle in the early 1990s, running a database required far more knowledge. An Oracle administration expert with a decade of experience understood perhaps only about 5% of what the database required.

Tools such as "Shortcut for SAP Systems" complement missing functions in the SAP basis area.


If you want to get more information about SAP basis, visit the website "www.sap-corner.de".

The presentation layer represents the interface to the user (SAP GUI).

SAP Stuff
Zurück zum Seiteninhalt