Then SUM suddenly complained about mismatches in table UVERS, stating that it didn't find the version numbers it expected.Īnd indeed, when I loaded the Stack XML file in SAINt, it shows that it has, for at least six modules, the correct target releases specified, but complained that it could not safely finish the queue, because it was 'missing support packages'. So I proceeded with the upgrade and besides some minor hickups with locked transports and modified SAP tables, it went through fine until we reached step 'Postprocessing'. I had SUM run over the flat dir, with all the SAR Archives in it, and it didn't complain that it couldn't find certain, required target packages. We used MOPZ from a Solution Manager with a new release level (7.x and most recent SP package stack), so I trusted the XML file that it calculated for us.Ī co-worker of mine took care of the actual download, because we have certain bandwidth limitations to combat at the office. In preparation for the test upgrade of an ancient ECC6 system to xxx, we copied the Quality Assurance system of our ERP/ECC landscape to an isolated sandbox system (also named Q01).
