SAP Basis Troubleshooting and fault elimination - NW Admin

Direkt zum Seiteninhalt
Troubleshooting and fault elimination
WE21 Ports in IDoc processing
If table logging is active in your system, you can specify which tables are to be logged in transaction SE13. For an active logging it is necessary to set the flag "Log data changes".

Reachable at any time: Your competent contact person is available at all times. If you operate SAP Basis Support in your own company, personnel bottlenecks may occur. If your SAP employees are absent due to illness or vacation, there may be no equivalent replacement available.
Beta test: secinfo and reginfo Generator for SAP RFC Gateway
The digitization of businesses and the emergence of new technologies mean that admins have to adapt to constantly changing conditions. Currently, the following trends (which are becoming more and more evident in the market) can be mentioned:

Understanding the structure and functioning of the system is especially important for IT administration. It is not for nothing that "SAP Basis Administrator" is a separate professional field. On the page www.sap-corner.de you will find useful information on this topic.


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 "Shortcut for SAP Systems" tool is ideal for doing many tasks in the SAP basis more easily and quickly.

If the number of jobs and the complexity increases, an automatic job control is a good choice.

So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.

It would also be possible to designate contact points (contact points) for upstream and downstream IT departments and external service providers and suppliers.
NW BASIS
Zurück zum Seiteninhalt