Change Request & Task Issue

[Former Member]

Hi Experts,

Please help me out for following concern.

Changes done(In Z program) for some testing purpose, are saved in test CR.

Now i want to save changes doin again in New CR, for further transport.But whenever i am goin to change it ,its taking either the same test CR or creating new Task in same CR. But not askin for new CR.

Some1 concerned that i have to release that CR ,then only i can do that,but i cant do it ,as it is test CR.

Please suggest solution.

Thanks in advance.

Thanks and Regards

Deepak

[dhorions]

If you open your program in se80, right click the program name and choose 'Other Functions', then choose 'Write transport Entry', you can add it to a new CR.

Then , in SE10, you can open your previous (test) CR (by doubleclicking it) and then click on the edit-pencil, you can then remove everything you want removed from the request.

[gopi_narendra]

Hi Deepak,

If you do not want to transport the current request you can delete it by deleting all the entries from the task and then the request can be deleted.

Then next time when you save your program you wil be prompted for a request where you can create a new request and save the new changes under it.

hope this is clear.

Regards

Gopi

[Former Member]

Hi,

If u want to store the new changes under the new tp then u have to release the old

tp, then only it will ask for new tp file for saving the program.

other wise all the latest changes u have done are stored in the oldest tp.

reward points if it is helpful.

Regards,

Satish.

[Former Member]

A Change request that is not released consists of an abject list that has details of the objects (programs, etc) that are to be transported in the request. While it is not released, it does not contain any of the details of the objects, just their object keys. These details are in individual tasks by user id.

When you release the change request, the system takes a copy of the current version of all the objects and writes it to two files in the transport directory of the SAP server - one control file and one data file. These files are named based on the request number.

<b>If you make further changes to a program before releasing the request, those changes will be included in that request when it is released.</b>

If you have made changes to a program that have been put into a change request that is not to be transported you need to manually move the relevant object list entries to the new transport request. You cannot simply delete them from the first request and then save changes to the program again as the object list entries may not be the same. Releasing the change request is not a solution as this may have the same result - the entries added to the new request may be incomplete.

For example, if you create a program it is added to a request as R3TR PROG containing program, texts, gui etc, but if you later change it and save it is added to request as LIMU REPS for program or LIMU REPT for texts or LIMU CUAD for gui.

To move manually, copy/paste values from SU10 object list of the task to a new request/task. Once 100% sure it is OK in new request, delete line from old task then lock object in new request (select line and use padlock icon). For customising there may be object keys associated with the line that you also need to copy. Take care to ensure all relevant objects are in the new transport.

Andrew

[Former Member]

Thanks Experts for your kind replies