System copy
STMS_IMPORT Import queue
The core of the three-layer model is the application layer. This consists of one or more application servers and a message server. Companies use the application server to provide services for the operation of applications in SAP. The message server serves as an "intermediary" between the applications and services, for example, by controlling communication between the individual application servers and determining the load on the application servers. Furthermore, the data is prepared for the user in the application view so that the user can call up the data visually in the presentation layer. At the same time, the user data is forwarded to the database.
SAP Basis Operation is responsible for ensuring the technical functionality of an SAP system. It includes all the technical components mentioned above. These are used to perform the following tasks.
System copy, system update, etc
IMPORT_PROPER In this step, the repository and table entries are recorded. There are the following reasons that may lead to the termination of this step: TP_INTERFACE_FAILURE: Unable to call tp interface. TP_FAILURE: The tp programme could not be run. For more information, see the SLOG or ALOG log file. TP_STEP_FAILURE: A tp-Step could not be performed successfully. The cause of the error can be found in the appropriate protocol, for example in the import or generation protocol. If the generation (tp-Step G) is aborted, you can either fix the errors immediately or after the commit is completed. In the latter case, you must do the following: To ignore the generation errors, select Additions Ignore Gen Error. Continue the playback. Buffer synchronisation problems can also cause generation errors. For more information, see Note 40584.
SPAM/SAINT updates (SPAM update) provide updates and improvements to SAP Patch Manager and SAP Add-On Installation Tool. There is always one SPAM update per review that will be updated over time. The version can be found in the short description, e.g.: SPAM/SAINT update - version 4.6A/0001 A SPAM update always comes first in the list of support packages in the SAPNet - R/3 frontend, i.e. before the other support packages. We recommend that you always install the latest version of a SPAM update before installing Support Packages. Prerequisites You can successfully commit a SPAM update only if there are no broken support packages in the system. If there are cancelled support packages, a dialogue box will alert you. You have two options: You will first complete the queue and then the SPAM update. You reset the status of the queue, play the SPAM update first and then the queue. You can reset the status of the Queue by using the Add Status Reset Queue. Note that your system is inconsistent when you reset the queue after objects have already been imported (for example, after an error in the DDIC_IMPORT step and following). Therefore, you should only reset the queue if DDIC_IMPORT was cancelled before the step. For more information, see Steps of the SPAM [page 26]. Note that starting with SPAM/SAINT version 11, it is no longer possible to reset the queue after the DDIC_IMPORT step and following. How to Check if the SPAM update you are offering is newer than the one you are receiving. The current SPAM version appears in the title bar of the SPAM window. To play the latest SPAM update, select Support Package Insert SPAMUpdate. SPAM updates are automatically confirmed after successful insertion. Load Support Package Usage Before you can insert Support Packages, you must first load the appropriate Support Packages.
The "Shortcut for SAP Systems" tool is ideal for doing many tasks in the SAP basis more easily and quickly.
BI Addon Patch A new service package and patch may need to be installed.
If you have unsigned SAP hints, there is a risk that the notice has been changed unnoticed and malicious code will be added to your SAP system when you install the notice.