Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
Showing results for 
Search instead for 
Did you mean: 

Transport Numbers

Former Member
0 Kudos

Hi all,

I have done code changes to existing one and created a new request. By mistake i have relased the request though there are still changes.

I have again created the new request and completed the changes. I think now all the changes will be under new request? If this transport is migrated to other environment, will all changes go?


Ram Sri


Former Member
0 Kudos

Hi Ram

You need not to worry at all, whatever the changes you made till the release of the last request, all will move.

thanks and regards

Mithlesh Kumar Jha

Former Member
0 Kudos

Hi jha

Thanks for your response. But my doubt is the changes i made to relased request and new request will all go in migration under latest transport numbers?

0 Kudos

Whatever the changes you made till the release of the last request, all will move along with your last request, no matter how many request before this u have created and released.

you just need to move the last released request.

0 Kudos


Depend on how this migration is done.

The requests are generally transported in order of released date not number.

So it's important that the last request you have released is the last transport.


Former Member
0 Kudos


You created transport say DEVK000001 and released it.

Now, you made changes to the same program and created transport DEVK00002.

When transporting, just make sure the DEVK000001 goes after DEVK00002 when building the transport buffers and you are safe.

That way, any changes to texts etc made in transport 1 and all the latest changes from transport 2 are transported up.



No worries about points for me, but please close this if your question is answered.

0 Kudos

When you release a request a version of program is saved in database . When you import your request to target system this version goes with it . It always better to import the requests in the order in which they were released on development system i.e. released first should be imported first and so on . This will ensure that you dont loose any change to Report source, text elements , GUI status etc .

If you are still in doubt best is to create a transport of copies with R3TR PROG <YOURPROGNAME>, release it and import in your target system . This will contain the active version of you program on development and will contain all sub objects .

After importing in target system you can always compare version ( Utilities -> Versions -> Remote Compare ) to see if your transports have moved correctly.