To inherit SAP permissions with different organisational levels
SM58 Transactional RFC
In order to cope with the digital transformation in general, but also to cope with the changing demands on the SAP basis and its scope of responsibility, it is necessary to revise existing roles and define and establish new roles. These include the roles of the technology architect, new features of the Subject Matter Expert (SME), and the role of the Expert Team Lead in leading a group of experts. Further information can be found in chapter 7.1 and 9.3 of the Master's thesis.
Job scheduling: your system needs to run various automated background jobs that consume resources. Your administrator must carefully schedule these tasks when user demand is low so they don't impact performance.
SM64 Batch Events: Overview and Management
We always keep your systems up to date: System upgrades and updates are very important both functionally and for the security of your data. Whether release upgrades or importing important support packages - we are your experts.
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.
"Shortcut for SAP Systems" makes it easier and quicker to complete a number of SAP basis tasks.
In a change of department or a new activity, permissions are automatically adjusted.
SAP Basis refers to the administration of SAP system that includes activities like installation and configuration, load balancing, and performance of SAP applications running on Java stack and SAP ABAP. This includes the maintenance of different services related to database, operating system, application and web servers in SAP system landscape and stopping and starting the system. Here you can find some useful information about SAP Basis: www.sap-corner.de.
For a better overview, it is usually useful to name and number the derivatives after the master roles.