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

When working with migration objects that creates instances using internal numbering, such as Customer or Product, in migration cockpit, internal numbering sequence is not the same as the sequence in the 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 Public Edition
• SAP S/4HANA

The sequence will be sorted after uploading data in staging table. This is neither controlled by migration content nor migration tool. SAP tables will sort the source IDs by ascending. As staging tables are transparent SAP tables, the staging tables for data migration are sorted in the same way.

The creation of internal numbering is also influenced by the configured number range configuration and the internal number range buffers (for details see for example KBA 1817764). Dependent on the number of jobs defined for the migration object during the migration within Migration Cockpit's Job Management, the jobs can run in parallel on different application servers and then different number range buffers are consumed.

To ensure that the new numbering is influenced by the source records sequence in the uploaded template, it is important to prevent any changes to the sequence after loading into the 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 source ID will not be sorted again.

• A001-2
• A002-1
• A003-4
• A004-3

KBA 1817764 - Number range skip in Customer / Vendor / Business Partner

migration, sequence, internal numbering, sort, sequential, data migration, PM - General maintenance task list, number range buffer, product, customer, migrate your data , KBA , CA-GTF-MIG , SAP S/4HANA Data Migration Cockpit Content , CA-LT-MC , S/4HANA Migration Cockpit , Problem