Handling duplicate data records in Masterdata load

STEP 1
The monitor ‘Details’ displays error as shown in below picture when a Masterdata load fails due to duplicate data error.

Reason : Generally this error occurs when MasterData (MD) has been loaded earlier and it is in “modified” status in MasterData table. Unless we execute ‘ChangeRun’ or ‘MasterData Activation’ step, the data remains in “modified” status and is not reportable. Now our current MasterData load fails to insert the latest changes into the same table in “modified” version as the earlier records are still sitting in the table, resulting in duplicate records error.
STEP 2
Create a new session and go to Administrative Work Bench AWB (T-code: RSA1)
Then select from menu select ‘Tools’-> ‘Apply Hierarchy/Attribute Change …’ Or (Crtl+F9)

Now we will be in ‘Change Run Reporting’ window as shown below

Here click on ‘InfoObject List’ button and one of the listed InfoObject should be the MD object which pertains to our current failed load with duplicate records.
STEP 3
Now go back to the monitor screen and set the ‘Total’ status of the failed request to red (even if it’s red already!) as shown in below steps.


STEP 4
Now go to Administrative Work Bench(AWB) and from ‘InfoObjects’ screen find the failed InfoObject.
Right click on the InfoObject and select ‘Activate master data’ from the context menu as shown below

Once the MasterData activation step is complete, go back to load monitor screen of failed load. In the ‘Details’ tab here check if the failed datapacket has been loaded succesfully into PSA.

• If YES, and only a couple of Datapackets have failed with this error:

then right click on that Data Package and select ‘Manual Update’ as shown in below pic.

This action will now push the data from PSA to MasterData object.

Once this step is successful we can change the ‘Total’ status that we changed earlier to red in STEP 3, back to green.

• If there is no PSA step or failed data packets are more then:

Repeat the failed load.

These steps will complete successful MasterData load. ‘Activation’ of the data will be carried out by ‘Attribute Change Run’ in a subsequest step either in a ‘Process Chain’ or in ‘Background’ job.