Regarding merge records

[Former Member]

There is an example that:

merge two records A and B to one record C, which has the same key with record A.

Will record A and B be deleted?

If it is customer master data, how to make sure my sales orders for A and B change to C, and all other tables related to A an B will be changed too?

[Former Member]

Hi Shen,

merge two records A and B to one record C, which has the same key with record A.

Will record A and B be deleted?I

When you merge records, they wouldnt be deleted.They can be referred using their local and global ids.

Its just that you will be able to view the merged view.

If it is customer master data, how to make sure my sales orders for A and B change to C, and all other tables related to A an B will be changed too?

The tables related to the sales order, wouldnt be changed just by merging of records.

You need to identify the respecitive fields of the master data which are a part of different tables , whose value you need to change from A to C or and from B to C and merge them using data manager.

Hope it helps.

Thanks,

Minaz

[Former Member]

Hi Shen,

merge two records A and B to one record C, which has the same key with record A.

Will record A and B be deleted?

- Within MDM ,Yes when you merge record A and Record B in MDM data manager,The records gets merged in to a new record so you can say that the individual records are deleted from the MDM repository to create a new merged record with global information and global Key.

If it is customer master data, how to make sure my sales orders for A and B change to C, and all other tables related to A an B will be changed too?

- Once you merge records A and B to create C,You henceforth sales order or purchase orders must be executed on this merged record on the basis of it merged gloabl key.As the MDM system has identified A and B as duplicates and given them a common global key in record C.

However thsi process will take place gradually in real time as you might have open orders on the exsiting duplicate records in the transactional system which needs to be closed slowly.

- As far as changing the data in the tables and fields in ECC may not be that feasible as record A nad record B will continue to exist in the transactional system for some time .What can be done is no need to change the local information of the individual records but rather refer to the glabal key generated from MDM for future processing.

You can also refer the below link to understand better how deduplication happens in MDM:

/people/michael.reil/blog/2006/05/18/mdm-matching-strategies-for-master-data-consolidation (matching merging in mdm)

Hope It Helped

Thanks & Regards

Simona Pinto

[former_member208981]

Hi Sheng,

After you merge the records to A and B, you cannot see them again in the records.

But conceptually they do not get deleted. The exist in the database, but you will not be able to accesss them via MDM.

Please go through the below article on Key mapping. (Finding Information of Merged Records with Help of Key Mapping)

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/7051c376-f939-2b10-7da1-c4f8f9ee...

Now as for what actions you want to take in your source system, depends on the requirement. Also it has to be done systematically, because if you are making changes to records A & B record, and there are transactions running on them, it would create errors.

So, the decision needs to be taken only after you are sure that it will not affect the transactions that are already running on these records, and future use of the A and B records should be stopped.

Hope it helps.

Thank you,

Priti

Edited by: Priti Rani Patnaik on Mar 5, 2009 9:22 AM

[Former Member]

Hi,

You can refer

Regards

Nisha