SKILLS & ROLLS
The basics of Basis Administration
Together with our SAP development team, our SAP Basis experts develop programs and transaction processes using Web Dynpro technology. This includes, for example, our SAP AddOn "SAP Password Reset". We would be happy to develop your solution.
SAP's client concept enables a SAP system to be split into several logical sub-systems - clients. These subsystems can be used independently and in isolation as separate systems. But how should non-client transactions be treated? How can you prevent one client from accessing the other and why should you want to prevent that? In this blog post, I will answer these questions and discuss some negative examples. Why is it important to consider independent transactions separately? Imagine that every one of your employees is allowed to create or change a client in the production system, or worse, both. Creating and modifying a client in the production system is authorised and documented - you wonder what could possibly go wrong? The risk in this case is a loss of integrity of system and data, loss of confidentiality: With each new client, Superuser SAP* lives up to its comprehensive, cross-client rights and the assigned standard password.
Operating systems and databases
Planning ahead: Ideally, your SAP system administrator should make the necessary adjustments to your system landscape before end users are affected. This requires careful planning and anticipation of long-term trends.
If you get a tp-step in the cancel message, it is a transport order-independent step whose logs cannot be displayed with logs. In this case, analyse the following files: tp-Step 6: P
tp-Step N: N tp-Step S: DS All protocols are located in /usr/sap/trans/log.
Tools such as "Shortcut for SAP Systems" are extremely useful in basic administration.
The syntax of the different ACL files may vary depending on the release level.
It contains one or more application servers and a message server.