Skip to Content
Technical Articles
Author's profile photo Arijit Dutta

How to change released TR into Unreleased TR

Introduction:

This blog post will describe in detail how to change released TR into Unreleased TR

 

In this blog post, we will take the example to change released TR into Unreleased one.

 

Requirement:

Change released TR into Unreleased TR using SE09 Transaction Code

Transaciton Code: SE09 – modifiable

Release Request – Now the request is as released status and now we want to change the status

 

Steps to be followed:

  1. Execute the program RDDIT076 and give the request number which you want to change the status and execute.

2. Two rows are available in the request overview. 1.Workbench Request type ‘K’ and 2. Development/Correction type ‘S’

 

 

3. Double click on row of Workbench Request and click on pencil icon change and change the status from R (Released) to D (Modifiable). Click Save

 

Next: Double click on Development request and change the status from R to D

4. Tcode: SE01 to check the status of TR from Released to Modifiable and now we can change in the program

Assigned Tags

      8 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Lars Hvam
      Lars Hvam

      Thanks, can you add a few comments on when this is needed and/or allowed? From a customer perspective I would not be very happy if a developer used this functionality.

      Author's profile photo Arijit Dutta
      Arijit Dutta
      Blog Post Author

      Lars,

      If developer released TR or task by mistaken but they don't want to create multiple TRs for one development otherwise it is better to create new TR with same objects.

      Author's profile photo Georgi Slavov
      Georgi Slavov

      Also from the developer's perspective - since ABAP in general misses a remote repo, also the whole workflow and governance processes like re-base-ing, etc. TRs do not get really 'versioned', the closest to this is probably the transport of copies(and test import)... So in which cases are these steps recommended over a regular follow-up transport(or transport of copies for that matter) .

      Author's profile photo Arijit Dutta
      Arijit Dutta
      Blog Post Author

      Georgi,

      These steps are only helpful if developer released TR or task by mistaken but they don't want to create multiple TRs for one development otherwise it is better to create new TR with same objects.

      -Cheers

      Author's profile photo Sandra Rossi
      Sandra Rossi

      Be careful, before posting a blog post, to search the same if it already exists:

      How to change released TR into Unreleased TR site:sap.com

      Surprisingly, your blog post comes only in third position, after others presenting RDDIT076 also:

      • https://blogs.sap.com/2014/09/03/how-to-change-released-tr-into-unreleased-tr/
      • https://blogs.sap.com/2016/01/06/change-released-task-to-unreleased-modifiable/

      And right after, there's another one about RDDIT076 again, plus a more general post:

      • https://blogs.sap.com/2014/01/06/how-to-change-transport-request-from-released-to-modifiable/
      • https://blogs.sap.com/2016/02/17/all-about-transport-request/

      So, your blog post is the 4th one fully dedicated to RDDIT076,

      Author's profile photo Jelena Perfiljeva
      Jelena Perfiljeva

      And there are important comments in those other blogs: to release this "transport zombie" afterwards, some attribute manipulations are needed.

      I really would not recommend this option. Use transports of copies to move stuff to QA. Released by mistake? Just create a new one.

      Author's profile photo Santhosh MB
      Santhosh MB

      Looks like, After installing SAP security note 3097887 – [CVE-2021-38178] Improper Authorization in SAP NetWeaver AS ABAP and ABAP Platform https://launchpad.support.sap.com/#/notes/3097887 you cannot use this trick anymore: the note deactivates this report RDDIT076.

      Author's profile photo Santhosh MB
      Santhosh MB

      This will not work for latest releases and if you implement SAP Security Note 3097887