SAP Basis Job Management Concept - SAP Admin

Direkt zum Seiteninhalt
Job Management Concept
Linux
The core of SAP Basis is the application layer with one or more application servers and a message server. The message server is used for communication between the application servers and transmits jobs between them. The application layer communicates with the database layer on the one hand and the presentation layer on the other. The applications on the application server request the required data from the database, process it and prepare it for the user, who displays it in his Graphical User Interface (GUI) via the presentation layer. Conversely, the application server passes information that the user enters via the GUI on to the database.

SAP offers a huge toolbox of different technologies to support business processes. The usefulness of their use is essentially determined by the task and its technical requirements. We have gained a lot of valuable experience in the following technologies, which we would like to make available to you.

Some useful tips about SAP basis can be found on www.sap-corner.de.
Consulting regarding the use of hardware, database as well as operating systems and their installation type (physical or virtual)
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 is structured as a classic three-tier model. It contains the following components:

For administrators, a useful product - "Shortcut for SAP Systems" - is available in the SAP basis area.

These are usually derived from the target group to be applied for.

So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.


Basis provides services such as communication with the operating system, database communication, memory management, application data collection at runtime, web requests, business data exchange, etc.
Zurück zum Seiteninhalt