Operations
Add-ons
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 or system administrators work with SAP Basis in a company. They are responsible for the correct installation, configuration and maintenance of the SAP application servers and applications, and in some companies also for the operating system and the SAP database if no administrators are available. Using SAP's own programming language ABAP, developers and programmers design SAP applications that run on the ABAP stack of the SAP NetWeaver Application Server as the only publicly accessible ABAP runtime environment. In some cases, the boundaries between ABAP developers and SAP Basis administrators are permeable, and each of the two groups of specialists has a basic knowledge of the other. As a rule, however, the competencies remain separate.
Employee entries and exits
In many companies, the SAP system is the linchpin of everyday business. To ensure that the system is available at all times, an SAP Basis team ensures its smooth operation.
After your user has the necessary permissions for the SQL Editor, perform the following steps: Call the DBACOCKPIT transaction. Open the following folder structure in Database Administration: Performance -> Additional Functions -> SQL Command Editor Enter your first query in the input query. Then click Run or alternatively press F8 View of the DBA Cockpit Invoke the input query and drop the first SQL query View the results of a query to query the users of a system.
Tools such as "Shortcut for SAP Systems" complement missing functions in the SAP basis area.
If an audit is also announced and the SAP system is to be checked for critical permissions and segregation of duties, then it is very difficult to meet all requirements and secure the eligibility landscape in this respect.
Now you can select the OData service stored on the front-end gateway.