Skip to Content
author's profile photo Former Member
Former Member

Progam Changes

Hello All

I wrote a new program and tested and moved to QA. Then I there are some more changes that were requested. So, how to handle this.. Since the program is already moved and its in QA, Do I need to tranport back to DEV and make the changes and re-transport to QA and then to PROD ?

Thanks for your immediate help


Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

5 Answers

  • Best Answer
    Posted on Aug 12, 2009 at 07:21 PM

    In DEV go to change mode of your program and make corrections and save then system will ask for new transport. and then transport the new request

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member


      Your current status of the TR in which the report exist in Dev is "released".

      so when you try to change the code in DEV it will ask you a "modifiable" TR whn you save/activate the report in Dev.

      so assign a new TR to it. release the TR after doing the changes. import it in QA. your object in QA will be over written with this new change.

  • author's profile photo Former Member
    Former Member
    Posted on Aug 12, 2009 at 07:22 PM


    you have to do change at Dev and then transport req to Quality and Production.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 12, 2009 at 07:26 PM

    Hi BI,

    1) Once you transport your Program to QA, U have a copy of your program in QA as well as DEV.

    2) Now if you want to make changes , Then change the program in DEV, create a new transport request for the changes.

    3) And move this new transport request to QA.Then ur changes will also reflect in QA.



    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 13, 2009 at 01:41 AM

    if you first transport has some more elements other than the program like a standard text or table entries.. you need to make sure those are going finally into PRD, with the final copy of the program is hitting PRD.

    if its just a program you can make the changes in DEV and move the NEW DEV Tr to Q and Prd... as ordered.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 12, 2009 at 08:11 PM

    Hi BI,

    when we transport a Transport request to QA or any other server, the Developments in that transport request does not physically get transported to other server.

    if its a new development for example a report a copy of it is transported to the other server i.e QA in ur case.

    But a copy also remains at DEV server.

    so if u want to make any change in the report its already thr in PRD just u have to do it is open the report in change mode ,

    make changes and save the report with a new Transport request.


    as the Transport request in which u were earlier doing developments of the report is already moved to QA so the next time you make changes to this report , it asks for a new transport request so all the changes in the report gets saved in this TR until u transport it to QA or any other server.

    All the changes always remain thr in DEV server so dont worry just open ur DEV make changes to the report save it create a new TR and transport it to QA.


    Akash Rana

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi BI,

      Nor the transport Transport number 9233333378 nor the previous transport (9233333333) will be move to PROD .

      None of the TR would move to PROD.

      AS u said u have only transported it to QA.

      I will tell u the complete process of a TR.

      Firstly i will like to tell u about the staus of any Transport request number. * transport request could be also called TR.

      if u transport any TR from DEV to any other server in ur case we will take QA, after a successful transport its staus is set RELEASED.

      Being as the abaper we just release a TR , it is been transported to QA by a BASIS guy.

      So if u have realesed a TR for example take ur 1st case "1-st change -- Transport Number 9233333333 - Transported to QA"

      and the basis guy successfuly gets it transported to QA .

      then next if u make any other change to the same development in DEV a new TR is generated, u cannot use the previous TR as it already has a status RELEASED , lets take ur 2nd case for that " 2-nd change - Transport number 9233333378 - Transported to QA - Latest" once u release this, lets assume basis guy also transported this successfully to QA.

      Now lets take one more case now u further make some changes in the same Development in the DEV Server, and generate a TR for eg. 9233333388, and successfully release it from DEV.

      But by mistake u gave Basis guy ur first TR 9233333333 to get transported to QA so the Developments in the TR 9233333333 gets overwritten to the same developemnts ONLY in the QA server not in DEV.

      So the conclusion is we just release a TR ,Transport to QA is been done by a Basis Guy, any released TR could be transported to QA or any other server as many times u wish, DEV server always contains ur latest developments they never get change or overwritten if u transport a TR to QA or some other server .

      u always update the developments in QA or any other server by Transporting the TR to them from DEV.

      Now lets take an eg. of QA and PRD.

      for example ur QA server client is 200 and PRD client is 210.

      and a TR has to be transported to QA and PRD which is already been released by you from DEV.

      So the Basis Guy have to separately run a program on QA-200 and PRD-210 to pull the TR from DEV.

      Best Regards,

      Akash Rana

      Edited by: AKASH RANA on Aug 13, 2009 12:28 AM

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.