topic Multiple Transports for the Same Object. in Application Development and Automation Discussions

Multiple Transports for the Same Object.

Former Member — Wed, 16 Feb 2011 21:18:10 GMT

I have ABAP program 123 and I make a change, create transport A and release the transport. I do not request transport A go to production.

I then modify ABAP program 123 again, create transport B and release the transport. I do not request transport B go to production.

Now I request transport A go to production.

Can someone explain to me why the changes in transport B are included when transport A is moved to production?

I thought each transport would be at its own change level.

Thank-you.

Re: Multiple Transports for the Same Object.

Former Member — Wed, 16 Feb 2011 21:24:56 GMT

In scenarios where both transports 'A' and 'B' are in QA, and your changes in transport 'A' is not ready for production move you should create another transport 'C' to back out changes in transport 'A' and move all transports to PRD.

Re: Multiple Transports for the Same Object.

ThomasZloch — Wed, 16 Feb 2011 21:31:49 GMT

In your scenario, the changes in B will not be included when A is imported, because A was already released (data file on the file system /usr/sap/trans/ was created) when the changes for B were applied to the same object. What makes you think they would be included? Are you sure you explained your scenario correctly?

Thomas

Re: Multiple Transports for the Same Object.

Former Member — Thu, 17 Feb 2011 00:03:56 GMT

Transport A should not have Transport B Changes ,please verify the version management using SE38 .

Re: Multiple Transports for the Same Object.

Former Member — Thu, 17 Feb 2011 13:37:32 GMT

I can guarantee all of you that when Transport A was moved, it contained changes that were made in Transport B.

Should I assume that the transport system here is not set up correctly?

I agree with you guys and I was always told it should work such that Transport A, when moved to production, would NOT have changes made in Transport B.

Re: Multiple Transports for the Same Object.

ThomasZloch — Thu, 17 Feb 2011 13:51:35 GMT

I believe you, on the other hand under standard cirumstances the CTS works as expected, otherwise there would be big problems around the SAP globe. There must be a different explanation.

The simplest one would be that the changes you expect in B were already applied to the object when A was released. Did you thoroughly compare the versions in the source system?

Thomas

Re: Multiple Transports for the Same Object.

brad_bohn — Thu, 17 Feb 2011 14:10:34 GMT


I can guarantee all of you that when Transport A was moved, it contained changes that were made in Transport B.

Surely you understand that Thomas is correct and that there's a logical reason, not related to transport layer configuration, for the issue? You CAN have multiple transports open for the same object without a lock by forcing it but check the dates as already suggested...