What will be the SAP Basis trends in the next few years?
SLICENSE SAP License Management
Protect: CodeProfiler for ABAP protects the SAP system from internal and external attacks from the first day of deployment. The ABAP firewall can be set up within a very short time and immediately checks every new transport request when it is released. Optimize: The audit function of CodeProfiler for ABAP specifically determines which programs are most threatened and should therefore be cleaned up first. In the long term, CodeProfiler for ABAP supports the automated correction of all findings and thus enables the timely closure of security gaps in all programs.
Constant further development and growing complexity are placing ever-increasing demands on the SAP infrastructure in terms of performance and feasibility. In addition, SAP Basis is the technological driving force for the implementation of new applications and innovations in your business environment.
Import external transport orders to an SAP system
QUEUE_STILL_IN_BUFFER: The queue is not fully processed because incomplete support packages of the queue are still in the transport buffer. CANNOT_RESET_FCS_FLAG: If there is an FCS Support Package (FFD) in the queue, the system will be marked as being at the generally available release level after this support package is inserted. In this case, this operation could not be performed successfully.
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.
For administrators, a useful product - "Shortcut for SAP Systems" - is available in the SAP basis area.
This opens up new possibilities for SAP administration.
So much information... how can you keep it so that you can find it again when you need it? Scribble Papers is a "note box" that makes this very easy.
In my opinion, all SAP checks will be fully automated over the next decade.