Central Numbering

Question

Hi all
We have CMDM scenario with central harmonised numbering where this number must be distributed to multiple downstream instances of ECC and BW in out landscape
We can achieve central numbering by configuration Key Generation on a single remote system. But we are running into a little trouble when we want to build the key mapping for all the other systems in the landscape.
For Example: On distribution we syndicate via remote ECC1 and this generates the harmonized Remote Key for that remote system. We now wish to Syndicate to the remaining remote systems ECC2, BW1 and BW2 and build the complete key mapping table with the single harmonized number for each system.  The problem is that if syndicator only u201Crecognisesu201D the remote key for ECC1 and therefore will not tag the other systems on output.
Anyone got any suggestion on this?? is there a working around in the MDM syndication where you can configure the tagging of the key to remote system even if that MDM remote system is not configured for key generation?
Or do we need to consider other alternatives?
Rgs
Con

Answer 1

Hi Con,
if you other systems with different keys also in the landscape and you don't want to have stored the key in a visible field in the repository, you can store for each target system the same  key in the key mapping. This results in different remote system entries, like ECC1, ECC2, BW1, BW2 etc.
Think also about following scenarios:
- When the mentioned systems should always have the same key, create for each system to distribute an own port but keep just one remote system for the different targets.
- Data Manager users usually want to see the key so it's sometimes useful to keep it as a unique field visible in the repository. Then you even don't need for the target systems belonging to this key a remote key at all, just take the unique field. It's not recommended when you do merging activities in the repository. For this case, the remote key is necessary.