Performance optimization
Release
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.
Before the project starts, it must be clear which systems are to be connected to the IdM and which services the system is to provide. This requires close collaboration between the department and IT, as later adaptations or additional systems will extend the implementation and exceed the budget. Analysing existing data To successfully implement an Identity Management System, high quality data is essential. Users' root data must be verified, updated, or maintained. Automation with incomplete or even incorrect data is otherwise not conceivable. Rethinking the Permission Concept With the introduction of an Identity Management System and a workflow for permission granting, the existing roles should be scrutinised once again. You should ask yourself whether the user knows what role he chooses from the current catalogue and whether it is sufficient for his task. Set Role-Owner Not only the user needs to know which role to choose. There must also be a person in charge of the role who adapts or adapts the role as required or acts as a point of contact when required.
SU01 User maintenance
Permissions beyond the daily task spectrum are granted only for limited periods and under control. The activities with the emergency user are logged in a revision-proof manner. Do you already have an emergency user concept in use or would like to introduce one? I'm happy if you share your experience with me! You can leave me a comment or contact me by e-mail.
If you look at everything I've described up front in its entirety, it quickly becomes clear which direction things are headed: the SAP basis will increasingly move toward an SRE-centric environment over the next decade. This is what the future of SAP looks like, and I look forward to an exciting journey.
"Shortcut for SAP Systems" makes many tasks in the area of the SAP basis much easier.
This means that it can be explicitly stated in which cases the SAP basis needs to be contacted and involved in order to make the necessary decisions and not jeopardise a project or company success.
It is used to eliminate conflicts that may arise between the different support packages and an add-on.