transporting change request's

[Former Member]

Hi,

a developer has changed a include. Also he has saved the changes in a change request (e.g. XA1817). Few days later I have also changed some lines on the same source code as my colleague and I have saved it on another change request (XA1819).

Now what happens if I transport my change request (XA1819) before transporting the change request from my colleague (XA1819) in productive system?

Thanks

Michael

[Former Member]

Hi,

a developer has changed a include. Also he has saved the changes in a change request (e.g. XA1817). Few days later I have also changed some lines on the same source code as my colleague and I have saved it on another change request (XA1819).

Now what happens if I transport my change request (XA1819) before transporting the change request from my colleague (XA1819) in productive system?

Thanks

Michael

[RichHeilman]

If the change request was not released, the system should not have allowed you to change the object without putting a change request underneath the request of the other users. Check your colleagues transport request, your request should be apart of it. Then can be released and the changes will move under one transport.

If you see the same object under two different transport requests which are both not released and not tied to each other, then you have a real problem.

I assume that you transport request is tied to your colleagues, check SE10.

Regards,

Rich Heilman

[Former Member]

Hi,

the situation is:

The CR (e.g. XA1817) from my colleague is released and transported to quality system, but not in productive system ( 3 systems architecture (dev./qual./prod.).

My CR (e.g. XA1819) is not released and not transported.

If I release and tranpsport change request XA1819 in quality and then in prod. system, whats happen?

Thanks

Michael

[Former Member]

Hi Michacel,

If you move your transport request XA189 to Production then the changes of urs and your colleague both will move to Production.

Thanks,

Vinay

[Former Member]

The order in which the transports are moved to Production system matter. So, if you belive your changes include the changes made by your collegue, make sure your transport is the last transport to be moved!

[raja_thangamani]

Only your changes will go to production.

Raja T

[RichHeilman]

<i>Now what happens if I transport my change request (XA1819) before transporting the change request from my colleague (XA1819) in productive system?</i>

To answer this question, your changes would be overridden when the other transport is transported, but again, this should not happen. The system should not allow you to change an object and tie it to a totally different transport heirarchy, it should tie directly to the other transport where the object was modified.

Regards,

RIch Heilman

[Former Member]

It is advisiable to transport all CRs in numerical order, with the latest CR being the active version in the Production system.

But, if you fail to tranport a lower order CR, you are not at fault! But make sure with your colleague not to move his CR to production system after you have moved yours... this will overwrite your version with his.

Hope this helps you.