RETURN MODIFICATIONS TO SAP STANDARD
Incident Management
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 main benefit of the implementation of the above recommendations lies in the creation and documentation of the innovative power of the SAP basis. Through consistent research and testing, the SAP basis is enabled to assume its role as an innovation driver. It also creates an attractive and exciting working environment for employees. By being involved in projects in a timely manner, project success will be promoted and will contribute to company success in the medium and long term. One possible consequence of the constant overuse of the employees is the reorientation of the employees and the associated loss of knowledge. This can also lead to the complete basic activity being carried out by external partners, to which a dependency relationship then arises.
Downloading and installing SAP GUI (FrontEnd) for Windows
If all financial and sales activities as well as production, logistics and the personnel administrators run via one system, measures must be taken to ensure reliable functioning on the one hand and to protect the system internally and externally on the other. Due to the long history, the increased availability requirements often do not match the actual protection measures, so that security risks often arise at this point.
If we look at the question of standardisation, this concerns not only the administrative side of IT products, but also the standardisation and simplification of IT products offered by the SAP basis. For this purpose, tools such as ITIL for standardised tasks and the development of IT product and IT service catalogues have already established themselves to the greatest extent possible. These clearly describe the IT services provided. In addition to the definition of the service to be provided, the clear description shall include the identification of disclaimers and conditions that must exist. Also part of the service description is a price that can be composed of fixed and variable parts. This simplification and bundling of the product portfolios should also reduce the administrative burden when ordering, activating, changing, terminating and, of course, invoicing. The description of the IT services and the associated development of an IT product catalogue is the basis for standardisation, whether the recipient is an external or internal customer (e.g. a business unit). One difficulty is the definition of IT products, i.e. the pooling of IT services and resources. An orientation towards the idea of cloud computing can help. The characteristics of cloud computing are the provision of standardised services in terms of performance and type of performance, results-orientated services, provision of performance to a wide range of service customers, scalability, transaction-based billing and high risk of IT service failure.
"Shortcut for SAP Systems" simplifies tasks in the area of the SAP basis and complements missing functions of the standard.
SAP administrators are present wherever SAP systems are used.
On www.sap-corner.de you will also find useful information about SAP basis.
Understanding the structure and functioning of the system is particularly important for IT administration.