cancel
Showing results for 
Search instead for 
Did you mean: 

During system refresh how to manage the changes that go to quality through this Transport of Copies

Former Member
0 Kudos

We have solution manager in our landscape and changes go to quality through transport of copies.

During times of quality system refresh from production we are trying to understand how to manage the changes that go to quality through this Transport of Copies?

For released transports we will get the delta transports which went to quality but not to prod comparing the import histories and can arrive at them but how do we bring in the changes that go to quality through transport of copies ?

Another question is How do we reimport those changes sequentially along with the released transports ?


Regards,

Lovneesh

Accepted Solutions (0)

Answers (4)

Answers (4)

tabea_steiner
Explorer
0 Kudos

Dear Lovneesh,

How did you resolve your issue?!

thank oy ufor sharing!

Regards,

Tabea

former_member199290
Participant
0 Kudos

Hi Tabea:

Generally before a system copy we pull out all CHARM Incidents with Status: To Be tested (and hence have their Transport of copies in QA ). We then ask the owners to put them back to development state. Once the system is ready we ask the developers and the configurators to put them back to testing state which would then regenerate the TOCs for all those CHARM incidents. Dependencies are to be taken care by the owner of CHARM requests/incidents.

Hope this helps.

tabea_steiner
Explorer
0 Kudos

Hi Mandeep,

thank you for your comment! So, you don't import anything back into the transport Buffer of your QA?

Thanks

Tabea

former_member199290
Participant
0 Kudos

Hi Tabea:

Please note that as part of the refresh activity we make sure all the TRs which were in the system before the refresh have been re-imported before we release the system for usage.

Once the system is relased after the refresh for the team, the TOCs shall be re-imported back into the system depending upon how the owners have changed the CHARM incident status.

Please note that decision for changing the status of CHARM incident to In-DEVELOPMENT or marking a CHARM incident ready for production is taken after consultation with development team.

Important thing however is to maintain the transport dependencies in order, taking the snapshot of QA import Queue/Import history before refresh.

Thanks.

Louis-Nicolas
Participant
0 Kudos

Hi Lovneesh ,

do you find a solution since May ?

Thanks for sharing ...

Regards,

Louis

Former Member
0 Kudos

Hi,

A similar post this should help you.

https://scn.sap.com/thread/1846634

Kind Regards,

Johan

Former Member
0 Kudos

Hi Lovneesh,

You will have to make a list of all those transports which are moved to QA but not to PRD before the date of refresh as after the copy these changes will be over-written and once the refresh is over you will have to move these transports in the same sequence they were imported to QA before the refresh.

You can make use of the E070 table, with the dates in consideration to generate the list of transports.

I hope you will not be having any open  transport request in QA, in case for any reason you have it. please release the same before the refresh or the changes will be lost.

Thanks,

Manas.

Former Member
0 Kudos

Hi Manas,

Thanks for your reply.

Actually there are a lot of open requests in our system. Moreover we use Solution Manager for transports where the concept of transport of copies comes in. I would like to know that how to deal with these transport of copies generated via Charm in Solution Manager. Also looking for a way to maintain the sequence of these transport of copies.

Regards,

Lovneesh