SAP Basis Involving business departments in job planning - SAP Admin

Direkt zum Seiteninhalt
Involving business departments in job planning
Configuration of email notifications
SAP HANA base administrators can master the database in a way that wasn't possible back then. The SAP database is much more self-healing. Errors do less damage, are easier to detect and fix, and are less likely to impact system performance and availability before they are fixed. Monitoring tools can automatically scan application logs, identify potential errors and even suggest fixes, making it much easier to get to the root of the problem.

You can also create your own folder with your transactions as a folder in the SAP Easy Access menu. Because if you create many transactions as favorites, it can quickly become confusing. So you can easily and quickly group your transactions in different folders.

If you want to get more information about SAP basis, visit the website www.sap-corner.de.
SYSTEM CHANGEABILITY AND CLIENT SETTINGS
At best, for the time in which an emergency user is in service, a separate log of the activities undertaken is written, which can then be evaluated. In the following chapter I would like to explain our best practice approach to implementing an emergency user concept. Our approach to using an emergency user concept We have had good experience with the use of the Xiting Authorizations Management Suite (XAMS) in this area. This suite consists of various modules for creating role concepts, managing permissions including a permission concept, and also enables the implementation of an emergency user concept. XAMS works here with a limited time assignment of reference users with extended privileges to enable the emergency user concept. A self-service application may be made with a justification and a period for allocating special rights. The application window is illustrated in an example in the following screenshot: Evaluation of the use of the Emergency User Concept Once this request has been initiated, a new mode will be opened for the user, in which he can work with the extended rights. In addition, depending on the configuration, a stored workflow can be initiated as an approval process, or pre-defined controllers will be notified by email to verify activities. Once the session has ended with the emergency user, the responsible persons will receive another email with the logged activity of the user with the extended permissions. One of these logs is shown in the next screenshot: These logs can also be viewed in the system. Here you will get an overview of all the sessions that have been run. In addition, it is possible to approve activities with special rights after an evaluation. This allows the controller to get an overview of the activities undertaken with the emergency user. If you are using this Emergency User Concept and following these steps, you can ensure: Each user on the production system retains his or her original necessary rights.

When it comes to outsourcing or outtasking SAP Basis services, we see ourselves as an experienced partner for ensuring that your SAP systems run smoothly. In addition to planning your future SAP deployment, we perform upgrades and configuration changes. We support you on-site and/or remotely in all SAP system management tasks to ensure the continuous availability of SAP applications.

"Shortcut for SAP Systems" makes it easier and quicker to complete a number of SAP basis tasks.

There are very few differences between permissions.

To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.


The Outside-In process involves knowledge from external sources in idea generation.
Zurück zum Seiteninhalt