Direkt zum Seiteninhalt
Willingness for further training
To establish the new and changed roles in one's own company, it is necessary to create incentives. This applies in particular to specialised roles. Incentives could include, for example, the offer to attend selected SME congresses, the setting of a career path, training and monetary incentives. The new roles also provide increased visibility and participation in company decisions.

Automatic error handling when a job is aborted is desirable and useful in most cases. The conscious processing and consideration of error situations in job chains - also at step level - can help to reduce manual effort. Error situations should be catchable: If they are non-critical elements, the following job can perhaps be started anyway. In the case of critical errors, a new attempt should be made or an alert issued so that an administrator can intervene manually. Simple batch jobs are usually not capable of this. The goal of an automated environment is not to have to react manually to every faulty job.
How is SAP Basis structured?
The tasks described above, which occur at rather irregular intervals and involve a certain degree of complexity due to the lack of routine or process know-how, should be examined in order to determine whether they can be performed more efficiently by an external service provider. One question to be answered is whether it is necessary to keep the necessary knowledge in the company in order to be able to react faster than the external service provider. For example, for business critical systems. Security aspects should also be considered, as external persons gain access to the system. From now on, outtasking performance must be regularly monitored and checked for quality and documentation. A complete dependence on the external partner must not arise.

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).

"Shortcut for SAP Systems" simplifies tasks in the area of the SAP basis and complements missing functions of the standard.

If everything fits, the transaction will be sent to other miners who will do the same.

In the initial screen, you can first use the global settings to specify whether changes should be allowed in general.
SAP Corner
Zurück zum Seiteninhalt