SAP Basis Transport management

Direkt zum Seiteninhalt
Transport management
Perform user comparison manually with transaction PFUD
SAP HANA has been one of the major topics in the SAP environment for the last few years. Many customers are currently faced with the question of whether or not to migrate your SAP system. In addition to the actual changeover itself, there are many other topics on which you should have already informed yourself in advance, as these influence the success of SAP HANA in your company. What do you already know about SAP HANA? I would like to encourage you to think about security in the following article. If you would like to learn about the architecture of HANA, I recommend a contribution from our colleagues at erlebe Software. SAP HANA Scenario But why are we even talking about HANA Security? Why is it so important to consider new security strategies with the new technology? With HANA it is possible to analyse data quickly. BW scenarios primarily benefit from the in-memory database (IMDB) used, as speed advantages in data access are particularly positive. Compared to a classic ERP / R3 scenario, the normal DB is replaced by HANA. The desired speed advantages result. However, migration is expected to be required for the changeover. This is caused by customer-specific developments in the system. HANA is not a further development of SAP ERP, HANA is the next stage of an ERP system. It is well known that an ERP system contains the capital of the companies. Therefore a new HANA system like all other ERP systems is also interesting for attackers. On the one hand, such a system contains the critical business data that are available for espionage. In addition, most business processes are mapped in such a system and offer an attack surface for sabotage. In addition, users do not initially know the new technology well. This also applies to administrators in the area of a new technology. Attackers quickly gain a dangerous leap of knowledge over these user groups. SAP HANA has a lot of new features, although many existing ones are used by SAP ERP, so there is a risk here.

A partner agreement must be entered into for each supplier in the transaction WE20. Such an agreement shall determine how the electronic data are processed. Select the vendor partner type LI and create a new partner agreement. In this example, a new partner agreement is created for IDES AG as a supplier. Enter the vendor's partner number in the appropriate input field and select LI as the vendor's partner type. The next step is to define the output parameters. These specify how the outgoing data should be processed. The message type defines what kind of messages should be processed. The Output Options tab specifies the port to send the message to and the IDoc type. The IDoc base type ORDERS05 matches the ORDERS message. The Message Control tab defines which application should generate a message. In this case a message should be generated when a new order is created. If an order is placed for a product of IDES AG in the transaction ME21N, this order will be automatically sent in electronic form.

SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page: www.sap-corner.de.
2D/3D printers (e.g. Zebra)
There is no way around containers, and even SAP will soon have to reorient itself here and allow the NetWeaver stack to be run in containers. There are many indications that Kubernetes will win the battle for supremacy among container management tools. SAP has also already invested in Gardener and is also intensifying its partnerships with IBM and Red Hat Openshift.

Although you always make sure that authorization roles are generated when administering them, it happens again and again that there are red lights in the user assignment in the production systems. Have you considered user matching?

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

As each project and department passes, the employee repeatedly needs new permissions to meet the requirements.

To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.


In addition to the interfaces between system elements, Basis includes a development environment for R/3 applications, a data directory, and user and system administration and monitoring tools.
Zurück zum Seiteninhalt