cancel
Showing results for 
Search instead for 
Did you mean: 

Database / System level copies

Former Member
0 Kudos

We currently have 2 landscapes within our solution, one supporting steady state (RD2 (Dev) --> RQ2 (Test) --> RP1 (Prod)) and one supporting a new global implemetation effort (RD1 (Dev) --> RQ1 (Test)). I know, bad idea to have 2 DEV instances, but that is what we inherited.

We are getting ready to go live with our new global implementation and will be transporting all config from the RD1 (Global Implementation DEV instance) to RP1 (Prod), afterwhich RP1 (Prod) will contain all the transports from RD2 and RD1.

Once we implement this first global population, we would like to collapse down to just one Dev instance. Any suggestions on the best way to do that since both RD1 and RD2 contain original "gold" clients and orginal config changes? Can we load all the same transports we loaded into RP1 into RD2 and have our new production landscape be RD2 --> RQ1 --> RP1 and then decommission RD1 and RQ2?

Any thoughts on how to get out of this spagetti mess with the least impact to long term steday state config/transport management would be much appreciated.

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Cherie,

We have a similar situation here. We are following the same approach. We have two parallel dev systems. What we are going to do is whatever transport goes from first dev to prod will also be moved into second Dev system and at the end of the project we will decomission the first one as we already have all the required transports in second one.

TomCenens
Active Contributor
0 Kudos

Dear Cherie

You might want to take a look at Change Request Management (CHARM in short) and Retrofit functionality (both are available in SAP Solution Manager).

Change request management can help you out, to transport requests in complex SAP system landscapes.

A setup with two lines like you describe is not uncommun and can even be useful so you should first be sure that it will not prove to be useful in the future.

Kind regards

Tom

Former Member
0 Kudos

Hello Cherie,

Would you plesae confirm below things

1.How the RD1 was built, was this the copy of RD2 and then proceed with new configs.

2.In the same roll out/project you used the 2 diff Dev servers if so, what is the transports flow you defined to PRD?

To my best knowledge, you will need to first identify the config & work bench requests from RD1 that can be moved to

to RD2, with the help of functional consultants, getting assurance that it will not impact/over write

the congiguration in RD2.

However Quality you can go for refresh from Prodcution any time and decomission one Quality.

Thanks & Regards

RajMeda

Former Member
0 Kudos

Hello Cherie,

Would you plesae confirm below things

1.How the RD1 was built, was this the copy of RD2 and then proceed with new configs.

2.In the same roll out/project you used the 2 diff Dev servers if so, what is the transports flow you defined to PRD?

To my best knowledge, you will need to first identify the config & work bench requests from RD1 that can be moved to

to RD2, with the help of functional consultants, getting assurance that it will not impact/over write

the congiguration in RD2.

However Quality you can go for refresh from Prodcution any time and decomission one Quality.

Thanks & Regards

RajMeda