Show TOC

Function documentationTransfer Performance


This report simulates a TDMS data transfer based on your system settings and provides information about the throughput of the TDMS run. You can use the information to modify your system settings for an optimal throughput.


  • You have ensured that the following release requirements are met:

    • All participating systems are on SAP NetWeaver 700 or above

    • All participating systems are on SAP TDMS Release 4.0

  • You have defined a system landscape using either of the following methods:

    • You have created a migration package for SAP TDMS

    • You have defined RFC destinations for the sender system and the receiver system using the SM59 transaction.

  • You have carried out one of the following actions before running the report:

    • You have created a new migration package and defined the RFC destinations for the package.

    • You have created RFC destinations using the SM59 transaction for the intended sender system and receiver system.


In the MWB_TRANSFER_PERFORMANCE transaction, proceed as follows:

  1. Preparation: The report provides default values for the data block size and data transfer volume per table. However, depending on your hardware specifications, you can change the default values. SAP TDMS transfer the data in portions, where each portion size equals the data transfer volume per table over the data block size. Enter values in all fields and execute the report.

    Recommendation Recommendation

    We recommend that you execute this step as a batch job to avoid execution time outs.

    End of the recommendation.
  2. Job Monitor: After you execute the report, SAP TDMS generates batch jobs to prepare the data for transfer simulation. You can verify the status of the batch jobs in the SM37 transaction. If you executed the preparation step as a batch job, verify that five jobs are complete. If you executed the preparation step in the dialog mode, verify that four jobs are complete.

  3. Transfer Jobs: After the batch jobs are successfully completed, the screen to start the transfer simulation appears. Specify the number of transfer jobs to be used per table by SAP TDMS for the simulation. When you execute the report, SAP TDMS initiates the transfer simulation for three tables. Hence, the total number of transfer jobs used is three times the number of jobs you specify. Ensure that sufficient batch processes are available in the central system of your data migration landscape. While the data transfer simulation is running, you can execute this step again to specify a different number of batch jobs. You can arrive at an optimal number of batch jobs by evaluating the impact of the specified jobs on data transfer.

  4. Transfer Performance: Specify the mass transfer ID and access plan ID of the current run in the Mass Transfer Run Details section. After execution, the Mass Transfer Performance Tracking screen appears. Choose Start Performance Tracking to view information about the throughput for the current run. After the simulated data transfer is complete, choose Stop Performance Tracking.

    You can specify the mass transfer ID and the access plan ID of the previous run to view a comparison between the two runs.

  5. Runtime Information: For a quick view, skip Step 4 and execute the Administration of Transfers to view runtime information about the simulated data transfer such as application logs, tables participating in the simulation, and the number of errors. Choose the Runtime Information tab page to view information about the progress of data transfer and the throughput.

  6. Reset Test Transfer: Executing this step deletes all temporary objects created by SAP TDMS in the simulated run.

    Recommendation Recommendation

    We recommend executing this step as a batch job to avoid execution time outs.

    End of the recommendation.