Those components cannot keep their versions: CPRXRPM

[Former Member]

Hi All,

On solution Manager "SAP EHP 1 for SAP Solution Manager 7.0" when i am I trying to collect the new SP stack 25

through Maintenance Optimizer i am facing following error under step "Select OS/DB-dependent Files"

ABAP queue check failed

Those components cannot keep their versions: CPRXRPM

Regards

Gopal Gangane

[Miguel_Ariño]

Hello,

There is a new queue check for components that don't change their version in the target stack.

The error you see could be due to a component version which should not remain unchanged in the target stack, or it could be related to some 'false positives' in specific situations with this check.

Corrections are now underway for the new queue check, so the issue could probably not be solved by something you can do in your Solution Manager system. The corrections to the check are most likely going to be in place tomorrow morning CET.

Best regards,

Miguel Ariño

Edited by: Miguel Angel Arino Clarke on Oct 28, 2010 5:26 PM

[Former Member]

Hi Miguel,

i'm not sure if understand you correctly.

Is it right, that the problem exists in SAP's backend and not in the Solution Manager?

I installed the latest Solution Manager with latest Packages these days. Now I have to calculate the queue for EHP4 for a ERP 6.0 system and I'm getting the same error for BP-ERP05 (600V2).

I would be glad to hear/read from you.

Regards,

Stefan Schiele

All for One Midmarket AG

[Former Member]

Hi Miguel,

I am not able to get the following does it means that still for this solution SAP is working and by tomorrow they will release and SNOTE

"Corrections are now underway for the new queue check, so the issue could probably not be solved by something you can do in your Solution Manager system. The corrections to the check are most likely going to be in place tomorrow morning CET."

Regrads

Gopal

[Miguel_Ariño]

Hello,

You can try now. The error message should not appear any longer.

The changes were done in the SAP service backbone, no need to apply a note.

Best regards,

Miguel Ariñ

[Former Member]

HI

For this issue I have raise a OSS message to sap and they suggested the following

And it worked my case

"SAP MESSAGE

1) Implement these notes below in this sequence according with your

SP level. Implement the latest version of these notes.

SP22=> 1507354, 1415315, 1452118, 1461849 and 1485385

SP23=> 1507354, 1452118, 1461849 and 1485385

SP24=> 1507354, 1461849 and 1485385

SP25=> 1507354, 1485385

2) When you encounter any warnnings of webdynpro objects during the

implementation phase, Note Asistant leaves these 'yellow' objects

unchecked by default, please mark those warning wendynpro objects as

checked and proceed to next steps, the implemetation will end

successfully.

3) If you're having problems to download note 1415315, use this link

below to download the latest version of note 1415315 and upload it with

transaction SNOTE.

https://sapmats-de.sap-ag.de/download/download.

cgi?id=QCGKZZ8KJ0MTDH9ZVT38KNU36248L5HG8EQQMEI7XJUROWYUGC

4) Please, I ask you to apply the latest version of note 1507354. After

apply this note, create a new mopz transaction and reply the results.

If you already have the latest version of this note, please, create a

new mopz transaction from scratch and reply the results. We were having

an issue in our backend that was solved by Development Support. "

Regards

Gopal G

[Former Member]

HI

For this issue I have raise a OSS message to sap and they suggested the following

And it worked my case

"SAP MESSAGE

1) Implement these notes below in this sequence according with your

SP level. Implement the latest version of these notes.

SP22=> 1507354, 1415315, 1452118, 1461849 and 1485385

SP23=> 1507354, 1452118, 1461849 and 1485385

SP24=> 1507354, 1461849 and 1485385

SP25=> 1507354, 1485385

2) When you encounter any warnnings of webdynpro objects during the

implementation phase, Note Asistant leaves these 'yellow' objects

unchecked by default, please mark those warning wendynpro objects as

checked and proceed to next steps, the implemetation will end

successfully.

3) If you're having problems to download note 1415315, use this link

below to download the latest version of note 1415315 and upload it with

transaction SNOTE.

https://sapmats-de.sap-ag.de/download/download.

cgi?id=QCGKZZ8KJ0MTDH9ZVT38KNU36248L5HG8EQQMEI7XJUROWYUGC

4) Please, I ask you to apply the latest version of note 1507354. After

apply this note, create a new mopz transaction and reply the results.

If you already have the latest version of this note, please, create a

new mopz transaction from scratch and reply the results. We were having

an issue in our backend that was solved by Development Support. "

Regards

Gopal G

[Miguel_Ariño]

Hi there,

I assure you that nothing you did in your Solution Manager solved the issue, it was the check that was disabled in the SAP Service Backbone. I don't suppose it or read it somewhere but got the information first hand from the people who program the interface to Maintenance Optimizer in the SAP Service Backbone.

Anyway this is not that important from now on, because the issue should not appear. I say this because the issue was not a Maintenance Optimizer program error, but a consequence of a new check at the SAP side that has now been deactivated.

Best regards,

Miguel Ariñ