System copy for QAS

[Former Member]

We are Go Live before 2 years.

Our SAP Landscape is Development->Quality->Production.

Now we want to refresh Quality server thru system copy.

So we can have same data, config and abap development as our Production. So it very useful in testing.

At present there are many abap developments which are not transfer to production due to some reasons.

So we are facing problem during testing as Production and Quality abap developments are different in some cases.

Is is advisable to re-fresh quality with production thru system copy?

Request you all to please share your experience.

Regards,

-dt

[former_member188883]

Hi,

You can prepare a list of developments which are not transported to production and exists in QAS.

Later you do system copy from production to QAS. Transport the required developments to QAS for testing.

Regards,

Deepak Kori

[Former Member]

Hi,

Thanks for you inputs.

So I will prepare a list of developments are under testing and not transported to production.

after system copy I need to import transport requests of the same in Quality.

Those development which not required to transport in production, that request no need to transport in quality. As I have mention in my post that there are certain old developments which are not transported in production and no need to transport in future also.

This is my first experience on SAP. Is it advisable to refresh quality server. In companies what standard practice follow after go live.

Regards,

-dt

[Former Member]

Hi,

This quite normal, requirement, which we do based on client / project requirements. Before starting the quality system refresh, try to export, the following, like RFCs, IDOC partners, IDOC ports, printers, model views, and most import, user master.

After your logical system conversions are done, import them back again to quality.

Prepare list of TRs, that need to be imported to QA, back after system refresh and confirm the sequence with the ABAP team and import them.

Do, schedule online backup, before importing the TRs, so that you can restore back to this stable state, in case of any issues, post deployment of TRs.

~hope this info helps!

Rajesh