SAP Basis Configuration & operation of the SAP Solution Manager - SAP Stuff

Direkt zum Seiteninhalt
Configuration & operation of the SAP Solution Manager
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.

The Advanced Memory thus contains mainly user contexts of different work processes, if these cannot be loaded completely into the roll area. Since the storage area is accessible for all work processes, the work processes can also access external user contexts that lie here. In addition, the Advanced Memory contains a global area where data can be stored independently of user contexts. The extended memory size is determined by the values of em/initial_size_MB and em/global_area_MB. The first parameter determines the size of the storage area in which user contexts can be stored, and the second determines the size of the global area. Parameters for Private Storage Last but not least, there is the private storage, which is only used when the user context of a work process has used up all the other storage areas available to it, i.e. its share of the extended memory and its rolling area. In this case, the workprocess goes into PRIV mode. A workprocess in private mode is bound to its current user context and will not become free for other tasks until the current request is completed. If it has used up all the private memory allocated to it, the workprocess will then be restarted and the memory released. This behaviour is controlled with the abap/heaplimit parameter. At times, the user context may exceed the value of abap/heaplimit. The parameters abap/heap_area_total, abap/heap_area_dia and abap/heap_area_nondia define an upper limit for private storage. The abap/heap_area_total parameter defines how much private storage all workprocesses can use in total. The parameters abap/heap_area_dia and abap/heap_area_nondia, on the other hand, determine how much private storage a single (non-)dialogue workprocess can use.
Request now
If all tasks considered to be an interface theme are supported by the SAPBasis, this means a very wide range of tasks. Here it is necessary not to overwhelm the own employees within the SAP basis and to keep the complexity of different topics and technologies manageable per capita. Therefore, a corresponding growth is associated with this interface task. This recommendation is general and does not apply only to the SAP basis.

Setting up Client certificate for access to SAP ONE Support Launchpad This week it was again: The Client certificate for SAP Support has expired. Who wonders how I can set up the client certificate in the browser? Here is the instructions against password-pop-up terror. Short and painless. Launchpad Call Personalisation SAP Passport Add Kachel to the Home Group View Kachel in My Home Create SAP Passport Certificate (with S-Users password) Download Certificate Open and Import Certificate Close Browser Then. If you (like me) have been looking for this feature for a long time, I'm glad to have a short ping in the comment.

Use "Shortcut for SAP Systems" to accomplish many tasks in the SAP basis more easily and quickly.

The ITIL set of rules describes the processes, the organizational structure and the tools required for IT infrastructure.

On you will also find useful information about SAP basis.

Even for companies that hand over operation of the SAP Basis to an external service provider, there are often tasks from the user and authorization management environment at this point.
SAP Stuff
Zurück zum Seiteninhalt