The Precalculation Server is a standalone application that allows you to generate and distribute Excel workbooks based on SAP BI data. Are you already using the Precalculation Server or would you like to take advantage of it in the future? I would be happy to explain the steps from installing the Precalculation Server to finally starting the instances on the target system so that you can use the Precalculation Server for your purposes. As a reader of our blog, you are certainly interested in tricks and tricks that will make your SAP system easier to handle. You may be familiar with the situation where you want to install a Precalculation Server yourself. Here you will learn how this task can be implemented in the SAP environment. Prerequisites For example, you need a Windows 7 or a Windows Server 2012 instance on which the Precalculation Server is installed to operate the Precalculation Server. Both 32 and 64-bit versions can be used. In addition, the machine requires a .NET installation to run the Precalculation Server in addition to a Microsoft Excel installation (32-bit version is essential). Download the installation files In advance, you should download the latest installation files from the official SAP website to the target computers. Cleanup Phase If you already have an existing installation on the system, the first thing you need to do is uninstall all items to use a clean host for the Precalculation Server. You can do this by calling the Windows Control Panel: The order must be followed according to the SAP documentation. Therefore, apply the following procedure for uninstallation, no installation of SAP should be visible anymore: Order: 1) SAP BW Precalculation Service 2) SAP Business Explorer 3) SAP GUI for Windows XY Note: During the installation and uninstallation of individual components, the progress bar status may be suspended at certain locations. This is not a cause for concern, but a normal behaviour. Often, it will stand at 92% or 95% for about 10 minutes.
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).
SM20 Evaluation of the Security Auditlog
In the area of SAP Basis it is necessary to make temporary changes in the security settings of the clients and systems in the course of system updates. You can use the system changeability variable to specify whether changeability of cross-client data, such as programs or menus, as well as client-independent customizing is allowed.
Either temporary programme calls are blocked that are actually desired or enormously large gateway logs must be analysed. If, due to the heavy workload, one were to decide to forgo the use of the access control lists permanently, this would be a major security vulnerability. The unprotected system does not have any limitations on the external services that may register, and there are no rules for running programmes. One possible consequence would be, for example, the registration of an external system on which malicious programmes exist. At the moment when foreign programmes are running on your system without any control, you can expect that great damage will be done. For example, it ranges from an unnoticed reading of purchase and sales figures, a diversion of funds, to a paralysis or manipulation of the entire system. In addition, this scenario is also possible for poorly maintained access control lists. Our solution: secinfo and reginfo Generator for SAP RFC Gateway To solve the problem, we have developed a generator that can automatically create secinfo and reginfo files based on gateway logs. The basic idea is based on the logging-based approach. It performs the task of time-consuming analysis of log files and also ensures maximum reliability through automation. Nevertheless, the entries of the generated files should be checked by one person. Since the log files used as input are sensitive data, of course none of the inserted data leave your system. More information about the generator can be found here.
"Shortcut for SAP Systems" is a PC application that simplifies or even facilitates many activities in the SAP base.
The SAP Basis Plug-In is an add-on that you can install on an SAP Web Application Server or other product based on SAP_BASIS 620 and SAP_ABA 620 or higher releases of these software components.
SAP recommends the use of the value ALL.