Handling SAP day-to-day business such as administration, maintenance and configuration of your SAP systems
Every SAP system develops over many years. It grows and changes with the company. The more functions are mapped in it and the more data is stored, the greater the importance of and dependence on this central ERP system. There is no such thing as a standard SAP Basis solution. It is developed individually with reference to the company.
Through a sound expertise in the SAP technology environment, it is recommended to bring the know-how of the SAP basis into the IT strategy and IT roadmap. For this, the responsibility lies primarily with the CIO as the carrier and responsible of the IT strategy and the IT organisation. Likewise, the SAP basis should serve as a sparring partner for individuals and boards (such as enterprise architects) that significantly influence the strategy.
But when it comes to the intricacies of large SAP environments, Ansible quickly reaches its limits. If you want to use Ansible to implement simple automations - starting and stopping SAP environments, for example - you have to put up with a lot of manual effort and complicated scripts.
All the roles that contain the string "ADM" are considered critical, as they usually refer to administrative roles. When identifying critical SAP permissions, profiles and roles, it should be noted that SAP does propose a concept for names, but this is not always taken into account by applications or its own developments.
Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".
Create a risk register and address security vulnerabilities in a risk-based manner.
This will save you some costs.