Getting Started Newsletters Store

Products Services & Support About SCN Downloads

Industries Training & Education Partnership Developer Center
Lines of Business University Alliances Events & Webinars Innovation
Log On Join Us Hi, Guest Search the Community
Activity Communications Actions
Browse
SAP NetWeaver Application Server
Previous
post
Next
post
0 Tweet 4
Hi Experts,

I will explain the procedure for changing released TR into unrelased TR. i.e; modifiable state. There is no option given
explicitly for chaning the released TR into unreleased TR in STMS or SE01 Transactions. we have to follow the below
steps.

1. Go to SE38
2. execute the report RDDIT076


3. now, we will get the below screen which asks for TR/Tasks . give the released TR number and execute (F8)

4. Once executed, you will get the below window,
How to change released TR into Unreleased TR
Posted by Pradeep kumar in SAP NetWeaver Application Server on Sep 3, 2014 6:36:51 PM
Share 1
0 Like

5. first we need to change the task to unreleased. double click on the task number. now, click on the pencil button to
enter edit mode.then click on input help on the filed "Status"

6. change the status from "R" to "D" and save
7. now repeat the steps 5 and 6 for Transport request. finally the status column should be in "D" as shown in below.
Average User Rating
(0 ratings)
0 Tweet 4

8. now goto SE01 or SE09, type the TR number and check. it will be in modifiable state.

Cheers,
Pradeep
263 Views
Products: sap_netweaver, sap_netweaver_application_server Topics: abap Tags: sap, netweaver, sapadmin,
sap_netweaver_platf orm
Share 1
0 Like
8 Comments
Like (0)
Martin Maruskin Sep 3, 2014 8:10 PM
hi Pradeep,

When we release TR then co-file and data-file is created in operating system's file system. The files
contains physical objects that are in TR.
What will happen if I change released TR to unreleased one as per your blog and I will release it
later again? Will files be overwritten or there will be new files? If new ones what name they will have
as name as per convention will be used already by previously created files. Or will 2nd release fail?

thanks,
m./
Pradeep kumar Sep 3, 2014 10:16 PM (in response to Martin Maruskin)
Hi Martin,

Thanks a lot for your queries. Actually I forgot to add this in the blog itself. Please proceed
as follow.

Once you changed the TR into modifiable, you can change objects in the TR. you have to
again release the task and TR.However, once we changed the released TR into modifiable,
you can't release the TR again and you will be getting an error "Request <Request ID> has
the invalid attribute EXPTIMESTAMP"

you have to double click on the TR, navigate to the properties tab. enter into edit mode. you
can see "Attribute" column in the screen.
Select the row "EXPORT_TIMESTAMP" and delete that row. save and come back. now you
can release the TR. now the datafile and cofile will be overwritten in OS level with same file
name.

Like (1)
Kindly let me know, If you have any queries.
Best Regards,
Pradeep
Like (1)
Martin Maruskin Sep 3, 2014 10:25 PM (in response to Pradeep kumar)
ok thanks Predeep, this info completes the blog!
Like (1)
Nick Loy Sep 4, 2014 5:34 AM
Hi,

Options seems good, but really not able to understand why all these steps? Just we can go ahead
and make a new TR by including the objects from the transport which does same thing!



Regards,
Nick Loy
Like (0)
Pradeep kumar Sep 4, 2014 5:52 AM (in response to Nick Loy)
Hi Nick,

Thanks for your comment. Yeah these steps 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 .

Thanks,
Pradeep
Like (1)
Sudhir Sadhu Sep 4, 2014 5:53 AM (in response to Nick Loy)
Hi Nick,

Good point but I think this will be helpful during NOTE implementation or Patch up-
gradation. If the TR is released and we don't want to create another TR then we can follow
this process to make the TR modifiable.

Regards
Sudhir Sadhu
Martin Maruskin Sep 4, 2014 9:29 AM
Hi Pradeep,

one more thing: how the unrelease operation of TR would effect SOLMAN in case TR is managed by
SOLMAN? Have you tested this scenario?

cheers
Follow SCN
Site Index Contact Us SAP Help Portal
Privacy Terms of Use Legal Disclosure Copyright
Like (1)
Like (0)
Pradeep kumar Sep 4, 2014 9:37 AM (in response to Martin Maruskin)
Hi Martin,

Sorry, I have not tested the scenario as we are not using solution manager for TR
management. If possible, kindly check and update so that it will be helpful for me and other
readers too.

Thanks,
Pradeep