Few Tips for Transport Request Manipulation
The purpose of transport request is to organize and move development objects from one server (say development) to other server. But sometime due to conflict in timing of different releases, we may need to move objects from one transport to other transport to release lock / dependency / to avoid transport failure due to missing object. It’s not very easy task always, especially if the Transports are complex and contain multiple components. Things get more difficult if objects are locked in one transport or the transport is partially released (few tasks are released and locked object is inside that task). These off hand tips will help developer to manipulate transport request if complex situation arises. These methods are not very advisable as this may lead to transport inconsistency if not done properly or with proper understanding of the consequences.
How to toggle the status of a Transport request?
Here is a transport request where one of the tasks is already released. Though for this example it is an empty transport. This example is valid for any transport request
Run Program RDDIT076
This report will show the details regarding the transport request.
Now double click on the task / Transport request if you want to change the status.
Click on change. Change the value of the status and save it.
As you can see, you can change any of the attribute of the transport request / task.
CAUTION: With this method, the program directly updates the necessary SAP tables.
SAP Tables for Transport Requests
E070 - Change & Transport System: Header of Requests/Tasks
E071 - Change & Transport System: Object Entries of Requests/Tasks
E071K - Change & Transport System: Key Entries of Requests/Tasks
E070T - Change & Transport System: Short Texts for Requests/Tasks
E070C - CTS: Source/Target Client of Requests/Tasks
Hi, very helpful article!
ReplyDeleteI've a question / doubt to clarify.. see if you could please help..
Scenario:
Transport (TP) is created, released and imported to the test system. CHanges though are now to be reverted / as not required to be imported to Production system.
Can I just modify the TP in the dev system and import again to the test system to bring the before status of the objects (.. so as to match all the system before changes)?
Please let me know!
Regards,
Manish
Excellent posting ...tested and works well
ReplyDeleteVery Useful and amazing post. Thank you so so so much...
ReplyDelete