Solution Manager version for Upgrade

[laurie_mcginley]

We are planning a technical upgrade soon from ECC 5.0 to ECC 6.0. (Windows and SQL Server) We have solution manager and use it as part of the landscape. Does it need to be brought to the same version as the other servers.

Seems there is a need for Solution Manager to use Netweaver which should be on a 64 bit system, which we do not have so don't want to do the upgrade on it.

Thanks in advance.

Laurie

[laurie_mcginley]

Thanks for the info, I have a better idea what needs to be done now.

Laurie

[former_member194360]

Hi Laurie

Since SAP ERP 6.0 Service Release 3 it is possible to install enhancement packages with an upgrade.

Following the SAP ERP 6.0 Master Guide holds (= for upgrades without enhancement package):

"With mass shipment of SAP ERP 6.0, SAP Solution Manager 4.0 running on NetWeaver 7.0 should be used"

Following the SAP enhancement package 3 for SAP ERP 6.0 Master Guide (= for upgrades with enhancement package), and namely SAP Note 1095233 holds:

"In case you want to use the Solution Manager Maintenance

Optimizer for installation support, we strongly recommend to have

installed at least SAP Solution Manager 4.0 Support Package 13.

Solution Manager Content should be updated to ST-ICO 150 Support

Package 13."

regards,

Andreas R

[Matt_Fraser]

Laurie,

Bear in mind that a Solution Manager v3.2 is sufficient (including in 32-bit) for the basics of a technical upgrade to ERP 6.0. However, if you want to include Enhancement Packages in your upgrade, or apply them later, then you need to use the Maintenance Optimizer in SolMan v7.0 (this is the same version as 4.0, it just got renumbered to be consistent with the underlying Netweaver release number). See Note 1155041 for this, and Note 1024932 for general discussion of what can be done with MOPZ in the different SolMan releases. It might be possible to do EnhPks with SolMan 3.2, but the documentation doesn't say this.

Additionally, it is generally recommended that your SolMan system be equal to or higher than your highest release and support pack level for all the monitored systems. So, if you're going to ERP 6.0, which is based on Netweaver 7.0, then you should really have SolMan 7.0 in your landscape, and have it at the highest support stack level available at the time of your upgrade. Is it critical? Probably not, but it is recommended.

As for 32-bit vs 64-bit, I would guess that decision is driven by what your hardware, OS, and DBMS support. Even if you only have 4 GB of RAM or less on the system, I would still generally recommend going to 64-bit. As far as the SolMan application is concerned, this is a non-event -- you just have to switch out the kernel to the 64-bit version. However, you do first need to be on a 64-bit OS and DBMS, so you would have to look into how much effort that transition would take. If you're getting by fine now on 32-bit, though, I see no reason why you couldn't stay there, and just go to 64-bit whenever you next upgrade your hardware.

Regards,

Matt

[Former Member]

Hi,

No you do not need to upgrade your Solution Manager 7.0 the latest version or migrate to a 64-bit.

All you will need during the upgrade is the key to be generated via Solution Manager that is fine.

And to set-up monitoring of ECC 6.0 and addition of the system in the landscape via Solution Manager is also fine with your present version. So you are fine to go for the upgrade from ECC 5 -> 6 with your current solution manager.

- Regards, Dibya

[Former Member]

What solution manager version do you have?

During the technical Upgrade the only thing you need is the solution manager key generated for the new system. If you will use Solman during the functional upgrade to carry on the project, then it will be better to have the 4.0.

If you have 4.0 32 bits don´t worry, you don´t have to upgrade to 64bits in a hurry, you can take your time to do it latter.