Archiving
SHARING OF THE SAP basis INTO A SINGLE APPLICATION AND INFRASTRUCTURE-RELATED LAYER
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.
Many companies that use or would like to use an SAP Basis system seek advice from external service providers or completely outsource the administration of the system. SAP Basis Consulting is a technical consulting service that covers many tasks and sub-areas related to SAP Basis. Providers include BasisTeam IT Service & Consulting AG, Phoron, Mindsquare and many others.
Troubleshooting and support in case of occurring problems
Although you always make sure that authorization roles are generated when administering them, it happens again and again that there are red lights in the user assignment in the production systems. Have you considered user matching?
For administrators, a useful product - "Shortcut for SAP Systems" - is available in the SAP basis area.
The website "www.sap-corner.de" offers many useful information about SAP basis.
Everything depends on this "SAP Basis" to keep SAP systems running.