Twicking Stack.XML file

Hello Experts,
We are doing the ECC6 EHP4 upgrade in our system. As per the process we generated Stack.XML first from our Solution manager for our test system and we used it for very first EHP4 installation on our test system. EHP4 was successfully installed. Now we are repeating the exact same EHP4 installation in to our next system which has different SID, Host etc.
Is it possible to just update the existing Stack.XML file and replace new host and SID of the next system in it, rather than re doign all Solution Manager steps just to generate new Stack.XML for next system ?
Thanks,
Harshal

Good to hear that, so what all i need is just to change the
Hostname, SID and installation number in it ?
or
anything else as well ? How should i keep the new file name as it contains some numbers in the file name
(e.g. SMSDXML_<SID>_<DATE&TIME>.<ID> (SMSDXML_ECB_20100121000340.255) ?
Thanks,
Harshal

Similar Messages

Error while generating stack.xml file in solman

Hi All,
I am unable to generate a stack.xml file in solman, below is the error.
Also, how to select a patch for Java stack JVM in solman. Please help me.
Thanks,
Dheeraj

Hi Kartik,
Thanks for the info.
I am trying to upgrade SAP JVM from 6.1.49 to 6.1.64,
I tried by manually downloading the file and upload it through SUM it was not successful.
Now I am trying with stack.xml and some product instance are not installed.
Any suggestions??
Regards,
Dheeraj

EHP4 - Stack XML file related issue

Hi,
I have the following two issues from DSWP tcode (or solution_manager):
1. From DSWP code -> Change Management -> Maintenance Optimizer, New
Maintenance Transaction and i select the ERP system , then i select the radio button Enhancement Package Installation after which it is showing a drop down from where i can
select EHP4 installation and second drop down i can select support
stack 03. But if i do the same thing again by coming out and going back
in on the same day it is showing only support stack 01, Next day again
for one time it is showing.. --- Why is it like this ?
2. Also after selecting the EHP4 version, support stack 03 it log's on
to the ERP system and it comes out with lot of components from
which if i select some of them and deselect some of them as per our
need, it continues to next screen and confirms the file from download
manager and also the XML file gets's created but unfortunately the XML
file contains all components including the one we deselect because of
which we ended up in doing all shown components last week. We
are in a stage of applying another technical usage and the xml is
created with all the components again. Any idea how to avoid this ?
Thanks,
Murali.

Hi,
The problem might be configuration of your system in SMSY transaction ...Because if some componenets you have selected there will come as selected by default...
Moreover go to SAP Note 1134872 - Maintenance Optimizer: FAQ for Stack Delta Files and related sap note to this note which contains problems related to MOPZ and stack xml file..
Thanks
Sunny

RPT_MOPZ_COPY_STACK_XML shows SC version differs for JAVA and DUAL-Stack xml files

Hi All,
I am using the report/program RPT_MOPZ_COPY_STACK_XML to copy the stack xml file I used from a previous upgraded system. Systems are identical. However, report shows below..
"Software Component Version KRNL64UC7.20 [01200615320200013056] differs between <System1> and <System2>"
and
Software Component Version SAPJVM6.1 [01200615320200012982] differs between <System1> and <System2>"
However, this is not the case when checked, it's strange that this particular component has the same version between the two systems, but the report says they differs in version.
Please help check how to resolve the issue.
SAP notes mentioned in below KBA were already obsolete. Solution Manager system just upgraded to 7.1 SP11.
1711612 - RPT_MOPZ_COPY_STACK_XML Report Troubleshooting.
We would appreciate your response for us to resolve this issue. Thanks.
Regards,
Philip

Hi Jansi, Divyanshu,
Both system have the same patch levels.
Here the situation, SYS1 is where we generated the stack xml file. Afterwards, used that stack file to upgrade SYS1.
Now we built SYS2, ensuring it has the same components version with the un-upgraded version of SYS1, so yes they have same patch number for same components, for this issue, kernel and jvm.
Thus, instead of running MOPZ for SYS2, we used RPT_MOPZ_COPY_STACK_XML to convert the stack file of SYS1 to be used for SYS2.
This is where we encountered below messages, when performing the copy.
"Software Component Version KRNL64UC7.20 [01200615320200013056] differs between <System1> and <System2>"
and
Software Component Version SAPJVM6.1 [01200615320200012982] differs between <System1> and <System2>"
We previously used SOLMAN 7.0 SP23, and the report is working fine there. Then recently, solman was upgraded to 7.1 SP11, and now the report is not working with the above issue.
We would appreciate if you could share actions on how we can fix the issue.
Regards,
Philip

Cannot generate stack.xml file

Greetings,
We are not able to generated stack.xml file in /usr/sap/trans/EPS/in
We have tried in /n/tmwflow/mopz_stack.
MOPZ is configured we are able to approve support patches
This xml file is required to upgrade the ECC_DIMP from 600 to 605
Please advice
R..../-

Wrote to SAP. Got the below mentioned reply from them
Please make sure that in transaction SMSY, in the Header Data tab for
the system you want to upgrade, both ERP 6 and EHP5 for ERP 6 are added
as product versions and also active. Information about why this is
needed can be found in note 1464712.
Please don't forget to choose a relevant product instance for ERP 6.
After this is done, please enter the system in an ERP 6 logical
component. Please add the new ERP 6 logical component to another
solution, and please proceed to opening the Maintenance Optimizer
transaction from the solution with the ERP 6 logical component.
The option to choose should be 'Enhancement Package install'.
The technical usage to choose is Discrete Ind.& Mill Products.
If somehow you are not able to choose technical usage Discrete Ind.&
Mill Products in the technical usage screen in Maintenance Optimizer:
please check note 1324838 for the required product instances of ERP 6
in SMSY.

Stack.xml file

Hi,
Currently we have NW7.0 SR3 (ABAPJAVA), Now we are planning to upgarde to EHP1 through ehp1 tool. how i can generate stack.xml file for (ABAPJAVA) stack without solution manager. Kindly help me
Regards,
Sampath.

Hi,
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/swdc/sps/index.do?pvnr=01200615320900001250&u=&session_id=saS000427859520110124070001SID%3aANON%3apwdf4962_OW1_01%3aBkxYmOjMQn50g5RGGRAOjSdi_oZwuReU3be5uAej-ATT
Check here.
You have NW 7.0 as source and EHP1 is present in target.
Regards,
Nirmal.K

MOPZ has issues calculating stack XML file in SOLUTION MANAGER

Hello,
We have a SOLUTION MANAGER system on NW 7.0 EHP1 SP stack level at initial support stack (ISS).
Recently we upgraded all our R/3 systems to ECC6.0 EHP4 SPS04 and now we are trying to upgrade the stack level to EHP4 SPS07. So we are trying to get a XML file from MOPZ but no luck.
The backend system has all the correct data updated in SMSY and all looks fine but while we try to calculate the stack for EHP4 SPS07 it ends with error like below mentioned.
Please look into the errors and throw some light if anyone has come across the same.
Error details:
System Messages
Type Message Text
Error The Installation/Upgrade Package for Add-on EA-APP L rel. 600 is not available
Error ABAP queue check failed
But the backend system has EA-APPL level at 604, we do not know why it is looking for installation/upgrade package for
EA-APPL 600.
Regards,
Yoganand.V

hi
can you check the sap note
1. Note 1277035 - Solution Manager: EHP4 product data missing
might be this could be the reason for your issue
or
check the thread already discussed the same and the solution also provided
[EHP4 upgrade error on SAPK-603DHINEAPS|EHP4 upgrade error on SAPK-603DHINEAPS]
////////////////It seems that there is a small bug in teh software vector for EA-PS.
Essentially, SAINT prevents you from going forward because it thinks that you don't have the correct version of EA-PS installed.
The solution for this is described in OSS Note: 1143022
"To import EA-PS in a system that already has the level EA-APPL 604, load the attached file ACP_EAPS.SAR into your system (SPAM-> Support Package -> Load Packages -> from Frontend) before you start the import using SAPehpi. Otherwise, an error may occur in the queue calculation, which can be solved by reloading the ACP"////////////////////////
check and update
Jansi

Problem with Stack XML file

Hello,
We have an ECC 6 system with EHP 4 SPS 5 and we watn to install a new Technical Usage (IS-OIL, IS-PRA and IS-UT)
In order to do that I have to supply an xml file created by the MOPZ.
I created a new MOPZ transaction, in the phaze "Update Options" I selected : Enhancement Package Installation,
Afterwards I selected in Target Enhancment package stack : SAP ERP Enhanecment Package 4 on NW7.01 - SP Stack 05
We do not want to upgrade the Stack to a latter one.
I have selected Oil & Gas with Utilities and continued.
The Sack XML that was created contained SAP-APPL, SAP-BASIS and SAP-ABA in patch level 8. we do not want to upgrade these components.
Is there a way to install a new Technical Usage without upgrading these components?
and if there is how can I create XML file suited for this situation?
Please Advice,
Zvi Gilinsky

Hello,
There is an equivalence of Support Package levels between EHP stacks and baseline ERP 6 stacks. Note 1064635 has a list of these equivalences.
In any case, stack 5 for EHP4 of ERP should include stack 5 of NW 701.
By your description it looks like you are having a Maintenance Optimizer issue. What is the Maintenance Optimizer stack level?
Best regards,
Miguel Ariñ

Can't convert stack XML file using report RPT_MOPZ_COPY_STACK for upgrade

Hello Colleagues/ SAP Experts,
Here is a background. 2 weeks ago, we have generated an XML stack file using MOPZ in solman 7.1 for the following systems (P6D which is DEV,
P6Q which is quality, P6R which is regression and P1P which is production). We were at our technical cutover rehearsal phase and the system that we were rehearsing was P6R. But AFTER our technical cutover, a new java component, which is seeburger as2 adapter, was installed in P1P, PRODUCTION. Thus, the landscape of P1P has changed as a new component was introduced and we believe that the generated XML file 2 weeks ago will no longer be valid for P1P. Instead of generating another xml file thru mopz for P1P, we would like to use report RPT_MOPZ_COPY_STACK_XML to convert the XML file OF P6R to map it toP1P. I have uploaded P6R XML and the target is P1P. So as you can see, P6R XML (source) --> P1P target.
Actions already done are the following:
1) Fulfilled and followed the resolution in note: 1711612
RPT_MOPZ_COPY_STACK_XML Report Troubleshooting
2) SAP-OSS is working in SM59
Basically, program RPT_MOPZ_COPY_STACK does not convert the Regression system's xml to the target, which is production. Kindly see attached screenshot. *the screenshot shows only 1 component in error but upon clicking the 'next difference' button, it will still show other components. I have checked my lmdb settings, will there be workaround for the issue?
Regards,
Meinard

