why do we lock objects in a transport ?

[Former Member]

hi,

why do we lock objects in a transport in SE09 ? whats the benefit/impact ?

thks

[Former Member]

hi,

We lock objects in a request .... because if the changes within the object are not released and if the other user wants to perform the changes then he has to be notified with the transport yet to be released ... so is why the object gets locked ....

Regards,

Santosh

[ThomasZloch]

you have it with transports today, don't you?

Imagine changes to the same object would be included in different unreleased transports...how would you ever be able to move the stuff consistently through your landscape upon release?

Thomas

[Former Member]

Yes Thomas, today is my TRANSPORTS day

and btw, just to confirm about locking, I have a transport moved from old system to the new one which contains this object say a function group!!.

Now I modify this FG in the new system and include in a different transport.

Due to some reason (errors encountered during transport movement), it is decided that the old transport is going to be moved from old system to new system once again. Will this impact the object that I have modified and included in the new request in the new system ?? Is it bcos of this I am asked to lock and continue my work on that ??

hope i have not confused you

[JozsefSzikszai]

if I undeerstand right:

1. function group in old system ==> transport request created (TR1)

2. transported into new system

3. function group modified in new system ==> transport request created (TR2)

4 .if re-import the TR1 into new system ==> function group will be overwritten, all changes lost in new system

5. If TR2 was release beforeTR1 was re-imported, than TR2 still has the changes. If TR2 was not released than (currently) TR1 = TR2

[Former Member]

hi,

it is decided that the old transport is going to be moved from old system to new system once again.  

Why do you want to move the old transport again as the changes pertaining to this object is already moved .... The new transport where you have modified with changes however failed ... So it is not necessary to move any transport request and if you want to retrieve the old transport changes to that program ... you can go to version management of that program and select the transport number and press retrieve to again get back the old changes ... Hope i have answered your question ...

Regards,

Santosh

Edited by: Santosh Kumar Patha on Jul 16, 2008 9:40 PM

[ThomasZloch]

different problem. once you release a transport, the object locks are removed. you can change the object again, create a new transport and release that one as well.

Now while importing in subsequent systems you need to take care that the older transport is not being imported after the newer transport has already been imported - older and newer in respect to time of release. Otherwise you end up with a wrong, older version in the subsequent systems.

the object lock is there so that all changes to an object - while not being released - are combined within in one transport request.

Thomas

[Former Member]

Thanks ERIC, So locking has nothing to do with this in my scenario ? Locking is not going to save my work ??

So if TR1 is reimported before I release TR2 (whether it is locked or unlocked), my FG wil be overwritten, am I right ? Please confirm and we r done. thank you very much.

[Former Member]

I dont think the changes will be overwritten in the new system if TR1 is re-imported and TR2 is not yet released. I guess TR2 changes will be there as it is not released.

I doubt if this can be done. As I has not done something like this, I believe errors/warnings could occur.

[Former Member]

To maintain the consistency. otherwise there is no guarantee that object will move to other system.