Preparation of documentation
ASSESSMENT OF EXISTING CUSTOMER-SPECIFIC SOLUTIONS
Different events can be used to change to the new or changed role concept. Among other things, the introduction of new technologies can be used to establish, for example, the characteristics of the SME or technology architect. But also fluctuation or new hires are suitable for the conversion and establishment of the new roles. In principle, it is recommended that the new rollers be introduced and implemented successively parallel to the existing operating model.
Transporting transport orders from one system line to another or importing third-party transport orders into the SAP system is also an occasional task for an SAP basis administrator. As in my last blog post on system modifiability, I would like to offer you a way to quickly present this topic. So you will find a step-by-step guide which you can follow if you have already understood the content of the topic, but only the steps need to be taken. What are the requirements? Transport orders include two files, titled "data" and "cofiles". These files consist of a six-character alphanumeric combination and a file extension, which often represents the system from which the files were exported. The first character is always a K (the cofiles file) or an R (the data file). For our example we call the files K12345_DEV and R12345_DEV. These files are of course needed for an import into your own SAP system. Furthermore, you need access to the file system or the SAP directories, as they have to insert the above files there manually. In addition, the transaction STMS is required in the SAP system because it attaches the transport orders to the import queue. Now, if you have all of this available, we can start with the import: What is the procedure? Operating System Level Preparation. The first step is to copy the files to the transport directory of the SAP system. This is usually below /usr/sap/trans, but can be changed individually depending on the system. If you want to make sure that you are working in the correct directory, you can look in the transaction AL11 to see which directory is specified under "DIR_TRANS". This is the right directory to work on. Here the existing files are copied into it, namely the cofiles file (K12345_DEV) in the cofiles folder (/usr/sap/trans/cofiles) and the data file (R12345_DEV) in the data folder (/usr/sap/trans/data). Note: In this case, especially for companies with multiple systems on multiple servers, the access permissions and the file owner need to be changed so that the import in the target system does not cause problems.
SAP GUI Patches / Hotfixes
This step prompts you to customise your modifications to Repository objects by calling the transaction SPAU. EPILOGUE In this step the insertion is completed. Among other things, it is checked that the queue has been fully processed. SPAM: Troubleshooting The SAP Patch Manager performs several steps during the recording. If errors occur, SPAM will interrupt the playback to ensure consistency of the recording. After fixing the error, you can resume playback. When you cancel, a dialogue box appears with the information on which step and why the editing failed. This dialogue box is also available when you select Jump Status and then Queue, Support Package or SPAM Update (View Support Package Status (page 29)). Depending on the processing step in which the error occurred, the dialogue box will provide you with additional specific assistance to correct the error. You may also need to reset the status of a Support Package [page 36]. If you are having problems downloading Support Packages from the SAPNet - R/3 frontend, please see Note 34376. If you are having problems working with SPAM, read the note 17381This note gives you an overview of known problems and their solutions. For a list of the most important information about Online Correction Support (OCS), see Note 97620, which is updated regularly. If you are unable to resolve your issue with the information provided or with the following information, then record a problem message in the SAPNet - R/3 frontend with the information from the error dialogue box and send it to the BC-UPG-OCS topic group. Note 97660 when capturing the problem message. See also: Generation Error [Page 30].
If this parameter is exceeded by a process, the query is cancelled before it could be executed. Both parameters are limited by the parameter abap/heap_area_total. Of course, there are several other storage parameters that would exceed the scope of this article. You can read their function in the SAP documentation.
Tools such as "Shortcut for SAP Systems" are extremely useful in basic administration.
This is usually divided into four pillars - the four Ps.
To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.
Site Reliability Engineering(SRE) is the equivalent of SAP Basis in the Google world.