Hi Donaldo,
Wow! What a ride!
I've been upgrading from ERP6 EHP 6 on NW A.S 7.31 (aka NW A.S 7.0 EHP 3 just to confuse us!). I'm using SUM 1.0 SP11, it has not been going that bad for me. Here are some general advices.
1. Make sure that SLD/LMDB contain the right info abour your systems before running MOPZ to create the stack.xml and downlowd the EHP7 and related SPS archives. Even with all that MOPZ seems to omit some Add-Ons that SUM will complain about later! (The UVERS issues). I can see that from Source and Target System shown in you initial msg, that there seem to be a problem with SLD/LMDB definition in Solman.
2. Update the current Kernel to the latest patch, tp, r3trans and the latest SPAM/SAINT updates. SUM will ask you for that, so if you do it ahead of time you save time later during SUM run. And make sure you use the latest SUM SP.
3. Do not use SUM's "single " use the standard option even when upgrading a Single system like a Sanbox (SAP SUM developers sanitize the most widely used option the most!).
4. Delay whatever you can get away with during SUM run. Let SUM do the mandatory stuff and you will do the rest manually later. For example SUM proposes to integrate SPAU Transport Requests into the update process, but just a screen generation that may not work would complicate the whole upgrade! So unless you sure, defer SPAU until after SUM is done! If you allpied the latest SPAM/SAINT update before the SUM run, you can skip that when SUM asks, etc.
5. Read the SUM Guide it has some good info about how you reset SUM when it get's stuck, and other tips. Make sure you have the latest Active Version of the used SUM Central Note. They update very frequently!
6. You can actually delete from UVERS the entry that you don't care about and make SUM happy!
for example many of the components you see in System Status may not be used by your customer, e.g. the BP-CANW, BP*, EA-HR_for other countries , etc. SUM get's stuck when it sees in UVERS that a Component has same release in the curent system and in the current EHP and SPS that is being applied. I run into the same problem , but in the EXtraction Phase, I reset SUM and it went through it fine the second time! I also tried to get the note you mentioned but SAP seems to haven't released it publicly! Of course, you did the right thing by making a backup of the table before changing it!
Finally, If I had caught your problems earlier, I'd have said either:
A)you were done with the Update if you reached the PostProcessing Phase! You could have stopped SUM, applied all the stuff it complained about manually! or,
B) In later messages, it sounds like things were corrupted?! Because the components of the NW A.S 7.4 : SAP_BASIS and SAP_ABA must show 7.4x and the Components of ERP 6.0 like SAP_APPL must show 6.17 if the update to EHP7 is correct! So at that point I'd say scrap it, reset SUM (as shown in the SUM Guide ) and start from scratch! If the Reset described in the Guide doesn't work (It didn't work for me!) try these steps!
1)Go to the directory SUM\abap\bin.
2)Enter the command "\SAPup reset prepare"
3)Delete the SUM directory.
4)End all SAPup processes on OS level before, if any exist.
5)Please try to run report RSUPGRES. This will solve UVERS inconsistency
6)Start everything again from beginning.
Finally be prepared, have fun and don't let SUM frustrate you!
Good luck!
Atman