What should an SAP administrator be able to do?
Control users and access rights
Automatic error handling when a job is aborted is desirable and useful in most cases. The conscious processing and consideration of error situations in job chains - also at step level - can help to reduce manual effort. Error situations should be catchable: If they are non-critical elements, the following job can perhaps be started anyway. In the case of critical errors, a new attempt should be made or an alert issued so that an administrator can intervene manually. Simple batch jobs are usually not capable of this. The goal of an automated environment is not to have to react manually to every faulty job.
For existing solutions, it is necessary to assess to what extent the solution is customised. A modification is the more serious the more time-consuming the maintenance is, including testing, e.g. in the case of upgrades. The fewer customer specifications are available, the more suitable a system or application is for external operation by a service form to be chosen.
SAP Business Warehouse: Reset source system with function blocks
Test of EDI data transmission In the transaction WE05 all incoming and outgoing messages and IDocs as well as the status of the IDocs are displayed. If the order data is correctly entered and the partner profile is correctly configured, the IDoc is listed as successfully processed.
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 many tasks in the area of the SAP basis much easier.
A first important step was the introduction of playbooks to professionalize our work.
For more details, see the section "Further information on DBACOCKPIT" in this blog post.