1 of 1 people found this helpful
Hi Ramya, may I ask why you want to have the extra step of bringing it all into one? Couldn't you do the same per catalog instead?
A merge from one supplier catalog into another is not possible. :-(
These catalogs are internal systems where product data exists. Some of the attributes are common across all of these catalogs and we want to ensure they are all consistently represented. So, if attribute1 is in catalogs 1,2,3.. we want to check if its same across all attributes. We were planning to run DQ rules to do that, but we are not sure if we can pass attributes from different catalogs to the same rule. Hope this helps! Any suggestions would be greatly appreciated.
a little bit, yes. Can you explain a bit more what you mean by
"if attribute1 is in catalogs 1,2,3.. we want to check if its same across all attributes"?
Maybe make up a real world example making sure we do not talk different things?
Other than that and not sure if helpful but quick thoughts reading your reply for potential alternatives:
1. Have all internal systems using the same Supplier Catalog?
2. Or merging the data into the master and doing the cleansing exercise in there?
I had a similar case in the past, with the need to check many supplier catalogs at the same time in order to build the final master record. You can find more info here Merging from The Elder: Informatica PIM multi-merge
I have developed the functionality using PIM SDK, since multi merge from many suppliers catalog into master one is not supported, and as Stefan has said, merging into a supplier catalog is not supported.