SAP Basis Troubleshoot errors - SAP Corner

Direkt zum Seiteninhalt
Troubleshoot errors
SAP ICM
The marketing mix model is suitable for creating a marketing concept. This is usually divided into four pillars - the four Ps. These are Product, Price, Place and Promotion. In the case of services, this is often accompanied by the aspect of personnel policy. Although the marketing mix model is aimed at the external distribution of products and services, aspects of it can also be applied to an internal marketing of the SAP basis. For the design of the respective areas of the marketing mix, it is recommended to use a guide to develop a marketing concept. STEP 1: DEFINITION OF PERFORMANCE This step deals with the description of the services to be offered. Similarly, this step provides a categorisation of the type of service. These include, for example, the levels of secondary or primary service. With respect to the SAP basis, this step is concerned with product portfolio analysis and the creation of IT products and a product catalogue. STEP 2: OWN RESOURCES Subsequently, a determination of one's resources takes place. That is, it identifies the resources that are available and that can be used and the resources that need to be developed. Resources are people, objects, systems, knowledge, and funds. For the SAP basis, this step is an inventory. STEP 3: DETERMINATION OF THE OBJECTIVES The mission and vision of service providers will be determined in the framework of the setting of the objectives. It also sets measurable targets for the next three years.

A secure SAP system does not only include a good role concept. It is also necessary to check whether a user should (still) have a specific role. Regular verification of role assignment is called recertification. In this blog post, I'd like to introduce you to the need for recertifications and our own tool, EasyReCert. The need for recertification - scenarios: Example 1: The "apprentice problem" Imagine the following scenario: A new employee (e.g. apprenticeship or trainee) will go through various departments as part of his or her training and will work on various projects. Of course, an SAP User will be made available to your employee right at the beginning, which is equipped with appropriate roles. As each project and department passes, the employee repeatedly needs new permissions to meet the requirements. After the employee has successfully completed his or her induction and is now in a permanent position, he or she still has permissions that are not necessary to perform his or her duties. This violates the principle of "last privilede" and represents a potential security risk for your company. Example 2: The change of department The change of department is one scenario that probably occurs in every company. If a change of department does not automatically involve a complete reallocation of roles and the employee simply takes his old permissions with him, critical combinations of permissions can occur very quickly. For example, an employee who has permissions in accounts payable and accounts receivable violates the SoD ("Segregation of Duties") principle and poses a potential security risk to your company. Recertification as part of a revision: The two examples above show that a regular review of role allocation identifies potential security risks for your business and can be addressed.
Hardware Sizing
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 Hosting should not be thought of as an off-the-peg suit, but as a made-to-measure suit. For mid-sized companies in particular, it is crucial to first identify corporate goals, technical conditions of the IT architecture and individual requirements. During this planning phase, added value and potential savings can also be identified.

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

SAP HANA base administrators can master the database in a way that wasn't possible back then.

Understanding the structure and functioning of the system is especially important for IT administration. It is not for nothing that "SAP Basis Administrator" is a separate professional field. On the page www.sap-corner.de you will find useful information on this topic.


The support packages that are no longer part of the queue are still visible in the list and can be selected again.
SAP Corner
Zurück zum Seiteninhalt