WE19 Test tool for IDoc processing
SM64 Batch Events: Overview and Management
An SAP administrator is responsible for controlling the SAP system in a company and ensuring its trouble-free operation. He or she maintains the SAP applications and is also responsible for their further development.
People tend to forget how important this element of the architecture is. The setup involved often proves to be especially important for companies looking to implement the SAP system for the first time.
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.
In addition to proactive monitoring to prevent possible errors or even complete system failures, our SAP Basis team also implements clearly defined authorization concepts. So that unauthorized persons cannot access important data and your employees are protected from unintentional violations.
Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".
Compared to an SAP ERP system, small apps are allowed instead of large applications.
This person ensures the trouble-free operation of the SAP systems.