Planning and execution of transports
SWO1 Business Object Builder
Today, most customers rely on an infrastructure abstraction layer, whether it's VMware or one of the cloud hypervisors. So base administrators need to know how to provision and manage systems in the cloud.
The 5 most common errors in SAP test management In this blog post I would like to discuss the 5 most common errors in SAP test management, which in my experience occur regularly in this area. I hope that with this I can give you some guidance so that you can avoid these mistakes. No test management Quite simple. You have complex SAP software in use or are just introducing a new module tailored to your company, but the test process plays a subordinate role and tests take place only sporadically and unstructured? Then you have already made the first mistake. To ensure high software quality, avoid hidden consequential error costs and consciously plan for a test period instead of the risk of time bottlenecks, a methodical approach should be planned. Too much testing If you have decided to introduce test management, you need to weigh up the resources required for this. A large amount of testing quickly pushes the cost-benefit ratio into the realm of inefficiency, because the time required for testing drives up costs. On the other hand, the test quality should of course be high. Therefore, a structured and comprehensive approach is of high importance. Basically, you should make sure that the costs for the test effort do not exceed the average of the consequential failure costs.
ST05 SQL Trace
The database layer is used to store all company data and consists of the database management system (DBMS) and the data itself. In every NetWeaver system there is a database server on which the SAP database is located. It provides all other applications with the necessary data. The data is not only data tables, but also applications, system control tables and user data. All basic components ensure that the user has fast and reliable access to this data.
Migrations occur, for example, when a customer decides to host his systems at Rödl & Partner and the SAP systems therefore have to be migrated from in-house operation or from the original hosting provider to our data center. Also in the course of a conversion to S/4HANA, the data is migrated from the original database type to an SAP HANA database. This is also done with the tool "SUM" (Software Update Manager) via the so-called "DMO" (Database Migration Option).
Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".
We set about creating detailed playbooks for all common scenarios - installations, portals, upgrades and migrations - and platforms.
SAP lockout issues: Call the SM12 transaction and make sure that there are no programmes named RDDIMPDP.