You can provide the Software Update Manager with the information about table migration durations from a previous SUM with DMO run. SUM uses this data to optimize the performance of subsequent DMO runs.

Although SUM does consider the table sizes for the migration sequence, other factors can influence the migration duration. In other words, consider more criteria than just the table size for the duration of a table migration. The real durations are the best criteria, but they are only known after the migration of the tables.

During a migration, SUM creates a text file with the extension XML that contain the information about the migration duration for each migrated table. The file is called MIGRATE<*>DUR.XML, and is created in subdirectory <SUM directory>  abap  doc  analysis. It can be used for the next DMO run to improve the table splitting. For this purpose, put the file into the download directory so that SUM can consider it during the next run.

The Software Update Manager scans the download directory in the SCANDIR_EXE phase for existing files. The files found are listed in the log file CHECKS.LOG or in the associated notification pop-up window. You can check the list to see if the migration duration file was also found. It is tagged with the CLONEDURATIONS keyword.

After the tables have been split in the EU_CLONE_MIG*PRP phases, you find in the SUM Utilities for DMO (Extended UI) the information whether the duration file meets the requirements and was therefore used. To do this, select the Table Splits view in the DMO Migration Preparation menu.