cancel
Showing results for 
Search instead for 
Did you mean: 

MPoz does not calculate stack files for EHP6 upgrade

Former Member
0 Kudos

Hi,

We are planning to do a EHP upgrade from ECC6 EHP0 to ECC6 EHP6, however my MPoz does not display stack files for EHP6 and EHP7.

It however displays the correct target in "Confirm target" for EHP5, EHP4, etc, but not for EHP6.

I have applied the following SAP Notes already:

Note 1681026 - Solution Manager: EHP6 product data missing

1935993 - SMSY: EHP7 - Product data is missing


but this did not help.


Any thoughts on this?


Thank you.

Best Regards,

Shilpa Jaiswal

Accepted Solutions (0)

Answers (9)

Answers (9)

Former Member
0 Kudos

Dear All,

Thank you for your time. The issue has been resolved.

Apparently using MPOZ i was trying to calculate queue for EHP6 SP14, but this was not possible.

When I did the same for EHP6 SPS8, i could proceed without any issues.

Thank you all for your help.

former_member185954
Active Contributor
0 Kudos

Hello Shilpa,

Can you please post the screenshot of your Solman 7.1 SP levels found in SPAM transaction.

Regards,

Siddhesh

Former Member
0 Kudos

Hi Siddhesh,

Please find below:

imaad_vasiq
Explorer
0 Kudos

Hi

How systems data is maintained in LMDB? Make sure that the data coming in LMDB is through SLD and maintain the production definition in LMDB properly.

Maintenance of Product in the System Landscape - SAP Solution Manager Setup - SCN Wiki

Regards

Imad

Former Member
0 Kudos

This is done already

former_member233480
Discoverer
0 Kudos

Hello.

Try note 1940845

Former Member
0 Kudos

Hi Anvar,

This note has been applied, however we are still not able to calculate the queue for EHP6.

Miguel_Ariño
Advisor
Advisor
0 Kudos

Hello,

In the log tab, there may be a warning message about dual stack not supported for EHP7 for SAP ERP 6.0 . Please check carefully the log tab.

If your system is a dual stack system, then upgrade to EHP7 for SAP ERP 6.0 is not supported directly. A dual stack split is necessary.

Best regards,

Miguel Ariño

Former Member
0 Kudos

hi Miguel Arino,

strangest part is there are no errors or warnings in log about this.

moreover I'm trying to generate stack for Ehp6.

the confirm major target stage simply does not display entry for Ehp6.

our solution manager is 7.1 sp12.

any ideas?

mamartins
Active Contributor
0 Kudos

Hi,

How recent is the SP level of your source system?

The EHP6 or 7, because they upgrade to Netweaver 7.40, they have pre-requisites in terms of SP level.

Recently I have done a MOPZ simulation to upgrade a ERP 6 (Netweaver 7.0 - no EHP) with sucess.

Please check the document https://websmp108.sap-ag.de/~sapidb/011000358700000552252012E

MM

Former Member
0 Kudos

Our source system is on SAP ERP 6.0 - SPS 23. DB on MSSQL 2012 and server running on MSSQL 2012.

Miguel_Ariño
Advisor
Advisor
0 Kudos

EHP6 does not upgrade to Netweaver 7.4.

former_member182657
Active Contributor
0 Kudos

Hi,

Is the note  1969109 - SAP Solution Manager 7.1 SP12 - Basic functions 

completely implemented on the system.Please confirm ?

Regards,

Former Member
0 Kudos

HI Gaurav,

yes that note was completely implemented during setup of solution manager.

rahul_yedapally
Active Participant
0 Kudos

Hi shilpa,

if you check in PAM, no option for EHP7 direct upgrade.

first we need to upgrade to some EHPS and then upgrade to EHP7

Windows server and SQL server database needs to be updated to latest patch

Thanks,

Rahul Yedapally

Former Member
0 Kudos

HI Rahul,

we actually want want to upgrade to EHP6, but the confirm major target stage shows no errors there.

Former Member
0 Kudos

In the stage "Confirm Major Target", I do not see the entry for EHP6 / Netweaver 7.3

However for other EHP levels wiz. EHP5, 4, I can see the respective entries in 'Confirm Major Target'

Former Member
0 Kudos

Hi Shilpa

Please Ensure that you applied all notes from infotype@1 of note 1887979.



Kind Regards,

Phaneendra K

Former Member
0 Kudos

Hi,

I have applied the patches for solman 7.1 SP12 and it does not solve the issue