Advice on hardware, database, operating system, type of installation (physical or virtual)
Planning of SAP environments
Customers with such a case regularly contact us. Creating a Permission Concept from the ground up is often a time-consuming task. Furthermore, the know-how, which aspects should be dealt with in an authorisation concept and how the corresponding processes can look practical and at the same time audit-proof is often lacking. Our solution: tool-based generation of an individual, written authorisation concept In this situation, we have recommended to our customers the tool-based generation of a written authorisation concept directly from the SAP system. We use the XAMS Security Architect tool, with which we have had good experiences. This includes a template for a revision-proof and comprehensible, written authorisation concept. It includes established best practices for role and entitlement management. The template covers all relevant areas in a permission concept. The included text of the authorisation concept is completely customisable, so that the concept can be tailored to your situation without creating a permission concept from scratch. Dynamically update the written authorisation concept One of the biggest challenges after the development of an authorisation concept is to keep it up to date in the long term and to measure the sustainable implementation in the system. This is achieved by integrating live data such as configuration settings and defined rules directly from the connected system. For example, lists of existing roles or user groups and tables are read from the system each time the document is generated and updated in the permission concept. The following screenshot shows an example of what the appearance in the concept document might look like. Automatically check and monitor compliance with the concept To check compliance with the concept, the XAMS Security Architect includes extensive inspection tools. These cover the rules formulated in the concept and are suitable for measuring the extent to which the reality in the system meets the requirements formulated in the concept.
The following folders on the system will then be completely deleted: C:\Program Files (x86)\Common Files\SAP Shared\BW delete C:\Program Files (x86)\Delete SAP C:\Program Files\SAP This completes the CleanUp phase. Install new version SAP GUI and Bex (BI Addon) The first step is to install SAP GUI and Business Explorer (Bex). Please select and install the following in the installer (see screenshot): SAP GUI Suite under SAP GUI for Windows (=Frontend) Business Explorer complete The progress bar often stays at about 93%. It takes a few minutes to complete the installation.
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).
Among other things, it determines which application server a user logs on to in order to distribute the workload (load balancing). The message server also enables the individual application servers to communicate with each other.
The "Shortcut for SAP Systems" tool is ideal for doing many tasks in the SAP basis more easily and quickly.
When the table is called, the S_TABU_DIS or S_TABU_NAM permission object is checked with a specific activity.
The SAPSolution-Manager can also support this as a tool of SAP e.g. through the Guided Procedures.