Can we do value mapping through MDG Consolidation ?

[titu4mdg]

Hi Experts,

We are doing vendor initial load through MDG consolidation from ECC source system to MDG Hub on S/4 HANA target system. Here the vendor account groups are changing in the target system (example: from ACGRP1 to ACGRP2)

Can anyone tell me if we can do this value mapping for a vendor from ACGRP1(ECC) to ACGRP2(S/4) while doing dataload through Consolidation process in MDG? 

Thanks in advance!! T

[Saravanan_SD · Accepted solution]

Hello T,

1. This particular adapter will utilise the value mapping already maintained in the system for the mapping. If value mapping is maintained between source system and consolidating system, the adapter will map the values else the inbound value will be considered.

2. Both options has its advantage and value addition.
If using ETL tool like BODS, it will be simpler in sense of value mapping where you can review the data pre and post conversion of values. But the value mapping has to be maintained in BODS for ETL purpose and same values to be maintained in MDG for MDG replication.
If using MDG consolidation for value mapping, all changes need to be visualized in the consolidation FIORI App. Performance and sizing need to be considered for better processing. But value mapping is maintained only in MDG system.

Regards,

Saravanan

[titu4mdg · Accepted solution]

Hi Saravanan,

Thanks again. If I have understood your reply correctly, kindly confirm my inline comments below:

1. This particular adapter will utilise the value mapping already maintained in the system for the mapping. If value mapping is maintained between source system and consolidating system, the adapter will map the values else the inbound value will be considered. - so does it mean that, the custom code implemented in the Adapter class does not write any value mapping entries into MDG, it only reads the value mapping maintained in MDG? I am just trying to understand this part correctly. Also kindly clarify what you meant by "else the inbound value will be considered". what inbound value are you refering to?

2. Both options has its advantage and value addition.
If using ETL tool like BODS, it will be simpler in sense of value mapping where you can review the data pre and post conversion of values. But the value mapping has to be maintained in BODS for ETL purpose and same values to be maintained in MDG for MDG replication. -  are you saying, apart from maintaining the value mapping entries in BODS, we also have to maintain the same manually in MDG? or we can just upload the value mapping file into MDG that can be generated from BODS ater the data is laoded?
If using MDG consolidation for value mapping, all changes need to be visualized in the consolidation FIORI App. Performance and sizing need to be considered for better processing. But value mapping is maintained only in MDG system. - here we have around 200K vendors that are being loaded into MDG from 3 source systems. But the value mapping(conversions) would be hardly for 10-15 attributes in vendor master. Do you still see any issue here if we do through adapter class for this small number of mapping entries?   

Looking forward to your response.

Regards, T

[Saravanan_SD · Accepted solution]

Hello T,

1. Yes, this is SAP delivered standard adapter for value mapping which reads already maintained mapping data in MDG system. If no value is maintained, the value uploaded for consolidation process will be considered as is. i.e., if account group is ACCGRP1 and if no mapping is maintained, it will consider the value ACCGRP1. 

2. Once the value mapping is maintained in MDG, it will be considered for both inbound (when using the correct adapters) and replication from MDG to other systems. i.e., if value mapping is not in MDG for account group ACCGRP1, then during replication, same value will be considered.  

Including value mapping steps is one of the criteria to be considered for performance related consideration in CMP process. Exact system performance can be ascertained on individual system based on your load testing. 

Regards,
Saravanan

[Saravanan_SD]

Hello T,

Yes, we have specific adapters to use for different scenarios. Adapter - 'CL_MDC_ADAPTER_BP_VALUEMAP_STD' is if you would like to consider value mapping. 

Please find below link for more details on the available adapters. 

https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/6d52de87aa0d4fb6a90924720a5b0549/a3bd115449e7bb29e10...

Regards,
Saravanan

[titu4mdg]

Hi Saravanan,

Thanks so much for your valuable input. Now I have 2 follow-up questions which are as follows:

1) Will the value mapping done by this Adapter - 'CL_MDC_ADAPTER_BP_VALUEMAP_STD' get saved in the Value Mapping table in MDG in the backend just like the way they get saved when maintained through "Maintain value mapping" node?

2) We have 3 source ECC systems from where we are loading this vendor master data into our MDG Hub on S/4 HANA. We are planning to extract data from the source systems via BODS and then through consolidation process the final load would be done into MDG. In this scenario, would you recommend the value mapping to be done by the Consolidation process(adapter class) or the value mapping should be done in the transformation step in BODS before it hands over the data to the Consolidation process ? Just trying to understand which one will have advantages over other.

It would be great if I get the answer.

Thanks, T