3016328 - Numbering sequence is not the same as the sequence in migration template

You are working with migration objects, such as Customer and Product, in migration cockpit. You found internal numbering sequence is not the same as the sequence in your uploaded migration template.

For example, the records entered in the template in the following sequence.

3

1

2

11

20

After uploading the template into the staging table, the sequence is in a sorted way as below.

1

11

2

20

3

• SAP S/4HANA Cloud
• SAP S/4HANA

The sequence will be sorted after uploading data in staging table. This is not controlled by migration content or migration tool. SAP tables will sort the source IDs by ascending. So the staging tables for data migration are sorted in the same way.

If you would like to influence the new numbering by the source records sequence in your template, you have to ensure that the sequence will not be changed after loading into staging table.

For example, the following source ID will be sorted again because the sequence in staging table will be different.

2

1

4

3

While the following soure ID won't be sorted again.

A001-2

A002-1

A003-4

A004-3

migration, sequence, internal numbering, sort, sequencial, data migration, PM - General maintenance task list , KBA , CA-GTF-MIG , SAP S/4HANA Data Migration Cockpit Content (LTMC) , CA-LT-MC , S/4HANA Migration Cockpit , Problem