Can two different SRM clients systems connect to one R/3 Back-end system?

[Former Member]

Hello,

Trying to developing SRM Co-Exist/Global strategy, based on the following scenario:

1. Two different SRM client systems, each at DIFFERENT SRM Version/Release Level. SRM system "A" runs in Stand-Alone and Extend Classic Scenario mode. SRM system "B" runs in Classic Scenario mode

2. Two different R/3 back-end systems, each with SAME R/3 4.7 Version/Release Level.

Question 1: Can the two (2) different SRM client systems be connected to one (1) of the R/3 back-end systems?

Question 2: Are there any Basis Plug-In (PI_BASIS) issues/difficulties to consider from either the SRM client or R/3 back-end side?

Question 3: Does each SRM client need it own unique transaction document type(s) and number range(s) definitions?

Question 4: Are there any other difficulties, for example, with RFC and Partner Profile related definitions and what are the steps to address/resolve difficulties?

Please advise and thanks in advance for your feedback!

Regards,

Ed

Edited by: Ed Shigo on Mar 16, 2009 6:40 AM

[Former Member]

Question 1: Can the two (2) different SRM client systems be connected to one (1) of the R/3 back-end systems?

They can be connected

Question 2: Are there any Basis Plug-In (PI_BASIS) issues/difficulties to consider from either the SRM client or R/3 back-end side?

Make sure that you have unique consumer entries for Middleware for Material replication, RFCs etc

Question 3: Does each SRM client need it own unique transaction document type(s) and number range(s) definitions?

Yes you need to have them.

Question 4: Are there any other difficulties, for example, with RFC and Partner Profile related definitions and what are the steps to address/resolve difficulties?

Don't see any difficulties as long as the a structured approach is followed.

[Former Member]

Hi Surya,

For Question 2, you mentioned unique "consumer" entries for Middleware for replication and RFCx, etc.

Specificallly were you referring to Table=SMOFPARSFA for middleware parrameter entries for the Consumer "Key" field definition and Tran-Id=SMOEAC for Back-end and SRM replication site RFC definitions?

Appreciate your feedback!

Regards,

Ed

[Former Member]

Apart from the table/Tcode you have mentioned create unique entries in Tables CRMCONSUM, CRMSUBTAB, CRMPAROLTP. Bottom line is that Middleware settings needs to be unique.

[Former Member]

Yes.As Surya mentioned,the source master data system remains the same but the consumer(SRM system) for the R/3 backend system will be two different SRM systems.Hence these tables in the R/3 system should have unique entries for the CONSUMER data for each of the connected SRM system.

[peter_novoth]

Hi Ed,

the scenario you are planning works within the standard, the same backend system can be contacted to several SRM systems (also different releases).

Of course you need to condider some things, e.g. what you have also mentioned is the number range, because this must be unique.

Regards,

Peter

[Former Member]

Hi Peter,

Can you provide any additional details?

Regards,

Ed