SAP Knowledge Base Article - Public

3580792 - Modifying Data Transfer Jobs to improve the data transfer performance of the SAP S/4HANA Migration Cockpit - Migrate Data Using Staging Tables in S/4 HANA Public Cloud

Symptom

  • It is desired to modify the number of data transfer jobs for a migration object or migration project
  • It is required to improve the performance of the data transfer during migration with the SAP S/4HANA migration cockpit (Migrate your Data app)

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental." 

Environment

SAP S/4HANA Cloud Public Edition

Cause

  • The data migration of one or more migration objects within a migration project takes a long time to perform due to an inappropriate or low number of data transfer jobs.
  • The data transfer jobs option remains as default and therefore, the number of data transfer jobs is 1.  This might result in poor performance of the data migration or slow data transfer.

Resolution

To adjust the number of background jobs that are used for your migration project, perform the below steps:

  1. Open the "Migrate Your Data – Migration Cockpit" App.
  2. Open the project where the modification of the number of background jobs for the data transfer is required.
  3. On the Migration Project screen, select “Job Management” to adjust job settings.

  1. Click "Edit" and in the field "Max. Data Transfer Jobs" enter a number of jobs higher than 1 in order to leverage the job parallelization of the data transfer and thus, improve the performance of the data migration.

On this screen:

  • To adjust the maximum number of background jobs used for the project.
    • It is possible to adjust the maximum number of jobs to be used per migration object.
    • Note that if an activity has already started for a migration object, then increasing or decreasing the number of jobs for the migration object will have no effect on that activity.

On the Job Management screen, it is possible to adjust the maximum number of background jobs that are used for the project or for a specific migration object. Data transfer jobs are responsible for transferring the data in the staging tables to the target SAP S/4HANA Cloud system.

The default number of background jobs for a project is 8 in SAP S/4HANA Cloud Public Edition. For single migration objects, the default number of data transfer jobs is 1. Increasing the number of data transfer jobs should be considered for the following situations:

  • A lot of data to transfered.
  • The migration object is a complex object with multiple staging tables.
  • Using one job results in an unacceptable data transfer time.

For more details see:

Restrictions:

  • In SAP S/4HANA Cloud Public Edition, the number of available batch processes is normally 10 per instance (Application Server).
    • Usually, for quality environments, there is one Application Server (10 jobs available) and for productive environment 2 Application Servers (20 Jobs available). The migration cockpit will only allow up to 80% of these processes to be used for the migration object.
    • In migrating several migration objects in parallel by using multiple migration projects, the system could run out of batch job processes and will queue the jobs. The result will be that the migration remains at a low percentage level because jobs are waiting in the queue to be executed.
    • We therefore recommend to avoid running too many batch jobs in parallel - this will not improve the performance of the data migration.

Remarks:

  • Increasing the number of data transfer jobs (to improve the performance of the data transfer) is meant for migration objects for which high data volumes need to be migrated.
  • For each migration object, SAP S/4HANA migration cockpit will consume at least 2 batch-job processes. One for controller job or one for calculation job, and N - 1 for load jobs. (N -1 is equal to "Max. Data Transfer Jobs" you have set for each migration object in migration cockpit).
  • For S/4HANA Cloud Public Edition, the migration cockpit will only allow up to 80% of these processes to be used for the migration object. This restriction is due to performance considerations. If you are transferring multiple objects in parallel it is important to note that the background jobs will queue up, which can negatively impact the performance of the system.
  • Distributing the migration objects into different migration projects will not help regarding performance. On the contrary, it will lose the advantage of the central cross-object value mapping that the migration cockpit provides.
  • If the step Simulate Import or Execute Import is in process for a migration object, changing the number of data transfer jobs has no effect. For the changes to take effect, need to wait until the activity has completed. If the activities are run again, the updated number of data transfer jobs will be used.

See Also

Other relevant information, KBAs or SAP Notes:

For performance tips & tricks for the SAP S/4HANA migration cockpit: Migrate Data Using Staging Tables see

3580750 - Performance tips & tricks for SAP S/4HANA Migration Cockpit: Migrate Data Using Staging Tables in S/4 HANA Public Cloud Edition 

  SAP S/4HANA Migration Cockpit

  • SAP Note 2538700 - Collective SAP Note and FAQ for SAP S/4HANA Migration Cockpit - File/Staging (Cloud)
  • 2853964 - Migration Cockpit: Collective KBA for G/L Open Item or G/L Balance or FI AP Open Item or FI AR Open Item or FI - Historical balance
  • 2848224 - Migration Cockpit: Collective KBA for Business Partner (Customer, Supplier)
  • 2811788 - SAP S/4HANA Migration cockpit: Collective KBA for migration object Material/Product (SIF_MATERIAL / SIF_PRODUCT)

Keywords

data transfer jobs, batch jobs, performance improvement, migration cockpit - staging tables approach, migrate data using staging tables, performance, SAP S/4HANA Migration Cockpit, Migrate your Data - Migration Cockpit , KBA , CA-LT-MC , S/4HANA Migration Cockpit , Problem

Product

SAP S/4HANA Cloud Public Edition all versions