4-system landscape

[Former Member]

Hi,

We have a scenario were we might need to have 4-system landscape, need advise:

We currently have 3-system landscape DEV/QAS/PRD (ERP 6.0/Linux/Oracle).

There is a new major develpemnt project comming our way and need to know how to plan our system landscape for the development and testing environment. The new project might last 6 months and during this developement phase there is major master data changes/configuration. During this phase how do we make sure the current production support is carried out effectively ? since the new developement/testing would have changed the data/configuration in our DEV and QAS box.

Is it possible to have 2 different development system ? in the landscape ?

Also is it possible to have 2 different Quality systems for 2 groups of developers ?

If so how would it fix into out current landscape ?

Or is there an alternative way to achieve this ?

Thanks

[Former Member]

Hi,

A multiple system landscape (2 Dev, 2 Qas & 1 Prd ) is really helpfull when you do any new development / integration testing. It also prevent your current landscape (Dev, Qas) untouched without any new development you also make sure that when the new changes comes to your old PRD before that you have to build a R - reference system. when every thing goes smooth you should make your transport route like:

DEV (N) => DEV (O) => QAS (O) => PRD

|

QAS (N) => QAS (O) => PRD

OR

DEV (N) => QAS (N) => PRD

Regards;

[Former Member]

Hi Baigsa,

Thanks for your reply and valuble suggestion.

This is what I am thinking of doing

Before golive

DEV->QAS->PRD - this remains as it is for (BAU) business as usual transports. And a new landscape consisting of DE2 and QA2 is setup from copies of DEV and QAS rescpectively.

Any transport released from DEV for BAU is also applied to DE2 and QA2.

DEV->DE2->QA2

During Go-Live all transports created in DE2 and which has passed testing in QA2 are moved to PRD.

After go-live the DE2 and QA2 becomes the main development and quality systems

DE2->QA2->PRD.

Is this a suggested approach according to your suggestion ?

Am I missing somthing here

Thanks

[Former Member]

Any transport released from DEV for BAU is also applied to DE2 and QA2.
DEV->DE2->QA2

In case every transport released from DEV will go PRD then this should work. But what if a transport is released from Dev and is not imported in to QAS .

We have similar setup but for a different reason and we import transports into Dev2 when they have been imported to QAS. So in PRD and Dev2 they move at the sametime.

Again if every transport released out of Dev will go to QAS then it should work.

Hope this helps.

Thanks,

Naveed

[Former Member]

Is this will be your first & last new development work, what I mean by If this activity you are doing let called it "New Product Development & Integration" .. what if your company needs with some new development & integration with other new products from SAP and want to deploy at you current landscape ? do you want to set it again ?

I don't know how big your company is but if it's growing then you'll need this Landscape forever... where every new developments will begin with DE2 and QA2 to PRD then DEV & QAS.

Regards;

[Former Member]

try transport groups

[Former Member]

Hi,

Thanks for your reply, could you please elaborate ?

Thanks