Hello Divyanshu Srivastava / Reagan Benjamin ,
Thank you for your replies. Yes I noticed that a new higher patch for one java component was already present when I have regenerated recently for production using mopz. Anyways, SAP has returned a message wherein they edited the xml file themselves. Most of errors were eliminated only error was kernel versions was not matched. We need to upgrade kernel of our production and test if it works. Hopefully it will. Thanks though at first we did not edit the xml as according to one sap note I read it will not be supported by SAP. Closing this thread now

Stack.xml There are no stack independent files in your selection error

Hi experts,
I am trying to do EHP upgrade from SR3 to EHP 6 , while generating stack.xml file using MOPZ I am facing the problem as like...
" There are no stack independent files in your selection "
Please find the attachment and help us if any one aware of it.
Note: Windows 2008 on Oracle 10 .2

Hi
Manu Mohandas
Thanks for your reply,
But We have selected those DB dependent Kernel files and DB independent kernel files in the previous step.
As you said we have clicked the " continue" .
PFA of next screen It is giving the same as previous ...
CHEERS
HSK

How to get stack.xml for EHP2 Netweaver BI 7.0 Upgrade without SolMan?

Hi Experts,
We are planning for BI 7.0 EHP2 upgrade from BW 3.5
SAP_ABA u2013 6.40 - 24
SAP_BASIS u2013 6.40 - 24
PI_BASIS - 2006-1-640 - 8
SAP_BW u2013 3.50 - 24
To Target version of NW BI 7.0 EHP2,
In SAP Support Package Stacks, Itu2019s not showing SPS (SAP Support Package Stacks) for NW BI 7.0 EHP2 but itu2019s showing NW BI 7.0 EHP1, Please advise, how to download SPS for NW BI 7.0 EHP2 with stack.xml file.
Thanks & Regards
Raja

