SAP Basis ORGANIZATION - SAP Corner

Direkt zum Seiteninhalt
ORGANIZATION
Daily Check Solution
In the case of distributed or local SAP systems, it can also be helpful if departments or decentralized IT units can schedule their own jobs themselves. It is important that the associated approval processes can also be mapped and easily tracked. This brings convenience, flexibility and a degree of freedom without neglecting operational security. The integration of the business departments can relieve the IT administrator and turn background processing into an end-to-end process integrated into the organization.

The logging of data changes in tables using transports should also be active. For this, the "RECCLIENT" parameter in your transport management system (Transakation STMS) must be set to "ALL" at all system levels.
SAP Business Application Programming Interface (BAPI)
The results of the tests can be documented so that the development can be considered over a period of time. This way, you will be aware of the revision and of the relevant issues before the examination.

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.

"Shortcut for SAP Systems" makes many tasks in the area of the SAP basis much easier.

Support packages intended for another release or an uninstalled add-on will not appear in the queue, even if they are loaded into your SAP system.

SAP Basis refers to the administration of SAP system that includes activities like installation and configuration, load balancing, and performance of SAP applications running on Java stack and SAP ABAP. This includes the maintenance of different services related to database, operating system, application and web servers in SAP system landscape and stopping and starting the system. Here you can find some useful information about SAP Basis: www.sap-corner.de.


SPAM: Troubleshooting The SAP Patch Manager performs several steps during the recording.
SAP Corner
Zurück zum Seiteninhalt