This is a documentation on moving transports during system upgrade process / system downtime.
Let us consider an example of the landscape as below:
Consider a situation where Development system is under upgrade process or is down.
And the objects are already present in Quality.
Make the necessary changes to the objects you want to move to production and collect it in the request (In Quality).
You will have a transport request like “AQBC12345″
Now, the request AQBC12345 is local to Quality system and you will not be able to move it directly to production as it will not have target system maintained.
If you try to maintain (in SE09), it will throw the below error : Production SID is not a consolidation target.
Here we need to use transport of copies option
Go to SE09, create a new request (F6) , select the option transport of copies
Then the below pops up, here give the description of the TR and select the target system has Production “SID”. Save.
You will get a new transport of copies request created as below Eg: AQBC900292:
A new pop up appears as below, give the transport request where in you had collected the changes. ” AQBC12345 “
Make sure that AQBC12345 is already released
And now release and transport the new request AQBC900292 from STMS.
Consider a situation where Quality system is under upgrade process or is down.
Break fix transports from Sandbox System.
- First create a transport in Sandbox as in Development
- This will create a LOCAL request since Sandbox is not a delivery system in the landscape.This type of request only sets locks on the objects for tracking changes but will NOT write a transport file when being released.
- Then in Tcode SE10/SE09 create a blank/new request of type “transport of copies”.
- Follow the same steps as we did in Quality. Here Sandbox will act as Quality System.
Development –> Sandbox–>Production