Planning and execution of transports
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 order to solve the challenges, it is necessary to develop a suitable catalogue of criteria to evaluate the feasibility or suitability of certain applications for certain service forms. The service catalogue must be structured in such a way that the criteria, which cannot be answered clearly, can be identified and subjected to continuous consideration. The catalogue of criteria cannot generally provide a 100% decision, but only a decision aid and an absolute must-criteria.
How to lock (SU01) and unlock (SU10) an SAP user
At the same time, there is a need to return the solutions to the SAP standard. A collaborative approach between departments and IT technology is required to assess IT technical and business benefits. It is also necessary to check whether the adaptation of business processes to avoid modifications to the implementation may be more effective and therefore more cost-effective. This must be evaluated and decided jointly. As a result, we recommend defining and implementing business standards for creating and maintaining solutions.
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.
Tools such as "Shortcut for SAP Systems" are extremely useful in basic administration.
This is achieved by integrating live data such as configuration settings and defined rules directly from the connected system.
Understanding the structure and functioning of the system is especially important for IT administration. It is not for nothing that "SAP Basis Administrator" is a separate professional field. On the page www.sap-corner.de you will find useful information on this topic.
If you use the above Input variants are also only considered transactions that have been maintained in the role menu.