Same objects in different transport requests

[Former Member]

Hi all,

is it possible to check whether an object is already in an other transport request available.

The problem is when two developers work on the same source we got some problems while transporting...

How can we prevent this?

regards

[Former Member]

assign another TR for that.

[Former Member]

Hi,,,,,,

There is a transparent table for version-management "VRSD", in this table just provide the report name and will give the history of all the Requests for that report with the developer,,,,,,

Thanks

saurabh

[Former Member]

Hi,

An object cannot be attached to two requests at a time.

The object has to be released from first request; only thn it can be added

to a new transport request.

However it is always advisable to transport the released request immediately,

else it may create version problems.

As for checking, you can check in table E071, to see if the object is attached

to another request.

Hope this helps,

Raj

Edited by: Rajat Chaturvedi on Dec 8, 2008 1:55 PM

[Former Member]

Hi,

Yes you can find whether an object is in some other request ie. if its locked under some other request.

GOTO-->Object Directory Entry --->Lock Overview ====>here you will fnd the Lock details if any.

[Former Member]

SAP handles it on it's own. one object can't be part of 2 transport request at a time.

Problem occures when user1 has locked one object e.g. say a ZStructure1.

User2 is working on another report which is also using ZStructure1. Now when User2 trieds to modify ZStructure1 SAP will inform user2 that new task will be added to User1's Transport request.

Normally user should check with User1 @ when that req is going to be transported & if both changes can move togather.

check with BASIS person if some settng can stop adding task to other ppl's request.

[Former Member]

Hi,

I think the problem is that the object is not locked any more....

e.g. I change a program and transport the program only to our quality assurance system..

In the meantime another one modifies the same program in the development system (-> program is not locked anymore!!!)

The other one transport the program to productive system....

And then we run into problems because my changes are also in the productive system...

regards

[Former Member]

Hi,

Once a transport is released, the object lock is also released. Then another transport is created if there are any changes. You need to make sure that you only import the correct transport request to production.

The usual transport path is DEV> QA> PROD . Are you are exporting from from DEV to PROD directly by any chance ?

regards,

Advait

[ThomasZloch]

> e.g. I change a program and transport the program only to our quality assurance system..

> In the meantime another one modifies the same program in the development system (-> program is not locked anymore!!!)

>

> The other one transport the program to productive system....

> And then we run into problems because my changes are also in the productive system...

Yes, there can be problems when transport A, that was released after transport B, is imported into production before transport B (and A and B share same objects).

As far as I know there is no SAP delivered check for this type of conflict. You could write your own (quite complex...) or manage your development team accordingly, so that changes to the same object are well coordinated (e.g. have your developers check the version history regularly).

Thomas

[Former Member]

Hi,

thanks for your answer.

I think i write a program to check this....

regards

[Former Member]

Hi,

you can use table E071

Reg-

Raj

[Former Member]

Hi,

You can implement BADI CTS_REQUEST_CHECK.

Use methods CHECK_BEFORE_RELEASE, CHECK_BEFORE_CHANGING_OWNER for adding the validations.

Best regards,

Prashant