Insert SPAM/SAINT Update
All topics are relevant, which may also be of interest to a customer. Ideally, you get a balanced communication structure in the communication triangle between marketing, the target group and your own employees. Internal communication is an important aspect for the SAP basis. It is primarily a matter of passing on or communicating your own services, IT products and positioning to your employees. STEP 10: PLANNING The planning provides a translation of the previously agreed definitions into concrete measures. A description of the measure shall be provided. The measures can now be scheduled and included in a cost overview. Above all, it is important to plan realistically and to consider dependencies. This step, too, is of great interest to the SAP basis and is necessary to translate the previously agreed specifications into a concrete marketing concept of the SAP basis.
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.
CHANGE OF PERCEPTION
Due to the variety of tasks and the high complexity, I find my job extremely exciting. There are very many constellations of SAP systems and databases. Each installation, migration and update brings new aspects and challenges. It is precisely these challenges that are important to me, so that I can continue to learn and develop professionally on a daily basis.
There are thus numerous interfaces between these fields of activity. As a result, the boundaries become blurred in some cases.
Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".
Typically, the following two SAP access permissions are enabled to protect print jobs: S_SPO_DEV (spooler device permissions) S_SPO_ACT (spooler actions).
Note that starting with SPAM/SAINT version 11, you cannot delete the queue after the DDIC_IMPORT step and following.