SAP Basis Preparation of migration to SAP HANA - SAP Basis

Direkt zum Seiteninhalt
Preparation of migration to SAP HANA
A new SAP system is created...
With simple job programming, you can start in clear environments with few dependencies. If the number of jobs and the complexity increases, an automatic job control is a good choice. Honico Batchman is such a solution, a 100% SAP integrated AddOn, which is quickly and easily installed via normal transports. The advantage here is that no additional infrastructure is required; instead, the existing SAP system landscape is used for the entire control and execution without incurring a loss in performance. This also ensures full audit and operational security (compliance). Since pure SAP systems are rather the exception, non-SAP systems can also be controlled and monitored. As a third option, high-end solutions are available that additionally monitor the infrastructure and legacy. Widely used products in this segment are UC4 and Arvato Streamworks. These three solution options differ significantly in terms of price and scope of services. IT departments in companies must therefore evaluate which solution is best suited to their own requirements.

Sound up-to-date know-how: With SAP Basis support, you can save time and money on training that would be needed in-house to keep your employees up to date. An SAP expert is always familiar with the latest technologies.
Migration to the Cloud Platforms
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).

The coverage of old core tasks (such as security or compliance) and new core tasks (such as cloud or mobility) must be increased in the sense of a holistic consideration. This means that certain tasks must be considered not only in the context of the SAP basis, but also in the overall context.

The "Shortcut for SAP Systems" tool is ideal for doing many tasks in the SAP basis more easily and quickly.

These are two relatively simple examples of Security Check tools' rulebook.

Client-server architecture and configuration.
SAP BASIS
Zurück zum Seiteninhalt