How to Generate Stack Xml for Ehp4 and Above Upgrade Applies to: ECC 6.0 EHP4 or Above. For more information, visit the Enterprise Resource Planning homepage Summary For upgrading Enhancement Package4 (EHP4) and above we need to have a Stack XML file of our target SAP system, which can only be generated with solution manager. Before proceeding, make it sure that your system has been added and correctly defined in solution manager or not. Once it is verified you can proceed with generation Stack XML file Author: Manish Chandra Company: Tata Consultancy Services Ltd Created on: 5 th May 2011 Author Bio Manish Chandra has been working with Tata Consultancy services Ltd since last 4 years as SAP BASIS Consultant. 2011 SAP AG 1
Table of Contents Introduction:... 3 Pre-requites:... 3 Procedure:... 3 Related Content... 16 Disclaimer and Liability Notice... 17 2011 SAP AG 2
Introduction: From EHP4 onwards, SAP has introduced Stack XML concept to upgrade. The Stack XML is required for upgrade. Pre-requites: Before starting the upgrade, you must check and ensure that MOPZ is working on your Solution manager system. Procedure: 1. First Check if the user id with which you have logged in is assigened to any S-User or not. It can be checked by using t-code AISUSER. 2011 SAP AG 3
Here Check if the user id with you have logged in, exists or not,if not click on new entries and add the user id and s-user which will be used to download the files from service market place 2. Add the user id and assign s-user to it 2011 SAP AG 4
3. Execute T-code DSWP 4. Select the solution for which the system belongs 2011 SAP AG 5
5. Goto tab Change Management and select option Maintenance Optimizer 6. Click on Tab Create New Maintenance Transaction on right side 7. On next screen select the product version for which Upgrade has to be done and Select the system 2011 SAP AG 6
8. Select the system 9. Select the option Enhancement Package Installation and continue 2011 SAP AG 7
10. Select the target stack (e.g. SP8 or SP7) and the technical usage of upgrade component. You can get the technical usage of software component from note number 1165438 After selection of technical usage click continue 2011 SAP AG 8
Next screen select OS/DB dependent files (e.g Kernel) if required to upgrade or else click continue 2011 SAP AG 9
Next screen step select the files with stack dependence which are to be upgraded. 2011 SAP AG 10
2011 SAP AG 11
Select the 2 nd option Click on confirmation Tab 2011 SAP AG 12
In the pop-up,select the files that are to be downloaded to download basket and click on confirm download. Click continue. Note the Transaction number (e.g. here it is 8000000490) and from the dropdown menu select completed 2011 SAP AG 13
Select completed status and click continue Click on tab complete transaction Now Goto t-code /n/tmwflow/mopz_stack 2011 SAP AG 14
In The next screen enter Transaction number and execute Next screen export the stack configuration XML file and save it 2011 SAP AG 15
Related Content http://forums.sdn.sap.com/thread.jspa?threadid=1371611 Note 1088980 - Documentation: SAP Solution Manager Note 1024932 - Maintenance Optimizer: Collective Note For more information, visit the Enterprise Resource Planning homepage 2011 SAP AG 16
Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document. 2011 SAP AG 17