OUTSOURCING NON-SAP PRODUCT MANAGEMENT
SAP BASIS AND DATABASE SERVICE
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 SAP basis requires a separation layer to upstream and downstream IT departments, which is clearly defined. In the direction of the infrastructure, for example, this can be the upper edge of the operating system. This distinction must also be drawn in the direction of application development. Here there are various services offered today by the SAP basis, which are more closely related to application, such as control of background processing, transport or also the automation of certain activities. In principle, it is necessary to examine which tasks can continue to be carried out in the SAP basis due to the requirements and which can be given in expert units.
Database management, database export and database import
In the SAP NetWeaver BI Authorization Concept lesson, the training participant is familiarized with the authorization functions of the SAP Business Information Warehouse. The differences between the authorization concept for ERP systems and the authorization concept for NetWeaver BI are taught.
Reachable at any time: Your competent contact person is available at all times. If you operate SAP Basis Support in-house, personnel bottlenecks may occur. If your SAP employees are absent due to illness or vacation, there may be no equivalent replacement available.
"Shortcut for SAP Systems" makes it easier and quicker to complete a number of SAP basis tasks.
The marketing mix model is suitable for creating a marketing concept.
Some useful tips about SAP basis can be found on www.sap-corner.de.
They are then re-created with a continuous numbering in order to distinguish them later.