Save changes in several requests

[Former Member]

       Hi all, How's it going?

                     I'm sorry to trouble you, I have this doubt. I need to save the changes of my programs in different requests.

                     Somebody know how do I get this?

                     So far, I was saving my changes in different versions but, this is in one request(going to Utilities-> Versions -> Generate Version).

I would appreciate your help in this issue,

Thanks in Advance,

Best Regards,

[RaymondGiuseppi]

At release time the transport request will try to lock the objects (see below), so usually you can only put your object in ONE workbench request (but in multiple tasks). To bypass this you can try to use a "transport of copy" request,

You can usually only release requests when all the objects they contain have been locked. This makes sure that only released object versions are exported and that inconsistent intermediate versions are not imported into other SAP Systems. Exceptions: You have administration authorization or the request is a transport of copies.

What is the actual purpose of your question ?

Regards,

Raymond

[Former Member]

Hi Raymond,

                   Thanks for your answer. With reference to your question, I try to saves my changes in

                   different requests numbers.

                   In other occasions, I have worked in Sap Systems that, when I did changes in any                    program, it asked me if I wanted save the changes in other requests number, then it allowed me

                   to create a request number.

                   This is used when differentes programmers work in the same program, but, each one saves your modifications in different requests number.

                    I would like to know how do I get that configuration? or How does it do?

Thanks in Advance,

Best regards,

[RaymondGiuseppi]

Sorry but,

it asked me if I wanted to save the changes in other requests, then it allowed me to create a request.

Those were not requests but tasks, attached to the same transport request (one header, one task per developer)

The first user who starts work on an object has to specify a change request where the work will be recorded. This locks the object so that it can only be changed by users who are working on a task within the change request.

Regards,

Raymond