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]

In Deploying to our second backend, we ran into pain points in the following areas:

- Vendor Replication (duplicate vendors in both system got different BP in SRM, hence users in backend 2 were confused as to which vendor or bp number to use).

- Product Category replication - Some customizations did not take into account global product category would be duplicated in SRM, one for each backend. In general, anywhere you could have duplicates across backends is an area to pay extra attention to: Plants, PORGS/PGRPS, etc

- Exchange Rate & Currency: SRM always overwrites so basically the last system to replicate from wins. Since Europe was more used to managing exchange rates, they had the added task of maintaining US rates with Mex, CAD etc in their backend. You will need to pick one master backend for currency & exchange rate replication.

PO Document Numbers - Since the source of PO's is SRM, the PO's will be sequential, but when replicated to R/3 there will be gaps. Backend #1 might get PO 1000, backend #2 might get 1002 & 1003 etc. Our business was initially concerned about the "waste" but the added cost of customizing number range for each backend was prohibitive, plus there was a desire to standardize on global number ranges for different doc types.