topic Re: Regarding transport request in Application Development and Automation Discussions

Regarding transport request

Former Member — Wed, 28 Jan 2009 07:27:03 GMT

Hi folks,

I have a small doubt.. can you any clarify my doubt.

I have changed one program and then released the request to quality, due to some reasons it failed.

Now i have created one more request , this time i just added some comments..Now i realeased to quality, it went fine.

Now i need to move to production, so i have asked the basis to move the new request and discard the old request..

I think it is correct always move the latest request. My doubt is the code which i wrote is in old request and in the new request only some comments are added...

if i send the new request whether all the changes are been overwritten in production?? This was my doubt..Will there be any problem.

I know its a silly question but just wanted your opinion..

Regards,

raj

Re: Regarding transport request

Former Member — Wed, 28 Jan 2009 07:30:11 GMT

ya u can release the latest one...it ll overwrite the code also...

but it is preferred dat the request is moved in the same sequence as in Quality

Re: Regarding transport request

GauthamV — Wed, 28 Jan 2009 07:33:03 GMT

yes, you can send the latest request which will effect all changes to PRD.

Re: Regarding transport request

faisalatsap — Wed, 28 Jan 2009 07:33:27 GMT

Hi, Kumar

The production program will replace by the new one which you are talking about the with comments the latest one.

KInd Regards,

Faisal

Re: Regarding transport request

Former Member — Wed, 28 Jan 2009 07:37:42 GMT

Hi,

Thanks for giving your opinions... I have given points to all of you..Once the request is moved to production and working well i will give 10 points to TT.

Regards,

Raj

Re: Regarding transport request

uwe_schieferstein — Wed, 28 Jan 2009 08:35:21 GMT

Hello Kumar

There is an obvious explanation why you should always transport even failed requests completely, i.e. also into the productive system.

Scenario:

Transport 1 fails in QAS / TST
Transport 2 is ok in QAS / TST (contains bugfix for transport 1)

=> import 1 & 2 SIMULTANEOUSLY into PRD

When you transport requests simultaneously the system internally merges the requests so that they are imported as a single one where the bug in request 1 is "suppressed" by the bugfix in request 2

If you transport only request 2 into PRD and 5 months later your basis team want to do a system copy (PRD -> TST) guess what happens. They ask what should be done with all "open" requests in TST that have not been imported into PRD. If the basis team is not careful and does not check the import log of the failed request they may just forward this request into PRD where it is likely to fail.

Regards

Uwe

Re: Regarding transport request

Former Member — Wed, 04 May 2011 12:07:12 GMT

thanks