topic Re: Transport Request behaviour in Application Development and Automation Discussions

Transport Request behaviour

Former Member — Wed, 02 Jun 2010 10:37:20 GMT

Hi ppl,

Suppose I have a TR X which contains the creation of an object A (assume it's a custom table) and another TR Y which contains the modification to the same object A.

While moving the TRs to production, what will happen if only the TR Y is moved to production ? Will the system create the object A in production ?

Also, will there be any problems faced (other than losing the modfications done to object A) when the TR X is moved to production (TR Y is already in production) ?

Regards.

Re: Transport Request behaviour

Former Member — Wed, 02 Jun 2010 10:43:25 GMT

if your TR X is a custom table there is not way that you will be able to transport TR Y.

coz it will give a error in transport.

if this is a report and both of these modifications if you put TR Y then TR X . the changes on TR Y will be gone coz it will be over written. these kind of things can happen when you have DEV , QA , PRD where you have 2 Tr's in QA and you transport the sequence different then the new changes get overwritten by the past ones

Nafran

Re: Transport Request behaviour

Former Member — Wed, 02 Jun 2010 10:56:22 GMT

Hi,

If we consider that in TR Y:

the table maintenance generator is deleted, one of the fields of the custom table is changed and then the table maintenance generator is re-created.

Still will the TR Y not create the custom table in production (considering TR X is not in production yet) ?

Re: Transport Request behaviour

Former Member — Wed, 02 Jun 2010 11:12:10 GMT

its like this your only deleting table maintenance generator but not the table it self right,

so for e.g when you insert a line in the table the object in Y will go to production and try to insert a line on the table and when it tries to do it an error will be generated since the table will be missing.

btw why cant you send TR X first