Scheduling background jobs, job monitoring, job deletion, etc
Workflow
Although you always make sure that authorization roles are generated when administering them, it happens again and again that there are red lights in the user assignment in the production systems. Have you considered user matching?
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.
Support of SAP modules
The establishment of Software-Defined Data Centres or IaaS are the key to further flexibility and standardisation of SAP technology infrastructure. The concept of a Software-Defined Data Centre is to create an abstraction layer over the individual virtualised components, such as servers, networks or storage, that controls, controls, provisioning, and automates the entire infrastructure.
Better technologies have expanded the role of SAP Basis Administrators, paralleling the IT industry as a whole. It's no longer enough to keep the system running and performing well. An SAP HANA Basis Administrator also plays a role in cost control, IT strategy and even business policy.
With "Shortcut for SAP Systems" a tool is available that greatly facilitates some tasks in the SAP basis.
SAP HANA base administrators can master the database in a way that wasn't possible back then.
Manual identification of critical SAP permissions is difficult overall.