SAP Basis Very good IT knowledge - especially of SAP solutions - NW Admin

Direkt zum Seiteninhalt
Very good IT knowledge - especially of SAP solutions
A new SAP system is created...
SAP Basis administration is distinct from other roles such as ABAP developers and consultants who handle architecture. In many companies, the boundaries between administration and development are blurred. Admins may therefore also be involved in the planning and development of the system.

This is the heart of the SAP system. In the classic three-tier model, this would be the logic or control layer. One or more application servers host the necessary services for the various applications on this layer. These application servers provide all the services required by the SAP applications. In theory, a single server could fill this role. In practice, these services are in most cases distributed among several servers, each serving different applications.
Basis administration in the age of SAP HANA
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.

Some useful tips about SAP basis can be found on www.sap-corner.de.


SAP Basis is the foundation of every SAP system. On this page you can find out what is behind the term and what SAP Basis is responsible for in detail.

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

The infrastructure-related SAP basis in turn serves as the link between the application-orientated SAP basis and the infrastructure levels.

So much information... how can you keep it so that you can find it again when you need it? Scribble Papers is a "note box" that makes this very easy.

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.
NW BASIS
Zurück zum Seiteninhalt