Software Update Manager (SUM)'s Odd States

[HuseyinBilgen]

Have you ever done an upgrade with SUM?

If yes, have you ever done an Ehancement Package 6 Installation for SAP ERP?

If yes, have you seen the following odd state?

We noticed the following state during our recent ERP 6.0 EHP6 Upgrades.

Situation

When you're doing an EHP Upgrade/Installation, you've to use SAP Solution Manager to generate the STACK.XML file for the system in order to download and execute the Installation/Upgrade.

During this process, you may remember that you're setting the ERP version to EHP6 for SAP ERP 6.0 and NetWeaver version to SAP EHP3 for SAP NetWeaver 7.0 as it can be seen below:

Then you're copying this STACK.XML onto server and run the SUM by using this STACK.XML and downloaded files. Below you can see the SUM 1.0 SP5. IT shows you the source and terget releases and it is same as the releases you see on Solman MOPZ screens.

When you finish the upgrade/installation, SUM shows you another screen with the same information as seen below

Everything seems to consistent until you finish the EHP6 upgrade/installation. But when you check the software components releases and SP levels via SPAM or System>Status, Suprise :smile:

Question

Who is responsible of this dramatic change? Yes I accept that it may be the case that NetWeaver 7.03 and NetWeaver 7.31 has the same code level, but why this suprise?