What has changed in the past decade and what can we expect in the coming decade? How will they affect the requirements profile of SAP Basis experts and how can they adapt to them?
Finally run SQL queries directly in the SAP system
Cross-client tables can be modified. The control system of another, productive client can thus be undermined and undermined. Quite a lot of power! Did you also know that the SAP system provides a feature that deletes table change protocols (DBTA BLOG table) and that it is effective across all clients? If the table change logs have not been additionally archived via the BC_DBLOGS archiving object, traceability is no longer available. That way, every criminal act within your company can be beautifully covered up. Similarly, full access to batch management allows you to manage all background jobs in all clients with the permission. This allows you to delete old background jobs that have gone unauthorised. There are also some points to consider when managing print jobs. Typically, the following two SAP access permissions are enabled to protect print jobs: S_SPO_DEV (spooler device permissions) S_SPO_ACT (spooler actions). Why? Confidential information in print jobs is not protected against unauthorised disclosure. (Strictly) sensitive print jobs can be read unauthorised or redirected to external printers and printed out. Print jobs are unprotected unless additional SAP access permissions are enabled to protect print output. The print jobs are multi-tenant, which means that the authorisation award should also be well thought through at the point.
This possibility is particularly advantageous when it is a new topic and there is not yet a lot of know-how in the company. Instead of buying an expensive coach to teach employees the basics of a new topic, this means that the knowledge can be made available more cheaply and in a longer term, for example, through an online course.
SAP HANA®
Permissions beyond the daily task spectrum are granted only for limited periods and under control. The activities with the emergency user are logged in a revision-proof manner. Do you already have an emergency user concept in use or would like to introduce one? I'm happy if you share your experience with me! You can leave me a comment or contact me by e-mail.
When I began my career administering SAP ERP on Oracle in the early 1990s, running a database required far more knowledge. An Oracle administration expert with a decade of experience understood perhaps only about 5% of what the database required.
"Shortcut for SAP Systems" simplifies tasks in the area of the SAP basis and complements missing functions of the standard.
Administrators often need to replicate part or all of a database, for example, to create a system backup or test an upgrade before putting it into production.
If you want to get more information about SAP basis, visit the website www.sap-corner.de.
Therefore, in the whole context of standardisation and automation, a sequence of tasks and systems needs to be followed.