System copy, system update, etc
DRIVE TASK AUTOMATION
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.
A Conflict Resolution Transport (CRT) is used only for add-ons, such as IS-IS or IS-OIL. It is used to eliminate conflicts that may arise between the different support packages and an add-on. Note that a CRT that applies to an add-on release also resolves all conflicts with previous releases of that add-on. In addition, a CRT may include other corrections for the corresponding add-on. A CRT can therefore always be a special add-on support package. Settings for SPAM With Additional Settings, you can access a dialogue box where you can specify general settings for the SAP Patch Manager (SPAM). These settings affect the behaviour of downloading and loading support packages of the different types equally. SPAM updates are an exception; certain settings are specified for these. You can toggle the following properties on and off: Transmission Monitor If you enable the Transmission Monitor, you can monitor the download of the support packages from the SAPNet - R/3 frontend with a graphical monitor. Otherwise, you will only get a progress bar. Scenario Choosing the scenario determines which actions should be performed while the Support Packages are being played in. The default scenario is used to fully deploy support packages; All steps are performed. The test scenario allows you to determine whether a modification match is required or whether conflicts occur that should be resolved before the support packages are loaded. The test scenario does not import data and objects into your SAP system. There is no test scenario for SPAM updates. The choice is ignored when a SPAM update is introduced. Rebuild data files You can specify whether the data files from the EPS packages will be reunzipped each time you try to play. In principle, this is the case.
Quick check of your SAP security settings with the Xiting Authorizations Management Suite (XAMS)
A role concept according to best practice protects you from potential attacks within your SAP landscape. However, to protect your system from unauthorized access via the network, a correct configuration of the SAP gateway is required. It enables the use of external programs via interfaces or the call of ABAP programs and serves as a technical component of the application server, which manages the communication of all RFC-based functions.
Within SAP R/3 Enterprise, the SAP Basis Plug-In is a prerequisite for you to use the SAP R/3 Plug-In. SAP Basis Plug-In and SAP R/3 Plug-In must always have the same release level, for example PI 2004.1 and PI Basis 2004.1. If you plan to upgrade SAP R/3 Plug-In within SAP R/3 Enterprise, you must also upgrade SAP Basis Plug-In. As of SAP Basis Plug-In 2005.1, the release levels of the two plug-ins no longer need to correspond. However, the SAP R/3 Plug-In Support Package for PI 2004.1, which contains new interfaces, still requires a specific SAP Basis Plug-In. For example, SAP R/3 Plug-In Support Package 10 for SAP Plug-In 2004.1 requires SAP Basis Plug-In 2005.1.
"Shortcut for SAP Systems" makes it easier and quicker to complete a number of SAP basis tasks.
By using an IdMSsystem, manual processes can be replaced by automated workflows that are mapped and administered centrally.
One of the possible causes of error is that
adm does not have write permissions for the /usr/sap/trans/cofiles (UNIX) directory.