3784238 - Generated SAP asset numbers are not assigned in the same sequence as the legacy asset numbers in the migration template

• In the Migrate Your Data app, when migrating the Fixed Asset – Master Data object, the generated SAP asset numbers are not assigned in the same sequence as the legacy asset numbers in the migration template.
• Customers may expect the generated SAP asset numbers to correspond to the sequence of the legacy asset numbers maintained in the migration template.
• Example: Legacy asset numbers are entered sequentially in the migration template, but the generated SAP asset numbers are assigned in a different order after migration.

SAP S/4HANA Cloud Public Edition. 

1. Open App “Migrate your Data”.
2. Open the relevant migration project.
3. Select the Migration object “Fixed asset - Master Data”.
4. Upload the template file. 
5. Complete “Prepare.”
6. Run “Simulate.”
7. Start “Migration.”
8. Review the migration results. Observe that the generated SAP asset numbers are not assigned in the same sequence as the legacy asset numbers in the migration template.

• Fixed Asset main numbers are assigned internally by the system and cannot be manually assigned during migration.
• The asset number mapping displayed in Mapping Tasks is generated automatically after migration.
• Therefore, the generated SAP asset number sequence is not guaranteed to follow the sequence of the legacy asset numbers in the migration template.

1. During migration, the Migration Cockpit may split the uploaded migration data into multiple access plans and process them using parallel jobs. As described in KBA 3291930, records are therefore not guaranteed to be processed in the same sequence as they appear in the migration template.
2. The Fixed Asset number range object ANLAGENNR uses parallel buffering. As described in KBA 1843002, chronological number assignment is not guaranteed.
3. After migration, verify the relationship between the legacy asset numbers and the generated SAP asset numbers using:
   • Mapping Tasks in the migration project.
   • Manage Fixed Assets (Legacy Asset Number field).

• KBA 3016328 - Numbering sequence is not the same as the sequence in migration template.
• KBA 3291930 - Migration Cockpit parallel processing and access plans.
• KBA 1843002 - Gaps and jumps in number range assignment.
• Fixed asset - Master data | SAP Help Portal 

Migration cockpit, fixed asset master data, non-sequential numbering, internal number assignment, number range, parallel buffering, access plans, mapping task, legacy asset number, sequence mismatch, asset class, s/4hana cloud public.  , KBA , CA-GTF-MIG , SAP S/4HANA Data Migration Cockpit Content , FI-FIO-AA-MD-2CL , Fiori Apps for Asset Master Data (Public Cloud) , Problem