Maintenance Optimizer SP Stack XML calculation is not showing ABAP components

[Former Member]

Hello,

We are currently have SAP Solution Manager 7.0 EHP1 SP24 installed and we are trying to Upgrade this to SAP Solution Manager 7.1 SP04 (Latest).

So, for starting the Solution Manager 7.1 Upgrade, we need to generate the Upgrade XML file in Maintenance Optimizer (SOLUTION_MANAGER). When we tried to calculate the Upgrade XML, at the 2.6 step in the Maintenance Transaction, the ABAP support pakcages are not visible except ST-ICO & ST-SER and Java Components.

FYI - We have checked the RFC connections for OSS in SM59 & RFC's in SMSY. All are working fine.

Could you please let us know if anyone has faced this issue.

Thanks & Regards,

Prabhu Reddy.

[Former Member · Accepted solution]

Hello Everyone,

Thanks for the response. SAP also replied to use all the DVDs and the XML created by MOPZ     (providing XML created by Maintenance Optimizer as per the SAP Note: SAP Note 1577909 - Additional information about Solution Manager 7.1 SR1).

When we started the SOLMANUP upgrade tool:

It finished Initialization phase successfully.

It also finished Extraction phase sucessfully without any issues, but

when checked the "EPS\in" directory, there were no extracted files

available. (FYI - The SOLMANUP Program detected all SAP Solution

Manager 7.1 Upgrade DVDs automatically except the downloaded support

packages created by XML using MOPZ).

We also continued with Configuration phase and provided the Stack.XML

file (Stack.XML file created by MOPZ) and after providing this XML

file, it did not pickup the Add-Ons, Support Packages itself and we are

stopped the Upgrade because of this issue.

Now, the question is how to continue further?

Kindly suggest how to continue further at this critical stage.

Thanks & Regards,

Prabhu Reddy.

[Former Member · Accepted solution]

Hello All,

This is to just to share with all.

After we downloaded the XML created by MOPZ and its Support Packages, Place all the XML files, Support Packages, SAP Solution Manager 7.1 SPS04 Upgrade DVDs in one directory i.e., Download Directory and start the SOLMAN 7.1 Upgrade.

Please use the latest SOLMANUP Upgrade Tool from the SMP.

Please let me know if you're facing similar issues.

Thanks & Regards,

Prabhu Reddy.

[Miguel_Ariño]

Hello,

Please go forward with the Maintenance Optimizer transaction , and when there is an XML file, please check whether all the packages show there.

Development Support recently said that the calculation of SP4 is made so that you don't need to download the files, but you just use the files in the Solution Manager 7.1 SP4 DVD. The XML should have the correct queue.

Please let me know if the XML does not have all the software component packages.

Best regards,

Miguel Ariño

[Former Member]

Hello Everyone,

Thanks for the response. SAP also replied to use all the DVDs and the XML created by MOPZ     (providing XML created by Maintenance Optimizer as per the SAP Note: SAP Note 1577909 - Additional information about Solution Manager 7.1 SR1).

When we started the SOLMANUP upgrade tool:

It finished Initialization phase successfully.

It also finished Extraction phase sucessfully without any issues, but

when checked the "EPS\in" directory, there were no extracted files

available. (FYI - The SOLMANUP Program detected all SAP Solution

Manager 7.1 Upgrade DVDs automatically except the downloaded support

packages created by XML using MOPZ).

We also continued with Configuration phase and provided the Stack.XML

file (Stack.XML file created by MOPZ) and after providing this XML

file, it did not pickup the Add-Ons, Support Packages itself and we are

stopped the Upgrade because of this issue.

Now, the question is how to continue further?

Kindly suggest how to continue further at this critical stage.

Thanks & Regards,

Prabhu Reddy.

[Former Member]

hi,

make sure your spam and saint updated to the latest level, maintenance certificates are up to date.

please read the prerequiste here for automatic calculation of stack xml here. make sure all are valid in your case, spcially marking product instance relevant and product version

http://help.sap.com/saphelp_sm71_sp01/helpdata/en/57/4e0eb0eae6457ea69b509813048989/content.htm

please check

Thanks

Jansi