SolMan - the Solution Manager takes over the monitoring of the system status and enables central application management
SAP Solution Manager
Site Reliability Engineering(SRE) is the equivalent of SAP Basis in the Google world. Ben Treynor, who has been with Google since 2003 and is considered the godfather of SRE, describes SRE as "what happens when you give operations tasks to a software engineer".
The marketing mix model is suitable for creating a marketing concept. This is usually divided into four pillars - the four Ps. These are Product, Price, Place and Promotion. In the case of services, this is often accompanied by the aspect of personnel policy. Although the marketing mix model is aimed at the external distribution of products and services, aspects of it can also be applied to an internal marketing of the SAP basis. For the design of the respective areas of the marketing mix, it is recommended to use a guide to develop a marketing concept. STEP 1: DEFINITION OF PERFORMANCE This step deals with the description of the services to be offered. Similarly, this step provides a categorisation of the type of service. These include, for example, the levels of secondary or primary service. With respect to the SAP basis, this step is concerned with product portfolio analysis and the creation of IT products and a product catalogue. STEP 2: OWN RESOURCES Subsequently, a determination of one's resources takes place. That is, it identifies the resources that are available and that can be used and the resources that need to be developed. Resources are people, objects, systems, knowledge, and funds. For the SAP basis, this step is an inventory. STEP 3: DETERMINATION OF THE OBJECTIVES The mission and vision of service providers will be determined in the framework of the setting of the objectives. It also sets measurable targets for the next three years.
SWDM Business Workflow Explorer
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.
In every company with an SAP system, there is someone who is responsible for the SAP Basis. This person ensures the trouble-free operation of the SAP system. He or she accompanies maintenance work and intervenes in special situations, such as poor performance. Even for companies that hand over the operation of Basis to an external service provider, there are often still tasks from the user and authorization management environment at this point.
Tools such as "Shortcut for SAP Systems" are extremely useful in basic administration.
This can be called under Services.
So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.
Ten years ago, there wasn't much more for SAP Basis experts than SAP Solution Manager.