Hi Experts
After getting the stack.xml file, we started the process of upgrading our BW 3.5 system to BW 7.0 EHP2. We
have downloaded all media list and EHPI tool. The EHPI tool latest
version SAPehpi_111-10005800.SAR has been used and we are getting the
following error.
Release '640' is not supported by this tool.
Request you to please suggest the solution.
Regards,
RajaMurugesan,PMP

Upgrade FI-CAX 600 to FI-CAX 617 - how to calculate stack.xml?

Hi experts,
I'm currently on the task to update our FI-CAX from 600 to 617 on our ERP 6.0 EhP7 Utilities system. In SAINT I get the message that this upgrade can only be done with a calculated STACK.XML file, but unfortunatly I'm not able to select FI-CAX in MOPZ. Can anyone guide me through MOPZ and selecting the correct packets?
Kind regards
Roland

Hi Roland,
please open a new Maintenance Optimizer Session. Then you have to choose "Enhancement Package Installation". Please select technical usage "Leasing/Contract A/R & A/P". This will calculate Fi-CA and FI-CAX 617.
Cheers,
Andreas

SAP_BS_FND addon was not selected as part of the stack xml

We are in a process of upgrading production system (SAP NW 7.0) to EhP1, we
have components SEM-BW,FINBASIS installed in the Netweaver system, we have added the system under Netweaver
We have generated the stack xml file using solution manager MoPZ but we are not
getting the option to select the upgrade addon SAP_BS_FND as part of
stack xml file
where in we had an option to select the SAP_BS_FND for Development
and Quality and we have included the addon SAP_BS_FND in stack xml file
my main question was why the component is not available for Production for selecting the option ??
Please suggest us how to proceed further, we have read the note Note
1326576 - SAP NetWeaver Systems Containing SAP ERP Software Components
which says to install the addon after upgrade
generating the stack file from Service Market Place too is not including the SAP_BS_FND in the stack xml
Please help why it is behaving different for production
Thanks,
Ravi
Edited by: ravi prasad on Aug 8, 2011 9:56 AM

