SAP Basis Aufbau der SAP Basis - SAP Basis

Direkt zum Seiteninhalt
Aufbau der SAP Basis
The basics of Basis Administration
In the last few years, I have been asked time and again what SAP Basis is and what we SAP Basis administrators do in our daily work. With this blog post I would like to provide a little insight into exactly this area of work.

In order to meet the growing integration and coordination between internal IT departments and external service providers and suppliers, it is necessary to include a company-wide interface department in the IT organisation. The SAP basis can assume the coordination role and interface function in the environment of SAP products and technologies.
Customizing of the notifications according to customer requirements
Own development testing is very common in the quality system. Therefore, the customising/workbench developments must be transported to the appropriate system. It is highly recommended to use the order type "Transport of copies". This post explains why you should use this type of order and what you need to consider. Transporting copies - Why? All objects on the original transport order remain locked. Only the copies of the objects are transported to the next SAP system. If something goes wrong during transport, objects can easily be recollected or added. In addition, when copies are transported to the test system, no import is created in the production system. The import queue remains clean and clear. The problem with overtaking transports is eliminated. Transporting Copies - Creation To create a transport of copies, call the Transport Organiser through the transaction SE01. Check the Order Type "Transfers of Copies" and click View Create a new order (using the Document icon or F6 key). Then select the order type "Transport of copies". Then define a description and the destination system of the transport. Transport of copies - Add objects The transport order of the type "Transports of copies" was created. Now we want to add the objects of the original to be transported. Unfortunately, not all objects of an order can be copied directly. Therefore, it is important to take the objects task by task. A transport order can contain multiple tasks. Press CTRL+Y to highlight the task ID and then copy it by CTRL+C. Right-click on your order of the type "Transport of Copies" and select the Include objects option. Select the object list of an order and copy in the ID of the task that contains the objects to be transported. Confirm your input. All objects of the order are transferred to the transport of copies. You can then transport the objects to the test system using the normal transport procedure.

SAP's client concept enables a SAP system to be split into several logical sub-systems - clients. These subsystems can be used independently and in isolation as separate systems. But how should non-client transactions be treated? How can you prevent one client from accessing the other and why should you want to prevent that? In this blog post, I will answer these questions and discuss some negative examples. Why is it important to consider independent transactions separately? Imagine that every one of your employees is allowed to create or change a client in the production system, or worse, both. Creating and modifying a client in the production system is authorised and documented - you wonder what could possibly go wrong? The risk in this case is a loss of integrity of system and data, loss of confidentiality: With each new client, Superuser SAP* lives up to its comprehensive, cross-client rights and the assigned standard password.

Tools such as "Shortcut for SAP Systems" complement missing functions in the SAP basis area.

These cloud resources are integrated with existing on-premises resources and deployments on Amazon Web Services, Microsoft Azure and Google Cloud Platform.

When I upload it to Facebook, I made a copy of it and I can upload it to Instagram, for example.
SAP BASIS
Zurück zum Seiteninhalt