Single SRM instance with multiple ECC backend

[Former Member]

Guys,

Wondering if you know any of the SAP's clients that have implemented single SRM instance with multiple ECC backend?

My company, Verizon is looking at going with that option and we would like to know if anyone has alreday implemented that model. If so, we would like to get an idea of the challenges involved.

Thank you,

Seyed

[Former Member]

Hi,

I know for sure of companies under the referred landscape. They have a global SRM system and mutliple R/3 back ends with another HRMS system. On top of that they have both classic and extended classic deployment in SRM.

The challenges you may face:

01) Middleware replication for basis objects, product categories

02) Country specific customizings

03) HR replication (would be tricky if there is a separate HR system) and a global Org structure and the attributes maintanance. I do not think the HR org structure would really support you for the root level attributes maintanance.

04) Work flow template requirements.

05) Vendor replications

06) Exchange rates, curreincies... all would have to be in sync.

We have implemented this and there are lessons learnt also especially when the HR data is replicated from a separate system. I am sure in your case of multiple R/3 back ends, neither of the systems would have the HR data.

Hope these pointers will help.

DV

[Former Member]

indeed they are pain points Rao . very good.

master data synchronisation are very challenges across all the systems.

Muthu

[Former Member]

The main challenge will be if anyone of the backend system is shutdown the srm doesn't work for the particular group of users. Refresh of the quality system is also challenging you need to take backup of all the system at the sametime.

Data visibility also important. User should not be able to see the documents belonging to other backend system. Roles should not have any open value like * in the purchase organisation or purchasing group. I have worked with one srm and three backend. Catalogue URL switch also a big challenge.