Hi,
>The note says that if going with EhP1 with ERP components then it asking to register the system in Netweaver and then >upgarde the addon package with SAINT
You should read the note carefully, below is extract from this note:
Maintain your SEM, E-Recruiting or SAP Learning Management system as an ERP
system in SMSY in order to download the EHP packages and to be able to
maintain the system. Afterwards you must not use the generated Stack XML,
but instead use a generated Stack XML from SAP Service Marketplace and
include the packages for ERECRUIT, SEM-BW, FINBASIS or LSOFE in the
IS_SELECT phase during the installation of EHP1 for SAP NetWeaver 7.0.
Thanks
Sunny

Error in stack.xml - Upgrade to EHP1 SPS 8 using SUM

Hello
we're currently upgrading our PI-system. We use SUM
as upgrade tool.
I've opened a maintenance task in solution manager and defined the
target support package stack (SAP PI 7.1 EHP 1 SPS8).
During the upgrade procedure (step 2: Select Target) in SUM I get an
error, after selecting the stack xml file:
Cannot construct a support package stack from
file /usr/sap/trans/EHPinstfiles/SMSDXML_XIT_20111010063232.419.xml.
Stack definition
file /usr/sap/trans/EHPinstfiles/SMSDXML_XIT_20111010063232.419.xml is
rejected.
See error messages in /usr/sap/XIT/SUM/sdt/log/SUM/DEFINE-TARGET-
SOURCE_09.LOG.
DETECT define_target define-target-dialog define-target-
source com.sap.sdt.j2ee.services.servicesimpl.DefineTargetService class com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParserException
Next an outtake of the log-file:
Oct 12, 2011 10:31:41 AM [Info ]: Basic component properties of SDU file DEPLOYARCHIVES/sap.com~tc~lm~itsam~co~ui~xi~msg~wd.ear have been read. Component name is sap.com/tc/lm/itsam/co/ui/xi/msg/wd and version is 7.11.
Oct 12, 2011 10:31:41 AM [Info ]: Subcomponents of component sap.com/SOAMONBASIC have been processed.
Oct 12, 2011 10:31:41 AM [Info ]: File /usr/sap/trans/EHPinstfiles/SOAMONBASIC08_0-10006070.SCA has been analyzed for deployment components.
Oct 12, 2011 10:31:41 AM [Error ]: Component with name SERVERCORE and vendor sap.com has multiple archive names.
Oct 12, 2011 10:31:41 AM [Info ]: Parsing of stack definition file /usr/sap/trans/EHPinstfiles/SMSDXML_XIT_20111010063232.419.xml has finished.
Oct 12, 2011 10:31:41 AM [Error ]: The following problem has occurred during step execution com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParserException: Cannot construct a support package
stack from file /usr/sap/trans/EHPinstfiles/SMSDXML_XIT_20111010063232.419.xml.
Stack definition file /usr/sap/trans/EHPinstfiles/SMSDXML_XIT_20111010063232.419.xml is rejected. See error messages in /usr/sap/XIT/SUM/sdt/log/SUM/DEFINE-TARGET-SOURCE_12.LOG.
Regards
Christian Kaiser

Hello
I've solved the problem.
In the stack.xml file are multiples software-components with the same name, here "SERVERCORE".
I had 3 entries, two with patch-level 0 and one with patch-level 1.
I've deleted the two entries with patch-level 0 and then it works.
Regards Christian

Stack XML creation for specific package

Hello
I want to upgrade my ERP 6.0 EHP4 system's LSOFE 603 to 604 but I received I need a stack.xml for upgrade. Our Solution Manager 7.0 EHP1 system is recognising ERP system's SP levels but it is not giving me an upgrade option for LSOFE. I only saw latest SP which was 7 and all other SP's latest levels but not upgrade packages.
How can I create a stack.xml for LSOFE 604?

hi,
If you operate a Netweaver system that contains at least one ERP software component (ERECRUIT, SEM-BW, FINBASIS or LSOFE), you must not use a stack XML file created for an SAP ERP system. Instead, you have to use a stack XML file for SAP NetWeaver systems. The EHP4 packages for the ERP software components have to be added manually in phase IS_SELECT.
Generating the Stack XML File
First of all, create a stack XML file for NetWeaver systems. This can be done either via the SAP Service Marketplace or in the Maintenance Optimizer of your SAP Solution Manager.
check and update.
Jansi

Twicking Stack.XML file

Similar Messages

Maybe you are looking for