Master / Slave ECC System - Impact on BW

[Former Member]

We have several instances of SAP and are looking at making one system the primary master data system that updates the other systems. So master data is created on the master system and it is then transferred to the slave systems. So, for example, materials will exist on both systems - same key and attributes etc.

At the moment our BW system links to all SAP instances and take master data from all SAP instances. Thinking aloud, other than duplicate data, are there any obvious issues that might arise from this scenario?

Thoughts gratefully received.

Thanks,

Joel

[Former Member]

Hi Joel,

From my understanding of master and slave there won't be any duplication. For example if table XYZ will either be in master or salve.

Thanks,

Shakthi Raj Natarajan

[Former Member]

Hi Joel,

Technically there should be any issues and this will increase the performance of your BW extract.

On what scenario do you think data will be duplicated?

Thanks,

Shakthi Raj Natarajan.

[Former Member]

Because the same master data will be on several SAP instances and we load master data from each. I guess the data could be overwritten vut in some cases source system maybe part of the key so wont overwrite.

[Former Member]

Hi Joel,

why do you want to update master data from multiple sources when the data is same? data might overlap which leads to in consistence data. to avoid this you can add Sourcesystem (ex: 0LOGSYS/0SOURSYSTEM) as an attribute of your main infoobject

[KodandaPani_KV]

Hi,

Master data always have the overwrite function and if you load multiple system it will overwirte the existing records.

let say example BW system have connected to 2 soure system mean data wil feed form the 2 source systems.

then check the tables (P table) any inconsistency and compare with the RSA in ECC side.

Thanks,

Phani.