How to Reload the Records (Without Duplication) You already Transferred/Loaded in Target System

[former_member5846]

Project Nature - SAP S/4HANA Migration

Scenario - Where an incorrect field value has been loaded, the record is created in S/4HANA but needs to be re-loaded with the corrected value. Duplicate entries get created.

Please consider that we have inter-dependent data objects in the SAP S/4HANA Migration project.

- How do we reload the data without duplicating it?

- Is there any solution available which can be used in SAP Data Migration Project.

For your information - Data Load Tools/Routines are using

1. SAP Migration Cockpit

2. SAP LSMW

3. SAP Customize ABAP Program

[Marissa]

Hi,

Tag SAP S/4HANA Cloud Data Migration is for S4HC essesial edition. Since you metioned LSMW, I revmoved this tag.

Thanks and regards,

Marissa

[vijy_mukunthan]

Hi Shamik

Those objects which ever has internal number range. Those will generate duplicate entries. For those cases you need to have a validation in LTMOM.

For ex. If the equipment is already exist check and validate with ABAP code to skip those entries. Other wise yes of course duplicate entry will be created. It is exactly like how in LSMW check the equipment from table and if it exist skip record will be used same approach in LTMOM this logic has to be in place to avoid duplicate creation.

This logic should be place which ever object you have the trouble.

BOM validation not required since the migration cockpit by itself it will validate. All other objects need to check and validate.

We are also in S/4 hana 2021 version. LTMC will not work. You have work with migrate your data app for your migration activity.

Thanks and Regards

Vijay

[former_member5846]

Thanks for your response Vijay.

My topic was - 'where an incorrect field item/input has been loaded, so the record is created but needs to be re-loaded with the corrected value.' - Looking for a solution without refresh the system.

FYI - We have two target systems -

1. S/4HANA ON-PRIMISE 2021

2. SAP Cloud for Real Estate (Public Cloud)

Records are duplicated in the aforementioned situation due to the internal number range. As is well known, the Migration Cockpit has validation steps, but what would happen if we wanted to update the records using the same primary key value that has previously been loaded?

Warm Regards,

Shamik