Re: Transport order to production system

Stan, were you really never curious to look in the transport itself and in the version control screen in ABAP Editor? It really doesn't take a lot to understand how the transports work...

You have not told us what exactly are the changes in the program, but let's assume that the program version in TR1 already included a reference to the custom table in TR3. When TR1 is moved to Production (wouldn't you move it to QA first? but more on this below) what do you think would happen? TR3 with the table is not there yet, so take a guess. Bingo - you'd get a syntax error. However, after you move TR2..4 your program will likely be OK because TR1 version will just be overwritten by the subsequent transports and the table will arrive too. (Not sure what's in TR4 and whether TR3 will trigger program generation, but in the worst case you'd just need to generate a program to fix it.)

So it is quite important to follow the right transport sequence when importing. There are many posts on SCN on this subject. For this reason it might be a better idea to keep the relevant objects in the same transport. Even if different people are working on this they can just add a task to the same transport.

Also try to avoid releasing the transports (which usually causes such situations) until the last minute. For example, we started using a transport of copies (Google it) to move changes to QA system and it significantly reduced the number of transports going to PRD. Now in most cases it's just 1 transport instead of 4-5 before.

And, as I've mentioned, there should be QA system in the middle. Do not be afraid to try things in that system even if you fail. If you've simply moved the transports there you would've seen by yourself and learned much more than said here. Also make sure to befriend a local Basis admin, they are chockful of the transport information.