cancel
Showing results for 
Search instead for 
Did you mean: 

MDM MASTER DATA LOAD - remote key missing issue

Former Member
0 Kudos

We have a multi-system of entry scenario for master data. ECC, legacy system for system of master data entry. "Vendor" is loaded through legacy system to MDM and remote system/remote key is added for legacy system when data arrives from legacy system. legacy created data is also syndicated to ECC.

When a Vendor is created in ECC with an "alternate payee" relationship to a vendor created in legacy and when this ECC created vendor flows to MDM, MDM is not able to do the mapping to alternate payee vendor as there 'ECC' remote system/remote key for this vendor and MDM load fails with value exception.

How to handle this situation? One solution is as and when legacy data flows to ECC from legacy system through system, a reverse syndication should be done from ECC to MDM so a 'ECC' remote system entry is automatically created.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Subin,

If you have scenario that all the vendors which are created from Legacy to MDM are also sent to ECC, then you can either simply paste the same file in FTP folders for ECC remote system. It will automatically add ECC remote keys as well.

It is more or less same as you have suggested like reverse syndication to MDM system. This will be done by PI system and will place the file in MDM system. I would prefer first option as it will ensure that correct/same schema is used for import because sometimes, we have different syndication schema than general import schema.

Another option you can try is by Setting Qualified Range for ECC remote system. You can select appropriate lookup table(e.g. Account Groups) and set Number ranges as per every account group. These number ranges would generally be Vendor Numbers only. So this will generate Remote Key upon syndication only, so it will automatically generate remote keys for ECC remote system when data is syndicated to ECC.

But one concern here is that since Vendor numbers will already be there, so there might be a mismatch of vendor number and remote key generation at the time of syndication. You would need to test this scenario thoroughly so that you do not face any problems in future. Please let me know your thoughts.

Thanks and Regards,

Ankush Bhardwaj

Answers (0)