Data Replication from MDG HUB to Legacy System Using PI system

[Former Member]

Hello All,

Key Mapping and Value Mapping is always 1:1 from HUB to recipient system based on business system settings.

If we are replicating to PI system (which takes care of further replication), how do we handle Key & Value mapping?

Since I am using a PI system, I would be setting it as recipient system for replication, which would in turn replicate to multiple legacy systems based on certain criteria. Now how will i get the right info on which system has got which key created for future replication of same object.

In case of Value mapping, since i would be sending only 1 Idoc/SOA to PI system, how do i take care of value mapping to multiple systems?

This is a scenario based, ideally I would have preferred direct replication to the Target systems but what if PI system is involved? How should this situation be handled?

Please advise.

Thanks,

Dinesh

[Saravanan_SD]

Hi Dinesh,

Yes, Key Mapping and Value mapping are 1:1 and is based on the business system. Considering this, below are few options. ( I am not a PI expert though 🙂 ) .

1. When the data is sent from MDG system to PI, the output must have an identifier to determine the target system. Assuming MDG is sending data to system SYS1, this information need to be in the output file, so PI can identify and push it to SYS1 system.
2. MDG must place the data in file locations based on the Business systems. PI can use that as an identifier to determine the target. (This is very old practice. But still an option 🙂 ) In both cases, MDG replication will automatically take care of key and value mapping. PI need to identify the target system.
3. PI can store the key and value mapping details and use it during the Mapping with in PI to the target systems. Of course, this is not ideal scenario.

I will also wait to hear from others opinion on this topic.

Regards,

Saravanan

[Former Member]

Thanks Saravanan for the inputs.

1. I agree we can send the receiver system details or some identifier from the MDG System itself.

2. Yes this is also a good option

3.So then No key/Value mapping need to be maintained in MDG System, if PI is going to take care of this.

Having no exposure to PI is creating doubts on which approach to take. Hopefully a PI expert or MDG+PI expert can give some insights on this.