SAP Solution Manager's Software Update Manager (SUM) with the Database Migration Option (DMO) -- or SUM-DMO --...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
is the best choice for migrating to Business Suite on SAP HANA if your ERP system must be upgraded first.
Moving to SAP HANA requires an ERP system of at least EHP 6.0, and SUM-DMO -- an important tool in the Software Logistics Toolset 1.0 -- enables companies to upgrade to EHP 6.0 or higher. SUM-DMO can also enable you to convert your database to Unicode, if required, before migrating to HANA. If the company's source SAP ERP system is already on EHP 6.0 or higher, SAP's other migration tool, Software Provisioning Manager, can be used, since it enables database migration straight to SAP HANA. (It offers no intermediary upgrading step, as SUM-DMO does.)
Each organization's IT landscape varies widely in terms of the hardware and software it has installed. That's why Software Logistics Toolset 1.0, or SL Toolset 1.0, which consists of several database migration tools, is so important. Especially through the use of SUM-DMO, it greatly harmonizes the entire HANA migration process, although there are other important tools in the Toolset that companies may want to use.
Here are some other useful tools and best practices for use with Software Update Manager with the Database Migration Option that can help enable a successful HANA migration.
Maintenance tools. Install and use Maintenance Planner, or its successor, Maintenance Optimizer, which offers more features. These database migration tools guide the system administrator through the upgrades to the source SAP system, prepare the media and build an instruction XML file that will then be used by SUM-DMO.
EarlyWatch. Generate an EarlyWatch report for the system being migrated to SAP HANA. When importing a database into HANA, the system will refer to this report.
Multitask tools. Install the Table Comparison tool and the Benchmarking Migration tool from SL Toolset 1.0. These will guide and validate the migration process, as well as simulate downtime for actual migration activities.
Another advantage of using these tools is that they perform several tasks automatically, such as determining the number of files by which a table should be split, as well as which tables to migrate first to ensure a smoother and faster migration. This automation eliminates or minimizes the need for guesstimates, which often lead to migration errors.
The Benchmark Migration tool greatly helps in realistically estimating the time required for the migration project to SAP HANA from the source database. Using this tool is possible while the source system is still operational. It's also possible to define the percentage or number of tables to be used as a sample for simulation so as to have a realistic time estimate for the actual migration project. The Benchmark Migration tool also suggests hardware specifications to use during the export from and import to HANA.
The Table Comparison tool enables a comparison of the source and target database tables to ensure there will be no inconsistencies during actual migration. When simulating, it's better to compare only the selected tables (instead of all), as doing so expedites the comparison process and prevents the system's slowdown.
Consistency. Even if SAP releases a new version of Software Update Manager with the Database Migration Option during the database migration project, continue using the one already in process. Using a new version midprocess risks project delays caused by any new release bugs or other shortcomings.
Shadow system. Using SUM-DMO enables the system to create a shadow, or copy, system of the source system. All updates are simulated and implemented to the shadow system while the original system is still operational.
However, this additional shadow SAP system requires additional resources, such as servers, memory and CPU. It's best to take these factors into account and to manage these temporarily required resources accordingly.
Improvement contributions. Send database migration summary files to SAP. This serves two purposes; it helps SAP fine-tune and improve future releases of SUM-DMO, and it contributes to the dissemination of issues and lessons among the SAP community and ASUG members.
Updates. Since SL Toolset is continuously updated, be sure to check SAP Note 1563579 for the latest updates.
A primer on HANA cloud options
Your guide to Business Suite backup and recovery
Get to know Business Suite
Dig Deeper on SAP Solution Manager
Related Q&A from Jawad Akhtar
A logical extension of the Sales and Distribution component, and part of Business Suite, SAP CRM has components to tackle sales, marketing, service ...continue reading
SAP Maintenance Event Builder brings better organization to smaller maintenance projects by combining maintenance tasks, rescheduling and resource ...continue reading
The kitting process can be triggered either from SAP ECC or SAP EWM in kit-to-stock and kit-to-order business scenarios, and reverse kitting is ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.