Question Re: SRM development system landscape in Spend Management Q&A

SRM development system landscape

jenny_slay — Mon, 12 Dec 2011 14:02:47 GMT

Hi,

We have installed SRM 7.0 EHP1 in a new server. I need some idea about SRM development system landscape. How many clients we need to create in new installation for configuration/development/testing. Should it be similar to our current ECC development system ?

About our current ECC landscape, We have three client in Development ECC system:

1. DEV 300 : open for ABAP development, configuration. Restricted for any document entry

2. DEV 310 : Open for end user document entry. Restricted for Configuration and ABAP development. Its link to BW and

Portal system. This used for testing of any new development.

3. DEV 320: Sandbox system. Open for configuration but restrict for cross client customization and ABAP development. Its

also restricted for tranportation. Normally functional consultent use this client for play around customization testing.

Jennifer

Re: SRM development system landscape

jenny_slay — Wed, 14 Dec 2011 08:50:19 GMT

Can you please suggest me how many client required in SRM development system.

Re: SRM development system landscape

Former Member — Tue, 03 Jan 2012 04:58:21 GMT

Hi,

It depends on the Client requirement.

what ever you have mentioned for ECC the same can be used for SRM also.

Regards

G.Ganesh Kumar

Re: SRM development system landscape

Former Member — Tue, 03 Jan 2012 06:26:45 GMT

Jennifer.

do you have a SUS requirement as well? if yes.. then you need to have one client for SRM, one client for SUS, you may or maynot not separate config client in SRM(your client requirement)..

moreover one disturbing thing is why do you have sandbox as client in dev server,..

sandbox shoud not be connected to dev in any means

Re: SRM development system landscape

jenny_slay — Tue, 17 Jan 2012 17:37:49 GMT

Thanks you all for answering.

BR,

Jennifer