SAP Basis Migration of your ERP landscape to SAP on HANA or S/4HANA - SAP Basis

Direkt zum Seiteninhalt
Migration of your ERP landscape to SAP on HANA or S/4HANA
Troubleshooting and support
Maintaining the availability of critical business processes not only requires a high-quality infrastructure, but also places equally high demands on the management and operation of the underlying SAP NetWeaver and SAP HANA platforms due to their high complexity. These platforms are often referred to as SAP Basis.

By using a code scanner, it is now possible for every developer to scan for complex security patterns during the extended check of his program, which tell him whether he has built vulnerabilities into his program. These vulnerabilities are detected and can now be addressed in a workflow-driven process. Currently, there are two products that can support customers in the area of scanning their own SAP programs.
SAP Electronic Data Interchange
Another important example is the reading permission for TemSe objects. The temporary files are often forgotten, because it is often not considered that cached (strictly) sensitive data, which is intended for only one user (owner), can be viewed by another user without permission - and across clients. The examples mentioned show us how important it is to carefully assign permissions for client-independent transactions. Download Transaction tables The transactions that enable the examples above, including certain expressions of the associated permission objects and our recommendations for them, can be found in the file "Critical cross-client permissions" for download. Other client-independent transactions are located in the Cross Clients TCODES file. The criticality of these transactions should be assessed according to the context. I recommend always being careful and keeping these transactions in mind.

At best, for the time in which an emergency user is in service, a separate log of the activities undertaken is written, which can then be evaluated. In the following chapter I would like to explain our best practice approach to implementing an emergency user concept. Our approach to using an emergency user concept We have had good experience with the use of the Xiting Authorizations Management Suite (XAMS) in this area. This suite consists of various modules for creating role concepts, managing permissions including a permission concept, and also enables the implementation of an emergency user concept. XAMS works here with a limited time assignment of reference users with extended privileges to enable the emergency user concept. A self-service application may be made with a justification and a period for allocating special rights. The application window is illustrated in an example in the following screenshot: Evaluation of the use of the Emergency User Concept Once this request has been initiated, a new mode will be opened for the user, in which he can work with the extended rights. In addition, depending on the configuration, a stored workflow can be initiated as an approval process, or pre-defined controllers will be notified by email to verify activities. Once the session has ended with the emergency user, the responsible persons will receive another email with the logged activity of the user with the extended permissions. One of these logs is shown in the next screenshot: These logs can also be viewed in the system. Here you will get an overview of all the sessions that have been run. In addition, it is possible to approve activities with special rights after an evaluation. This allows the controller to get an overview of the activities undertaken with the emergency user. If you are using this Emergency User Concept and following these steps, you can ensure: Each user on the production system retains his or her original necessary rights.

The "Shortcut for SAP Systems" tool is ideal for doing many tasks in the SAP basis more easily and quickly.

So if you want to find out more, I have the following 3 tips for you: 1) Our e-book about SAP RFC interfaces 2) Clean up our free webinar about RFC interfaces 3) Blog post about our approach to optimising RFC interfaces As always, I look forward to your feedback and comments directly below these lines!

It will also discuss future target groups which may be of interest in the future.
SAP BASIS
Zurück zum Seiteninhalt