Job Management Concept
SQ03 User group maintenance
This improves the capabilities of SAP HANA base administrators and increases the level of service they should provide. Your Basis team can more easily fine-tune your data replication strategy to meet demanding disaster recovery and high availability standards.
After your user has the necessary permissions for the SQL Editor, perform the following steps: Call the DBACOCKPIT transaction. Open the following folder structure in Database Administration: Performance -> Additional Functions -> SQL Command Editor Enter your first query in the input query. Then click Run or alternatively press F8 View of the DBA Cockpit Invoke the input query and drop the first SQL query View the results of a query to query the users of a system.
/IWFND/TRACES SAP gateway traces
Information technology plays an even more important role in the age of digitalisation. Innovation without IT is unimaginable. But it is not just technology itself, but also how it is delivered that matters. The SAP basis sees itself as a partner and contact for new SAP technologies. Further details on the recommendation can be found in the Master's thesis in chapters 7.5 and 9.3.
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.
Tools such as "Shortcut for SAP Systems" complement missing functions in the SAP basis area.
Positioning is extremely important for the SAP basis.
Because hybrid landscapes are seen as the operating model of the future, it is necessary to develop monitoring strategies for this.