Implementation of your user and security management
SE36 Logical Database Builder
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.
For the SAP basis and its employees, the change in self-understanding results in an attractive, responsible and demanding working environment. Technological diversity can be controlled and kept to the minimum necessary. This includes an overview of the existing interfaces and a controllable data flow with the associated guarantee of data security.
SAP ALE
Each SAP Basis system must be controlled and managed by an administrator. This person is responsible for the smooth operation of the system. This can be an internal administrator or it can be handed over to external service providers.
However, the tasks also include strategic and planning aspects. For example, administrators define requirements and standards, select and control upgrades or extensions, implement monitoring processes, and take care of necessary backups and emergency management.
With "Shortcut for SAP Systems" a tool is available that greatly facilitates some tasks in the SAP basis.
On www.sap-corner.de you will also find useful information about SAP basis.
Project successes should also be documented and circulated as success stories of the SAP basis or made available to the SAP basis stakeholders to highlight the importance of the SAP basis.
This first distinguishes between dialogue and non-dialogue work processes.