Define Queue
Incident Management
To use all the features of the SAP Patch Manager, you need the following permissions: S_TRANSPRT S_CTS_ADMIN Both are in the S_A.SYSTEM permission profile. If you log in to the Mandant 000 and your user base contains the appropriate permission profile, then you can use all the features of the SAP Patch Manager. When you log in to another client or without the appropriate user profile, you can only use the display functions. Map this permission profile to the system administrator only. Only the system administrator should have permission to perform the following actions: Support Packages Download Support Packages Play Support Packages Confirm Successfully Recorded Support Packages Reset Support Package Status Support Packages eliminate errors in the SAP system or make necessary adjustments due to legal changes, for example. The affected objects will be replaced in your system. Each Support Package is valid for one release level (but for all databases and operating systems) and requires a precisely defined number of predecessors. The upgrade from the following release or revision level contains all support packages from the previous booths that were available until the upgrade was delivered. SPAM ensures that support packages are only played in the order specified. To avoid problems, play all support packages as they are deployed. This allows you to keep your system up to date.
In addition to acute project support, our SAP Basis team can also serve as co-managers. With co-management, your SAP administrator and an abilis employee share the day-to-day tasks.
Reset Support Package Status
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.
Due to the technology diversity, including in the SAP product portfolio, the support by a single silo unit SAP basis is almost impossible. Likewise, there are many activities that are located for historical reasons in the SAP basis and in parallel in the non-SAP area. In this respect, the separation between SAP and Non-SAP must be examined and, if possible, eliminated by standardisation, integration and centralisation. For example, the issue of output management can be set up in a team that has knowledge in the SAP printing area as well as in the non-SAP printing area and has contact points in the SAP basis. From the SAP basis, tools must be made available to the non-SAP areas to support them in their work in the SAP environment.
Tools such as "Shortcut for SAP Systems" complement missing functions in the SAP basis area.
You will see the list of installed software components (e.g. SAP_BASIS, SAP_HR, SAP_BW, Add-On).
SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page: www.sap-corner.de.
These cover the rules formulated in the concept and are suitable for measuring the extent to which the reality in the system meets the requirements formulated in the concept.