ADMIN TOOLS
Web Development
In order to ensure the necessary expertise both in the direction of application and application-related IT departments as well as in the direction of infrastructure units, the SAP basis should be divided into an infrastructure-related SAP basis and an application-orientated SAP basis. The infrastructure-based SAP basis acts as a contact level and point of contact for IT departments such as virtualisation, storage management and databases. The application-orientated SAP basis serves as the contact and coordination level for application-related topics. BUILDING OVERARCHING EXPERT TEAMS WITH SAP basis INVOLVEMENT To reduce organisational friction points as well as to optimally handle selected topics, it is recommended to set up expert teams with the participation of the SAP basis. These teams of experts can be virtually organised and therefore of temporary duration and consist of participants from all relevant IT disciplines or business areas. If the topic of the virtual group of experts is the focus of the SAP basis, the SAP basis will take over the management and control of the expert team.
To facilitate communication within IT departments, it is necessary to identify clear communication channels and contact persons and also to use uniform tools for communication. It would also be possible to designate contact points (contact points) for upstream and downstream IT departments and external service providers and suppliers.
SCC1 Client copy
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.
The higher the degree of standardisation of operational and maintenance tasks, the more effective the technical operation and maintenance can be. At the same time, this simplifies outsourcing and, if necessary, the use of a cloud solution. CHOOSING AN APPROPRIATE SERVICE FORM Regardless of the chosen service form, as well as outsourcing and outtasking, the overall responsibility for the availability and performance of the IT-supported applications remains with the company. This still means internal coordination of maintenance windows or release booths, which remains in place. Similarly, the services provided by the external partner must be regularly monitored and their quality checked. Therefore, the chosen IT strategy must be chosen from this point of view with the lowest risk. If the technical operation is not sufficiently assessed in the decision, there is a significant business risk.
"Shortcut for SAP Systems" simplifies tasks in the area of the SAP basis and complements missing functions of the standard.
It is important that the associated approval processes can also be mapped and easily tracked.
At the same time, through the respective SMEs, the concept creates expertise in specific topics and enables communication on an equal footing with upstream or downstream IT departments as well as with external service providers.