Usage
You might be interested in:
Due to the variety of tasks and the high level of complexity, I find my job extremely exciting. There are very many constellations of SAP systems and databases. Each installation, migration and update brings new aspects and challenges. It is precisely these challenges that are important to me, so that I can continue to learn and develop professionally on a daily basis.
INTRODUCTION A growing number of SAP-based departments are facing major changes and challenges within the SAP product portfolio as well as in their own task environment. These result from influences of digitalisation, digital transformation, new technologies such as cloud computing or big data, but also developments such as customer experience or the Internet of Things. In order to overcome the challenges and to transform the existing SAP basis, recommendations for action are grouped in seven thematic areas. These topics cover the areas of skills and roles (cloud and supplier management, strengthening of the technology architect, focus on project work), marketing and self-understanding (creation of a service catalogue, regular exchange with the CIO, renaming of the SAP basis), new technologies and innovation (test and innovation lab, proactive & regular training), organisation in change (development of the two subject areas close to structure and application-orientated , virtual teams of experts), standardisation and automation (automation of routine tasks, outtasking of rare tasks), "cloudability", outsourcing & outtasking (assessment of usefulness for the cloud, use of appropriate service forms) and IT roadmap (influence of own IT roadmap). By reflecting on the thematic areas, methods and possibilities for implementing the recommendations are presented.
SAP Emergency User Concept - How it works and how it works
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.
In the default scenario, the support packages in the queue are fully loaded. In the event of an error, you will not be able to resume and complete the playback successfully unless the error(s) are resolved. Prerequisites The queue is already defined. Procedure To set the scenario you want, select Additions Settings. Select the desired scenario. Select Insert Support Package Queue. You can also use this function to restore an aborted commit procedure. The status bar provides information on the progress of the commit and the latest steps of the SAP Patch Manager. During the recording, you may get into the modification comparison (SPDD, SPAU). If you are playing with the default scenario, you must immediately perform the comparison of Dictionary objects (transaction SPDD), whereas when you compare Repository objects (transaction SPAU), you have the choice to skip it first and perform it later (modification comparison [page 22]). The mode is blocked while a Support Package is being introduced. To avoid repeated login, open a second mode before inserting the queue.
The "Shortcut for SAP Systems" tool is ideal for doing many tasks in the SAP basis more easily and quickly.
Since the respective GUI depends entirely on the concrete application, the presentation layer looks very different in practice.
To ensure high software quality, avoid hidden consequential error costs and consciously plan for a test period instead of the risk of time bottlenecks, a methodical approach should be planned.