16/09/2013: As mentioned by Julius in the comments, this blog post (orig 2011) is kinda silly :smile: . The reason mentioned below is not a valid reason to "unrelease a transport request". The blog post does demonstrate how system administrators can get creative in order to change something to their benefit or in order to fix a "stuck" situation. I'm planning on writing a follow-up blog post on the topic / comments in general. You basically shouldn't take this kind of action without a valid reason and I cannot come up with a situation directly where you have a valid reason.
CAUTION: Note that unreleasing a \ transport request is not recommended \ unless you have sufficient knowledge on TMS.
CAUTION: Note that editing table content \ can be dangerous and you can mess up your system if you start editing tables \ without enough knowledge and insight on the table content and table \ relationships.
A possible use case is a situation where a transport request \ release was started where the transport content is by mistake incorrect. For \ example someone wanted to export a table definition but gave in the wrong ABAP \ dictionary element and ends up exporting the table content instead. Exporting \ table content of large tables takes time and creates large transport requests. \ The user notices that the release of the transport request takes abnormally \ long and notifies a #sapadmin to check out the situation.
After the situation is explained the #sapadmin is aware of \ the mistake of the user and action has to be taken. The export of the table \ content can be cancelled by killing the process on OS level. This will cancel \ the transport release and the transport release will be in status cancelled. Now let’s take a look how you can unreleased \ that transport request so the content can be corrected.

List table E070 in transaction SE16 (press F7 after filling in the table name)

Fill in the transport request (notice <SID> is hidden here because of sensitive content) – if SID = AA1 request here would be AA1K900625.Press execute

Double-click the TRKORR value entry

You can now see the entry for your transport request in table E070
Now you have some options but in the end you have to change the value of field TRSTATUS to set the transport request in an unreleased status.

Enter /h and press enter twice in the command line to go into the coding in debug mode

Scroll down in the code until you reach the code = ’SHOW’ line(notice the other available CODE values: EDIT,INSR,ANVO (edit including keys) an DELE)
Double-click code in the program code

This will add variable CODE into the right pane of your debug window
Click on the pencil to the right to change the value of Variable CODE

Change the value into EDIT and press the enter key
Press F8 once done

Change the TRSTATUS field value (press F4 for input help while the cursor is in the field)

End-result my transport request is modifiable again
You can then either add the missing entries, change an incorrect entry or delete the transport request all together.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 3143 | |
| 1916 | |
| 1916 | |
| 1213 | |
| 1079 | |
| 757 | |
| 755 | |
| 742 |