ABAP transport versions out of sequence

[Former Member]

Hi,

I have been searching OSS, SDN and the web but have not found any answers.

We are in the process of applying our support packs (ECC5) and have found a couple of inconsistencies with a few of our z* abaps. The latest version for some of them appears to be missing in our QA environment

Prior to applying the support packs we did a series of client copies using SCC9, SCC5 & SCCL , as well as using a R3trans script to delete the client. Not sure how this is related but think that it is .

As an example if I look at program a Z_XXXXXXXX in our

development environment I see the following versions

DECK910732 12.12.2007 18:15:50 GAZZA

DECK910027 28.09.2007 11:06:21 GAZZA

DECK909877 14.09.2007 17:15:43 GAZZA

If I check the transport logs they appear to move through in the correct sequence from Dev to QA and into Production,

The problem is that in QA the version DECK910027 is the active version not the DECK910732 which was transported after it ?

My questions are these –

Why isn’t the correct version DECK910732 in QA

And how do we identify any other objects programs that might have the

same problem.

[Former Member]

Hi Gary,

May be in one case DECK910732 is not imported properly to your QA system?(check the logs), in another case DECK910027 is re imported and which ovver written the latest ver. DECK910732.

I suggest you to re import DECK910732 again to QA and your problem will be solved, make sure no one else is importing TP's.

Regards,

Hari.