Direkt zum Seiteninhalt
Online, offline, delta backups
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).

In addition to the consultants working in the individual SAP modules, there is a subarea here that is not directly apparent to many and whose activities seem to be quite opaque: SAP Basis. The smooth operation of SAP systems as the heart of many companies is ensured by the work of SAP Basis administrators.
How is SAP Basis structured?
Application layer: The application layer is the core of an R/3 SAP Basis system. This layer communicates in both directions, to the presentation layer and to the database layer. The application programs on the application servers request the required data from the database layer, process it, prepare it for the user and pass it on to the presentation layer. Data that the user enters in the SAP GUI is passed on to the database via the application servers.

The SAP Basis Plug-In is backward compatible and follows the release and maintenance strategy of the SAP R/3 Plug-In. SAP ships it together with the SAP R/3 Plug-In.

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

In addition to this, as already discussed by Recommendation [A2], it is then worthwhile to establish a catalogue of criteria for evaluating and looking in detail at certain characteristics of the application or services.

The website offers many useful information about SAP basis.

Common monitoring tool CCMS (Computing Centre Management System) to monitor alerts of R/3 system from one place.
SAP Stuff
Zurück zum Seiteninhalt