EHP Stack file
I have multiple systems with same configuration where I need to update to EHP4 for ERP6 (EHP4 ready systems) on DB2 UDB. (ABAP only; central system)
I know that I can use the same set of SP files downloaded but I'll need to modify my stack file. I want to avoid registering in mopz for this time..
Any clue on how can the stack file be modified ? I have come across two unique system dependent entries in stack file including SID & Hostname ... is there anything else that I should change ?
Thanks,
Hi,
Another best approch to generate consistent EHP stack is, select all systems ( in step - v ), so that for entier landscape you will have only one EHP stack file.
You can use the folloiwng steps to generate EHP stack.
I assumed that your system has been connected to SolMan system.
i) Use the t-code DSWP
ii) Select the active solution form the list , say SAP ECC system
iii) Once you select the solution, click on “operation” than select the “ Maintenance Optimizer”
iv) Once you select Maintenance Optimizer tab, on the same window, click on “ Create new maintenance transaction” and this will open your default browser ( IE or Firefox )
v) On the browser you need to select three things and click on continue
-- Solution : Same as step-ii
-- Product Version : ( Say ECC 6.0 )
-- System ( Say Dev or QAS)
vi) Select “Calculate file automatically” . It will take some time
Rest of the steps are easy – you can select your components, OS, DB etc
Regards,
Dipam
Similar Messages
-
XML file or Configuration stack file for Ehp inclusion in Upgradation
Hi,
We are Upgrading 4.7 to Ecc 6.0, we want to include Ehp3 in the Upgradation but we are not able to generate XML or Configuration stack file, can anybody please help me to get XML file or Configuration stack file for Ehp inclusion in Upgradation.
Regards,Hi Aashish,
can you please provide some further information?
What exactly are you doing in the SAP Solution Manager - Maintenance Optimizer?
I assume that you are at least on SP 15 which is a prerequisite.
Currently a common error is a wrong maintained SMSY: Please check SAP note 1022072 for details.
Best regards,
Christian. -
EHP5 Stack File is invalid: component 'EA-HR' (stack release 600 source .
Hi all . . .
Attempting to install EHP5 on ERP ABAP stack. Currently on EHP4 SPS5.
During the configuration roadmap step, the Stack configuration overview told me that "for the following components, a Component Upgrade/Installation and/or Support Packages will be included according to the selected EhP stack configuration . . . " and it proceeded to list the various compoents and their intended releases. During that, I did take note that it wanted to move EA-HR to 600 SPLevel 0059 . . . I was surprised by this, yet I pressed on.
Now, during the Information Gathering phase (PREP_EXTENSION/SUBMOD_EXTENSION_NEW/EHP_INCLUSION) I received the error:
Last error code set: Stack file is invalid: component 'EA-HR' (stack release 600 < source release 604)
I understand that it is trying to tell me that the component is trying to install a release lower than what is already installed. The problem is, I do not know how to go about fixing it.
Any suggestions?
Thanks,
Bryan MontgomeryHello Bryan,
I believe the best and fastest way to have EA-HR upgraded to 605 is to unselect this usage type in MOPZ, regenerate the XML without it, upgrade the rest of the system to EhP5 level and, afterwards, upgrade only EA-HR to 605 level using SAINT.
Please make sure to check the EHP5 manuals:
http://service.sap.com/swdc
-> Ramp-Up Releases and Beta Software
-> Installation and Upgrade
-> EHP5 FOR SAP ERP 6.0
-> Technical Documentation
and these notes:
#1323537 - Release Info SAP Enhancement Package 5 for SAP ERP 6.0
#1304648 - SAP ERP Enhan.Pk.5 SP Stack 01(10/2009) - Release Information Note
Best regards,
Tomas Black -
Select appreciate components on Mopz for XML.Stack file on CD51033594 1-3
Dear Experts !
I have install ERP 6.0 EhP 4, then I use SAPehpi 7.0 tool to update software components from CD51033594 1-3, but in processing, It have error XML.Stack. Please show me how to select right component for XML.Stack from CD51033594 1-3.
Thanks and Best Regards. I hope, you can support for me as soon as possibleDear Expert !
Fist thank you very much for your answers ! I have installed a ABAP System on ERP 6.0 EhP 4 product with CD source from SAP Market : 51036888_13,51036902,51036767_5. And I need update my system from CD source 51033594 by SAPehpi 7.0 tool. But when processing update by SAPehpi 7.0 tool, It required a XML.Stack file. So how to I can select right XML.Stack file for my system ERP 6.0 EhP 4 on Solution Manager Maintenance Optimizer. Please help me as soon as possible. Thanks and Best Regards ! -
Stack file generation for upgrade
Hello,
I have to generate Stack.xml file to upgrade the system.
Kindly guide me for stack file generation and SUM toll for upgrading the system.
Thanks and Regards,
AkshayHi Akshay,
Kindly guide me for stack file generation and SUM toll for upgrading the system.
Above information is easily available on SCN,please search or elaborate exact issues which you're facing now.Anyways follow SCN doc at Generating Stack For EHP Upgrade
Regards, -
Stack file that is generated does not contain any java components
We are in process of upgrading our ecc6.0 system with ehp4. The enhancement is stuck up in configuration phase for JAVA. Though we have configured Java in solution manager the stack file that is generated does not contain any java components and so the installation is stuck up. Kindly request you to advice us on this issue .
Attached is the 'Trouble Ticket Report', PREPARE_JSPM_QUEUE_CSZ_01.LOG, and SMSDXML_EA4_20100623144541.375.txt
++++
Trouble Ticket Report
Installation of enhancement package 1 for SAP NetWeaver 7.0
SID................: EA4
Hostname...........: wipro
Install directory..: e:/usr/sap/EA4
Upgrade directory..: F:\EHPI\java
Database...........: Oracle
Operating System...: NT
JDK version........: 1.6.0_07 SAP AG
SAPJup version.....: 3.4.29
Source release.....: 700
Target release.....: 700
Start release SP...: $(/J2EE/StandardSystem/SPLevel)
Target release SP..: $(/J2EE/ShadowSystem/SPLevel)
Current usages.....:
ABAP stack present.: true
The execution of PREPARE/INIT/PREPARE_JSPM_QUEUE ended in error.
The stack E:\usr\sap\trans\EPS\SMSDXML_EA4_20100625054857.968.xml contains no components for this system.
More information can be found in the log file F:\EHPI\java\log\PREPARE_JSPM_QUEUE_CSZ_02.LOG.
Use the information provided to trouble-shoot the problem. There might be an OSS note providing a solution to this problem. Search for OSS notes with the following search terms:
com.sap.sdt.j2ee.phases.PhaseTypePrepareJSPMQueue
com.sap.sdt.ucp.phases.PhaseException
The stack E:\usr\sap\trans\EPS\SMSDXML_EA4_20100625054857.968.xml contains no components for this system.
PREPARE_JSPM_QUEUE
INIT
NetWeaver Enhancement Package Installation
SAPJup
Java Enhancement Package Installation
++++++
PREPARE_JSPM_QUEUE_CSZ_01.LOG>>
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[2.0.7.1006]/>
<!NAME[F:\EHPI\java\log\PREPARE_JSPM_QUEUE_CSZ_01.LOG]/>
<!PATTERN[PREPARE_JSPM_QUEUE_CSZ_01.LOG]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%s]: %-100l [%t]: %m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Jun 28, 2010 9:21:23 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:754) [Thread[main,5,main]]: Phase PREPARE/INIT/PREPARE_JSPM_QUEUE has been started.
Jun 28, 2010 9:21:23 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:755) [Thread[main,5,main]]: Phase type is com.sap.sdt.j2ee.phases.PhaseTypePrepareJSPMQueue.
Jun 28, 2010 9:21:23 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]: Parameter inputFile=EHPComponents.xml
Jun 28, 2010 9:21:23 AM [Info]: com.sap.sdt.j2ee.phases.jspm.JSPMQueuePreparatorFactory.createJSPMQueuePreparator(JSPMQueuePreparatorFactory.java:93) [Thread[main,5,main]]: Creating JSPM SP Stack queue preparator.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.ucp.dialog.elim.DialogEliminatorContainer.canBeOmitted(DialogEliminatorContainer.java:96) [Thread[main,5,main]]: Dialog eliminator spStackDialogEliminator allows to omit dialog SPStackLocationDialog
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.util.validate.ValidationProcessor.validate(ValidationProcessor.java:97) [Thread[main,5,main]]: Validatable parameter SP/STACK/LOCATION has been validated by validator RequiredFields.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.util.validate.ValidationProcessor.validate(ValidationProcessor.java:97) [Thread[main,5,main]]: Validatable parameter SP/STACK/LOCATION has been validated by validator SPStackLocationValidator.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.j2ee.phases.jspm.JSPMSpStackQueuePreparator.createQueue(JSPMSpStackQueuePreparator.java:107) [Thread[main,5,main]]: Using SP Stack E:\usr\sap\trans\EPS\SMSDXML_EA4_20100625054857.968.xml.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseStackTag(SPXmlParser.java:488) [Thread[main,5,main]]: STACK-SHORT-NAME tag is missing. The CAPTION of the stack will be used as stack name.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseStackTag(SPXmlParser.java:582) [Thread[main,5,main]]: PRODUCT-PPMS-NAME tag is missing. The CAPTION of the product will be used as product PPMS name.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSPXml(SPXmlParser.java:424) [Thread[main,5,main]]: Parsing of stack definition file E:\usr\sap\trans\EPS\SMSDXML_EA4_20100625054857.968.xml has finished.
Jun 28, 2010 9:21:24 AM [Error]: com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception has occurred during the execution of the phase.
Jun 28, 2010 9:21:24 AM [Error]: com.sap.sdt.j2ee.phases.jspm.JSPMSpStackQueuePreparator.createQueue(JSPMSpStackQueuePreparator.java:136) [Thread[main,5,main]]: The stack E:\usr\sap\trans\EPS\SMSDXML_EA4_20100625054857.968.xml contains no components for this system.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:906) [Thread[main,5,main]]: Phase PREPARE/INIT/PREPARE_JSPM_QUEUE has been completed.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:907) [Thread[main,5,main]]: Start time: 2010/06/28 09:21:23.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:909) [Thread[main,5,main]]: End time: 2010/06/28 09:21:24.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:910) [Thread[main,5,main]]: Duration: 0:00:00.781.
Jun 28, 2010 9:21:24 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:911) [Thread[main,5,main]]: Phase status is error.
++++++++++++++++++++++
[stack xml data: version=1.0]
[SPAM_CVERS]
ST-PI 2005_1_7000006
LSOFE 600 0015
SAP_AP 700 0015
SAP_BASIS 701 0003
SAP_ABA 701 0003
SAP_BW 701 0003
PI_BASIS 701 0003
PLMWUI 700 0002
SAP_APPL 604 0002
EA-APPL 604 0002
SAP_BS_FND 701 0002
EA-IPPE 404 0002
WEBCUIF 700 0002
INSURANCE 604 0002
FI-CA 604 0002
ERECRUIT 604 0002
ECC-DIMP 604 0002
EA-DFPS 604 0002
IS-UT 604 0002
IS-H 604 0003
EA-RETAIL 604 0002
EA-FINSERV 604 0002
IS-OIL 604 0002
IS-PRA 604 0002
IS-M 604 0002
SEM-BW 604 0002
FINBASIS 604 0002
FI-CAX 604 0002
EA-GLTRADE 604 0002
IS-CWM 604 0002
EA-PS 604 0002
IS-PS-CA 604 0002
EA-HR 604 0005
SAP_HR 604 0005
ECC-SE 604 0002
[PRDVERS]
01200314690900000432SAP ERP ENHANCE PACKAGE EHP2 FOR SAP ERP 6.0 sap.com EHP2 FOR SAP ERP 6.0 -00000000000000
01200314690900000463SAP ERP ENHANCE PACKAGE EHP4 FOR SAP ERP 6.0 sap.com EHP4 FOR SAP ERP 6.0 -00000000000000
01200615320900001296 sap.com +00000000000000
01200615320900001469SAP ERP ENHANCE PACKAGE EHP3 FOR SAP ERP 6.0 sap.com EHP3 FOR SAP ERP 6.0 -00000000000000
01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01 +00000000000000
[SWFEATURE]
1 01200615320900001296SAP ERP 2005 sap.com SAP ERP 6.0: SAP ECC Server
19 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Discrete Ind. & Mill Products
20 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Media
21 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Utilities/Waste&Recycl./Telco
23 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Leasing/Contract A/R & A/P
24 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Retail
25 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Global Trade
26 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Financial Supply Chain Mgmt
30 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Central Applications
31 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Strategic Enterprise Mgmt
33 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Human Capital Management
37 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Oil & Gas
38 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Catch Weight Management
42 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Public Sector Accounting
43 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Insurance
44 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Hospital
45 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: SAP ECC Server VPack successor
46 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: ERecruiting
47 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Defense & Public Security
48 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Financial Services
55 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Oil & Gas with Utilities
56 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: Defense
59 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: PLM Core
69 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: EAM config control
9 01200615320900003195EHP4 FOR SAP ERP 6.0_NW701 EHP4 FOR ERP 6.0_NW701 sap.com EHP4 FOR SAP ERP 6.0 / NW7.01: SAP ESA ECC-SE
++++++++++++++++Though we have configured Java in solution manager the stack file that is generated does not contain any java components
You will probably need to update Solution Manager first with a number of corrections so you can get a correctly generated stack file. Depending on your ST400 version in Solution Manager apply collective corrections from "Note 1461849 - MOpz: Collective corrections 24" or "Note 1452118 - MOpz: Collective Corrections 23". They generally deal with these kind of stack file issues.
Nelis -
How to check the current EHP stack level? in SAP
Dear All,
How to check the current EHP stack level? in SAP . i have checked forum before i am posting but still comfused .
same one said SAP_APPL , EA_Appl and SAP _HR is 60n if n=1.2.3.4. if n =1 is enhanced package 1 similarly 2,3,4 .
some one said SAP_BASIS 701,702,703,704 . according ehp1,2,3,4.
Pls check the details and confirm either is ehp1 or ehp4 .
Component version is simply shows SAP ECC 6.0 in system -> status.
Software Component - Release - SP level
SAP_ABA 701 0007
SAP_BASIS 701 0007
PI_BASIS 701 0007
ST-PI 2008_1_700 0003
SAP_BS_FND 701 0008
SAP_BW 701 0007
SAP_AP 700 0021
WEBCUIF 700 0008
SAP_APPL 604 0008
SAP_HR 604 0029
SAP_HRCAR 604 0029
SAP_HRCAT 604 0029
SAP_HRCAU 604 0029
SAP_HRCBE 604 0029
SAP_HRCBR 604 0029
SAP_HRCCA 604 0029
SAP_HRCCH 604 0029
SAP_HRCCL 604 0029
SAP_HRCCN 604 0029
SAP_HRCDE 604 0029
SAP_HRCDK 604 0029
SAP_HRCES 604 0029
SAP_HRCFI 604 0029
SAP_HRCFR 604 0029
SAP_HRCGB 604 0031
SAP_HRCHK 604 0029
SAP_HRCID 604 0029
SAP_HRCIE 604 0029
SAP_HRCIN 604 0029
SAP_HRCIT 604 0029
SAP_HRCJP 604 0029
SAP_HRCKR 604 0029
SAP_HRCMX 604 0029
SAP_HRCMY 604 0029
SAP_HRCNL 604 0029
SAP_HRCNO 604 0029
SAP_HRCNZ 604 0029
SAP_HRCPH 604 0029
SAP_HRCPT 604 0029
SAP_HRCRU 604 0029
SAP_HRCSE 604 0029
SAP_HRCSG 604 0029
SAP_HRCTH 604 0029
SAP_HRCTW 604 0029
SAP_HRCUN 604 0029
SAP_HRCUS 604 0029
SAP_HRCVE 604 0029
SAP_HRCZA 604 0029
SAP_HRGXX 604 0029
SAP_HRRXX 604 0029
EA-IPPE 400 0018
EA-APPL 604 0008
EA-DFPS 600 0018
EA-FINSERV 604 0007
EA-GLTRADE 604 0008
EA-HR 604 0029
EA-HRCAR 604 0029
EA-HRCAT 604 0029
EA-HRCAU 604 0029
EA-HRCBE 604 0029
EA-HRCBR 604 0029
EA-HRCCA 604 0029
EA-HRCCH 604 0029
EA-HRCCN 604 0029
EA-HRCDE 604 0029
EA-HRCDK 604 0029
EA-HRCES 604 0029
EA-HRCFI 604 0029
EA-HRCFR 604 0029
EA-HRCGB 604 0029
EA-HRCHK 604 0029
EA-HRCID 604 0029
EA-HRCIE 604 0029
EA-HRCIN 604 0029
EA-HRCIT 604 0029
EA-HRCJP 604 0029
EA-HRCKR 604 0029
EA-HRCMX 604 0029
EA-HRCMY 604 0029
EA-HRCNL 604 0029
EA-HRCNO 604 0029
EA-HRCNZ 604 0029
EA-HRCPH 604 0029
EA-HRCPT 604 0029
EA-HRCRU 604 0029
EA-HRCSE 604 0029
EA-HRCSG 604 0029
EA-HRCTH 604 0029
EA-HRCTW 604 0029
EA-HRCUN 604 0029
EA-HRCUS 604 0029
EA-HRCVE 604 0029
EA-HRCZA 604 0029
EA-HRGXX 604 0029
EA-HRRXX 604 0029
EA-PS 604 0007
EA-RETAIL 604 0007
FINBASIS 604 0008
ECC-DIMP 600 0018
ERECRUIT 604 0008
FI-CA 604 0008
FI-CAX 604 0007
INSURANCE 600 0018
IS-CWM 600 0018
IS-H 600 0024
IS-M 600 0018
IS-OIL 600 0018
IS-PS-CA 604 0007
IS-UT 600 0018
LSOFE 600 0018
SEM-BW 604 0008
ST-A/PI 01M_ECC600 0001
Regards
Edited by: satheesh0812 on Nov 17, 2011 7:57 AMHi Sateesh,
SAP_ABA 701 0007
SAP_BASIS 701 0007
PI_BASIS 701 0007
ST-PI 2008_1_700 0003
SAP_BS_FND 701 0008
SAP_BW 701 0007
SAP_AP 700 0021
WEBCUIF 700 0008
SAP_APPL 604 0008
Based on the component information provided by you, I can conclude that your system is ECC 6.0 EHP4.
EHP4 is derived from your component SAP_APPL 604.
In addition to this your EHP4 system has NW stack on NW 7.0 EHP1.
Hence your system is ECC 6.0 EHP4 with NW 7.0 EHP1.
Hope this answers your query.
Regards,
Deepak Kori -
Error while downloading the stack file
Hi,
I'm in the process of upgrading my EhP4 system to EhP5.
While trying to generate the file via MOPZ, I just can't seem to "Continue" with the Enhancement package installation option.
The error's as follows:
"Successor installed for SAP SNC 2007."--Check SMSY. (SMSY is perfectly reflecting whatever's installed on the ECC system.)
I just can't figure out where SNC has cm in from.
I do have the component ECC-SE on 604...does this have anything to do with it?
Pls. help..
Thank You,
Saba.Hi Saba,
I've had the same problem as you building the stack file for an EHP5 upgrade and have CPRXRPM version 400 installed. I used you idea of adding SAP SNC 7.0 as an installed product under the ERP system which enabled be to continue the mopz config and build a stack file.
Now when attempting the upgrade I get :-
"The Installation/Upgrade Package for Add-on SCMSNC rel. 700 is not available"
This is not that surprising I guess as its not installed.
Did you also come across this, if so were you able to bypass this?
Thanks
Warren -
EHP4 installation - problem with stack files
Hello all,
I installed ERP 6.0 EHP4 ready and would like to install EHP4 with sapehpi.
I have a problem with my XML stack files because it contains kernel 69 for all os and db.
This stack file has been generated in the MOPZ and MOPZ don't ask me to select kernel files.
I don't see the option Select OS/DB-dependent files in MOPZ.
Solution Manager version is 7.01 SPS23
What would be the solution?
Thanks in advance.
Best Regards,
OlivierHello Markus,
Thanks for your answer.
I fixed the problem by executing once again the following activity in spro. Really strange because I already did it and got the message that the activation was successfull. Anyway if someone encounter this problem, please do the following:
1. Perform IMG activity "Configuration of Extended Functions" (IMG Activity Key: SOLMAN_MOPZ_SLM_CONF), which is delivered as of ST400 SP15.
a) Call transaction code SPRO.
b) Click button "SAP Reference IMG"
c) Use CTRL+F and input "Configuration of Extended Functions" to search for the IMG activity
Noet this: as from ST 400 SP19, use CTRL+F and input "Maintenance Optimizer" to search the IMG activity group, under this group, there is the IMG activity "Configuration".
d) Perform it.
e) If this IMG activity is not available due to a low support package level, see SAP Note 1090202 for manual configuration.
Best Regards,
Olivier -
Stack file is invalid: 'SEM-BW' (stack release 600 source release 602)
Hi experts,
I encountered the following error while patching my BCS SEM system using EHPi.
Servere error(s) occured in phase PREP_EXTENSION/EHP_INCLUSION!
Last error code set: Stack file is invalid: component 'SEM-BW' (stack release 600 < source release 602)
The BCS SEM system is currently installed with SEM-BW 602. But the xml stack file generated by solution manager contains SEM-BW 600. From SMSY, under the Software Components tab, the release for software component SEM-BW is 602.
Where does solution manager obtain the data when calculating the xml stack? How can I generate a xml stack with SEM-BW release 602?
Thanks,
Tzyy MingHi.
When installing this system you have used an installation guide. If i were you i would try to configure the system described in the guide. SAP note 852447 talks about an IInstallation SEM-BW 600 on SAP NW 2004s AS ABAP;
So why not try to configure this system as netweaver as abap in smsy and add the add-ons as relevant. But i am not completely sure - i am at home and can not look to our SolMan system.
I do not think that the configured system should be the problem. You said, the smsy contains the correct data. Did you refresh the product data in your solution manager. That could be the reason why the queue ist not calculated correct ly.
regards,
Martin -
How to setup stack files on desktop
I just got my first macpro and accidently blew away my stacked files that were located on bottom rgt corner of screen. could not find in trash so do not know where it went ... just know that while dragging this stack across screen and released it I saw a cloud icon then it was gone. anyone know how i can get it back or how to setup a stack again...should be easy?
Items in the Dock are just aliases (shortcuts) to the actual files/folders somewhere on the computer. I can't remember exactly what is on the right side by default, but probably the Downloads folder or the Documents folder.
If you want a stack in the Dock, just drag a folder from the Finder to the Dock and the OS will make an alias to the folder in the Dock. When you drag off the dock, you are deleting the alias to the item. if you control-click or click on hold on the folder in the Dock, you can choose the display options that you want it to have.
Stacks only exist in the Dock. You can't move them to the Desktop.
If you want an alias to a particular folder on your Desktop, cmdoptdrag the folder to the desktop. While you are dragging you will see the alias badge (a swooped arrow) indicating you will create an alias, not move the file/folder. Keeping things on the desktop takes up lots more resources than other folders, so it is not a good idea to put a lot of items there.
Message was edited by: Barney-15E -
Stack File for JSPM when using Maintenance Optimizer
Hello,
As you know JSPM looks for a stack file when applying a support pack stack. When using maintanance optimizer I see no way to get a stack file. I end up having to do the work twice: once to get the files in maintenance optimizer, and again I have to go to marketplace swdc to choose the files and create the list of downloads again only to save a stack file.
Am I missing something? Is this double work really necessary?Hello John,
It seems that you are doing double work.
If you use the download type as "SLM" then you have a chance to transfer the XML to SLM. Else if you choose the download type as "Download Manager" then the XML should be created in the EPS/in folder of the Solution Manager system.
You also need to check whether you have applied all the applicable notes for the Solution Manager stack from the note 1122966 and that the BC sets for MOPZ are activated correctly.
Finally check the permissions on the EPS/in folder of Solution Manager to check whether there is a issue with authorizations.
A SLG1 log ( filtered by the username who creates the MOPZ transaction and time at which the transaction was created ) will reveal the errors in the process.
Regards
Amit -
EHP1 Installation - error during the XML stack file check.
Hello SAP fans and gurus.
I'm updating CRM with EHP1 and I'm stuck at the phase PREP_EXTENSION/SUBMOD_EXTENSION_NEW/SELSTACKXML. Something wrong with the XML stack file. I get this error:
Severe error(s) occured in phase PREP_EXTENSION/SUBMOD_EXTENSION_NEW/SELSTACKXML!
Last error code set: Error reading stack info, return Code = -1, Reason = 'The stack configuration is not valid for the system CRM, inst.-no. 0020652601'
The trouble ticket isn't saying much, but I'll post it anyway:
This trouble ticket was created by SAPehpi on 20110520102342
SAPehpi broke during phase SUBMOD_EXTENSION_NEW/SELSTACKXML in module PREP_EXTENSION / Extension module for start release >= 40B
Error Message: Error reading stack info, return Code = -1, Reason = 'The stack configuration is not valid for the system CRM, inst.-no. 0020652601'
Summary of SAPehpi:
SAPehpi Release: lmt_001
SAPehpi Version: 40.005
Start Release: 701
Target Release: 701
Summary of host system details:
SID: CRM
Host: sapvmcrm
MS Host: sapvmcrm
GW Host: sapvmcrm
Start Path: /usr/sap/CRM/DVEBMGS00/exe
Kernel Path: /usr/sap/CRM/DVEBMGS00/exe
Summary of operating system details:
OS Type: Linux X86_64
OS Version: 2.4
Summary of database details:
Database Type: ada
Database Version: 7.7.07.014
Summary of RFC details:
Host: sapvmcrm
GW Host: sapvmcrm
Client: 000
Destination: CRM
Language:
System No.: 00
There's one problem with the file SAPEXEDB_82-10007250.SAR, which was in the download basket, but is not available for download. I deleted the record in the XML stack file and tried the phase again... with no success. Going through the XML file and checking if the packages have been downloaded is a real pain in the ***.
Anyway, can I somewhere download this file SAPEXEDB_82-10007250.SAR?
Or can anyone help me, how solve this issue different way?
Thanks a lot in advance.
-StefanOK, I got it. Wrong installation number. We had to change the installation number in the stack file according the system in the Solution Manager via transaction SMSY. Then it worked like a charm.
-
EHP4 upgrade -- Error at loading stack file
Hi guys,
I have come across an error while upgrading to EHP4, after making a stack file from solution manager maintainance optimiser, I got the error of "no access to solution manager then I gave the path of stack file and it worked. Now it has sever error : Stack file is invalid. (stack release 2005_1_700 < source release 2008_1_700). Thats because after installing EHP4 ready the level of ST-PI is 2008_1_700 and the solution manager is calculating it 2005_1_700.
Any sugestions on it....>
Sunny Pahuja wrote:
> Hi Jawad,
>
> have you checked your Shadow system is up or not ? I think your shadow system is down ..Please check..
>
> Thanks
> sunny
>
Sunny Pahuja wrote:
> Hi Jawad,
>
> have you checked your Shadow system is up or not ? I think your shadow system is down ..Please check..
>
> Thanks
> sunny
Hi Sunny,
the sahdow system is running fine, the rfc is also connected but now it has error on phase MAIN_SHDRUN/ALTNTAB_FILL.
here are the logs
4 ETQ381 request "TP_SHADOW_CONNECT" means "tp needs to connect to shadow system"
4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"
4 ETQ383 translates to path "exe"
4 ETQ383 translates to path "exe"
4 ETQ399 default TPPARAM: SHADOW.TPP
4 ETQ010 Date & Time: 20090616080047
4 ETQ265 Starting report "RDDNT2MT" with variant "SAP_INIT" in batch
4 ETQ359 RFC Login to: System="ID2", Nr="01", GwHost="win-2cc-s-042", GwService="sapgw01"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "SUBST_START_REPORT_IN_BATCH" by RFC
4 ETQ234 Call of function module "SUBST_START_REPORT_IN_BATCH" by RFC succeeded
4 ETQ239 Logging off from SAP system
4 ETQ311 Batch job "RDDNT2MT" with job count "08011600" scheduled
4 ETQ359 RFC Login to: System="ID2", Nr="01", GwHost="win-2cc-s-042", GwService="sapgw01"
4 ETQ232 RFC Login succeeded
4 ETQ010 Date & Time: 20090616080622
4 ETQ234 Call of function module "SUBST_CHECK_BATCHJOB" by RFC succeeded
4 ETQ239 Logging off from SAP system
*1EETQ248 Missing log file(s) of report "RDDNT2MT", matching "RDDNT2MT\.ID2"*
1 ETQ207 Executing post-phase DB specific actions.
1 ETQ207 Executing post-phase OS specific actions.
4 ETQ010 Date & Time: 20090616080622 -
EhP4 Stack file format error in xml
Hi all,
My intention is to Upgrade an sap system 4.6C to Ecc6 including EhP4.
i am running through many problems since now
Here is my newest one:
In solution manager i calculated a stack.xml. After that, i copied the files to the test system which i am upgrading. Now in phase "Stack configuration" i must provide the xml-file.
when i click next, i get an error:
The selected configuration file ("M:InstCds
w70ehp1SMSDXML_P01_20090520113757.307.xml") is not useable.
Reason: "File format error"
Update ....
OK my fault.
in SAP Note Number: 1022704 is the info that in case of start release BELOW 4.6, you cannot use the xml-file, you have to choose the txt-file
Hm .. we have 4.6 which is not BELOW 4.6 but with the txt-file is works ... now i have the next error ...
i tried different files but every time the same error ...
Any idea ?
regards,
Bjoern
Edited by: Björn Trabes on May 20, 2009 4:23 PMSorry,
As i wrote
Hm .. we have 4.6 which is not BELOW 4.6 but with the txt-file is works ... now i have the next error ...
is work for the txt-files in this way, that the stack can be read.
It is a little bit confusing, as the german note says: as of 4.6 and lower
but the english note says: lower than 4.6
so there is a little diffrence
But now i have the Problem, that the generated Stack-file from the solution manager is invalid:
"# Error message set: 'Stack file is invalid: keep version w/o component upgrade'"
Maybe you are looking for
-
Generics and Auto-boxing not working together
Why does the following code produce a compile error: "Type mismatch: cannot convert from char to Character." public class X<Character> { private Character c; private Integer i; public X() { c = 'a'; i = 12; }Note th
-
500 Server Error when executing Query in Portal
When I run a query in the ABAP Web all the components (the pulldowns) work as well as the query executes. When I run the query in the Java WebI get a 500 Internal Server Error com.sap.ip.bi.base.application.exceptions.AbortMessageRuntimeException: Te
-
TableView performance with large number of columns
I notice that it takes awhile for table views to populate when they have a large number of columns (> 100 or so subjectively). Running VisualVM based on CPU Samples, I see that the largest amount of time is spent here: javafx.scene.control.TableView.
-
XRaid Performance Sub-Par for HD Video
Hey Guys....I'm testing out my fully populated XRaid with AJA's Kona 2 System Checker. Starts out great, writing at around 272 Mbps. But then after a few seconds, it drops off to around 60 Mbps. Read times are even slower at around 30 Mbps. Here are
-
Error when open Resouse Viewer form NEBC
Hi experts, I facing a error when opening Resouse Viewer from NWBC. Could you kindy provide some ideas or suggestiongs, Thanks in advance. Best Regards, Matthew He