MDG Consolidation - key Mapping update

[former_member568146]

Hello MDG experts,

I am working on a consolidation scenario for business partners on MDG 9.1

In below documentation slide 26, SAP mentions that "MDG consolidation can create the necessary key mappings for customer and supplier data by many - to - one matching, and keep them updated": https://www.sap.com/documents/2016/06/d8aa671a-797c-0010-82c7-eda71af511fa.html

However, I retrieve no documentation regarding how to automate or facilitate key mapping update through MDG Consolidation scenario. Do you have any documentation on this?

Thank you.

[former_member568146]

Any help would be much appreciated.

By the way, I see an existing adapter related to key mapping for standardization, matching and best record calculation steps but I think that would not answer my question since it is using existing data on the analysis side but, from what I understand, it is not enabling key mapping table update.

Thanks.

[michael_theis]

Hi Jean-Marie,

key mapping is always written automatically, latest at the activation of the record. There's no adapter needed.

Best regards

Michael

[former_member568146]

Thanks for the answer Michael.

From your answer, I therefore understand that we can have below case in a consolidation scenario:

1. Data load: business partners are uploaded (source system is also saved with respect to each bus. partner)
2. Match: system identify potential duplicated suppliers
3. Calculate best records/Validate: system identify potential record to be kept in MDG and this is validated by a human user
4. Activate: best records are saved/created in MDG and key mapping is updated for all the business partners that were uploaded step 1 even if the business partner is not to be created in MDG (e.g; it is duplicate suppliers)

Do you confirm that my understanding is correct?

[michael_theis]

Hi Jean-Marie,

yes, that's correct. You could even add:

5. Replicate: send updated best records back to their original source systems (based on key-mapping) to ensure that the data is updated in source systems, too.

That step is not mandatory, but it's an option to increase your data quality across systems.

Best regards

Michael