Empty Target Stack on Mopz

[Former Member]

Hi...

we try to implement SP25 on our Solman....

In Mopz-step 'Choose Stack' we get an empty field...

In Log we can find the message 'Stacks of Product Version SAP SOLUTION MANAGER 7.0 EHP 1 do not include NW Stack 05 (09/2009)'

Source-Stack is 23, NW is on 5

somebody have a suggestion ?

best regards

Christoph

[Miguel_Ariño]

Hello,

You may safely ignore the ''Stacks of Product Version SAP SOLUTION MANAGER 7.0 EHP 1 do not include NW Stack 05 ' kind of error messages, but it is not normal that the target stack shows empty. I have never seen that with Maintenance Optimizer SP23 or higher, for product Solution Manager.

Perhaps you can check out the http://service.sap.com/sp-stacks application and download the stack delta from there , for a workaround .

Best regards,

Miguel Ariñ

[Former Member]

Thank you for the info about workaround...

We will try, if we can't find a solution for the empty-field-problem

other suggestions ?

best regards

Christoph

[Miguel_Ariño]

Hello,

Sorry, not really. Without screenshots or a look into your Solution Manager system I am not able to recommend anything...

Best regards,

Miguel Ariñ

[Former Member]

No problem....

Do someone know, where the Mopz is getting the SOURCE-Stack-Version ?

Out of the SMSY ?

Look at this screenies:

[Java-Components|http://www.christoph-bastian.de/sap/java.jpg]

[Abap-Components|http://www.christoph-bastian.de/sap/abap.jpg]

[Empty-Field|http://www.christoph-bastian.de/sap/field.jpg]

[Miguel_Ariño]

Hello,

The only things that come to mind are:

- What are the authorizations of the S user in the marketplace?

- Are all the correction notes for SP22 applied?

- In SCPR20, are the Solution Manager BC sets activated in exactly this order?

SOLMAN40_MOPZ_TTYP_SLMO_000

SOLMAN40_MOPZ_001

SOLMAN40_MOPZ_SP18

- Does this happen for other systems / product versions?

- Does this happen for all users?

Best regards,

Miguel Ariñ

[Former Member]

- What are the authorizations of the S user in the marketplace?

They must be the right ones, because in the testsystem (same config) it works...

- Are all the correction notes for SP22 applied?

I will check this...

- In SCPR20, are the Solution Manager BC sets activated in exactly this order?

YES

- Does this happen for other systems / product versions?

NO

- Does this happen for all users?

YES

Thank you for help...

[Former Member]

We've opened a ticket and are in contact with you on this way....

thank you

best regards

Christoph

[Former Member]

Hi

Please check the sap note [Note 1485385 - MOpz: Collective corrections 25|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=0001485385]

Jansi

[Former Member]

Hello.

Any new info on how to resolve this? I'm having the same issue with 3 systems -> dev/qua/prd

I have other systems working just fine.

I've implemented the latest Note 1590226 - MOpz Collective Correction 27but still issue remains.

Any idea?

[Former Member]

I've managed to resolve my issue...

It was a inconsistency in the Logical components (via SMSY) and then updating it to the Solution Landscape - Operation.

[Former Member]

Hi Ruben,

Could you please tell us how did you solved your inconsistency via tcode SMSY. We are facing the same problem with our Solution Manager, we have empty target stack on MOPz.

Thanks in advance.

Regards,