Implementation and operation
Controlling users and access rights
Before SAP HANA was released, there was no SAP database - you had to install SAP ERP (or the application you were using) on a third-party database, such as Oracle or SQL Server. SAP developed the HANA database to fully leverage the power of SAP's next-generation S/4 software.
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 the basis to an external service provider, there are often still tasks from the user and authorization management environment at this point.
Creation of final documentation and handover
To use all the features of the SAP Patch Manager, you need the following permissions: S_TRANSPRT S_CTS_ADMIN Both are in the S_A.SYSTEM permission profile. If you log in to the Mandant 000 and your user base contains the appropriate permission profile, then you can use all the features of the SAP Patch Manager. When you log in to another client or without the appropriate user profile, you can only use the display functions. Map this permission profile to the system administrator only. Only the system administrator should have permission to perform the following actions: Support Packages Download Support Packages Play Support Packages Confirm Successfully Recorded Support Packages Reset Support Package Status Support Packages eliminate errors in the SAP system or make necessary adjustments due to legal changes, for example. The affected objects will be replaced in your system. Each Support Package is valid for one release level (but for all databases and operating systems) and requires a precisely defined number of predecessors. The upgrade from the following release or revision level contains all support packages from the previous booths that were available until the upgrade was delivered. SPAM ensures that support packages are only played in the order specified. To avoid problems, play all support packages as they are deployed. This allows you to keep your system up to date.
This point may sound a little trivial at first. Who tests, surely documents this? Experience shows: Yes, but often patchy. In the case of unsuccessful tests, where subsequent or additional developments are due and the cause of the error is not directly apparent at first glance, good result documentation often pays off. This saves developers time in communication and effort by re-imagining the scenario. At this point, the SAP Solution Manager offers extensive opportunities to manage templates and result documents centrally and in the individual test plans. Automated testing only Automated testing offers many advantages, whether it is a higher software quality through more comprehensive test coverage or reusability of test cases. However, it does not always make sense to use only automated test scripts. A less good choice is the test automation for frequently changing software or processes, because the maintenance effort can be enormous. At this point, it is often more effective to run manual test runs instead of spending a lot of time customising test scripts. Poor test preparation The relevant processes have been defined, the test plans have been created and the test period has begun - so can testing begin? Not always. Lack of test preparation often leads to unplanned additional time costs. Sometimes the testers were not familiar with the test environment or no one thought about taking care of a sufficient and current test data set (master data, movement data). Make sure you have thought of everything you need! (missing test data, unrepresentative test environment, unstable).
With "Shortcut for SAP Systems" a tool is available that greatly facilitates some tasks in the SAP basis.
It's not for nothing that "SAP Basis Administrator" is a career field in its own right.
If you want to get more information about SAP basis, visit the website www.sap-corner.de.
They should all be marked and deleted until the view is empty again.