Virtualization of your SAP system landscape
Optimization of the SAP infrastructure
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 Basis operations manage the IT underlying the SAP system. In addition, the operation ensures the maintenance and availability of business processes. Various tools can be used for this purpose, which take over the maintenance, servicing, configuration and monitoring of the SAP system. Basis operation is the prerequisite for ensuring that the SAP system is fully operational and covers the business processes well.
SAP Business Application Programming Interface (BAPI) is an interface that allows developers of customer and third-party code to access ... View full definition
In every company with an SAP system, there is someone who is responsible for the SAP Basis. This person ensures the trouble-free operation of the SAP system. He or she accompanies maintenance work and intervenes in special situations, such as poor performance. Even for companies that hand over the operation of Basis to an external service provider, there are often still tasks from the user and authorization management environment at this point.
Basis is a set of programs and tools that interface with databases, operating systems, communication protocols, and business applications (such as FI, CO, MM, etc). The full form of BASIS is "Business Application Software Integrated Solution".
"Shortcut for SAP Systems" makes it easier and quicker to complete a number of SAP basis tasks.
In the transaction RZ11, however, it is possible to view information about individual parameters, provided that you know their name.
On www.sap-corner.de you will also find useful information about SAP basis.
The decision to outsource a task or service should be taken not only in terms of cost, but also by assessing the competitive differentiation and strategic importance.