Solution Manager 7.1 Upgrade - ST add on release Issue

Good day
I have the following issue where the ST add on's are = the target release of the upgrade. The release is only on a higher patch level in 7.1(SPS4)
The step is Configuration(3) in SOLMANUP, it will not get past the phase of deciding to keep the add on's, the error is:
For the following Add-on component(s) the KEEP YOURS decision is not longer valid,
since at least for one of the base components an Add-on upgrade has been included:
ST-ICO     (changed base component: ST)
ST-PI      (changed base component: SAP_BASIS)
ST-SER     (changed base component: ST-PI)
You need to change the decision of the above Add-on(s).
Any ideas?
Thanks

Hi Miguel,
I am using SOLMANUP, I am using the installation/upgrade software and using SPS 4 as my target release. I am using SPS4_upgrade.xml in my download directory.
If I try using SPS 2 with SPS2_upgrade.xml it produces an error because my patch level of ST-PI is already patch 5 in my current system(Solution Manager 7.01 EHP1), and SPS 2 of Solution Manager 7.1 ST-PI = patch 4, that's why I am using SPS 4 stack as it is a higher level that my current patch level of ST-PI.
The issue is that the mentioned ST add-on's are the same release as the target release, the only difference is the patch level. The upgrade recognises that the source and target release is the same, but will not let me keep with Decision = Keep
Thanks
Derek

Similar Messages

Solution Manager 3.2 upgrade to version 7.0

Hello All,
I am in the Solution Manager 3.2 upgrade to version 7.0.
In phase IS_SELECT "Upgrade Assistant" asks to add a few files update
components (Attachment: screens). Two of them (ST-SER and CPRXRPM) I
managed to find and read.
However, in the SAP Service Marketplace I can not find the new Add-On'ów:
ST and ST-ICO.
(For example:
ST - 400,
ST-ICO - 150_700)
Can I skip them in this step and leave the current versions?:
ST - 320 level 19
ST-ICO - 150_620 level 10
Best regards,

Those are part of the normal "upgrade" package - I wonder which DVDs you used to start the upgrade...
SAP Solution Manager 4.0 Upgrade (2) 1 of 11
etc.
Are you trying to do a Netweaver upgrade? This won't work...
Markus

Solution Manager 7.1 upgrade,j2ee_admin is locked

Hello ,
I am in the middle of solution manager 7.1 upgrade and running into execution phase now. but my j2ee_admin password is locked.
I want to unlock and reset the password but this is what happening .:
1. I try to login with old j2ee_admin password but it is not correct.
2. I re-check with updating same to configtool but no luck
3.I have enabled emergency SAP* ID and can login to Visual Admin so
4. when I try to access UserAdmin so that I can unlock j2ee_admin it gives me error as Application error occurred
during request processing
Is there any way to reset /Unlock j2ee_admin even though NWA/ user admin is not available.
Please help me so that I can move ahead with upgrade
Thanks,
Supriya

Hi Supriya,
Hope you are doing good.
What is the status of the upgrade; is the UME still ABAP ? If so just login to the backend ABAP server/client and unlock j2ee_admin.
Else login to visual admin and there is a security provider in the services where you can unlock the user.
Hope this helps.
Kind Regards,
Hemanth
SAP AGS

Solution Manager Enterprise Edition upgrade slow

Hi
I am performing SOMAN 7.0 upgrade to Enterprise edition by upgrading kernel 701 and SP stack 18. I have already upgraded the kernel and java stack and now in the process of upgrading ABAP. I am expereincing really slow performance of this upgrade. I have checked tp and R3trans version which is uptodate as I updated kernel. I cant see any problem with CPU utilization as well swapping. I checked the SLOGs and there are no alerting errors. I see its moving and its very slow. I am just wondering if any of you guys experienced this - is this normal since this is a upgrade?

Thanks a lot, i realize the installation following the standard add-on installation procedure!
Now i have the ST-ETP
ST     400     0024     SAPKITL434     SAP Solution Manager Tool
ST-A/PI     01M_CRM570     0000     -     Application Servicetools for CRM 500 - 7
ST-ETP     100     0000     -     SAP Solution Manager Enterprise Edition
ST-ICO     150_700     0025     SAPK-1507PINSTPL     SAP Solution Manager Implementation Cont
ST-LV     100     0001     SAPK-10001INSTLV     SAP Landscape Verification Wizard
ST-SER     701_2010_1     0002     SAPKITLOS2     SAP Solution Manager Service Tools
Then don't forget to perform step 5. After the installation steps.
Step 5 says this:
5. After the installation
              To activate SAP Solution Manager Enterprise Edition, the Enterprise Addon SM_APPLM has to be activated in the IMG of the Solution Manager System. This is done via IMG activity SAP Solution Manager->Configuration->Scenario-Specific Settings->Activate Solution Manager Enhancements.
            a) In the case of ST-400 SP15-SP17
            To use Extended Tracebility in Change Request Management activate BC-Set SOLMAN40_CHARM_CONTEXT_001 in transaction SCPR20
            b) In the case of ST-400 SP18 or higher
            The activation of BC-Set SOLMAN40_CHARM_CONTEXT_001 will be done automatically.
In my spro i don't have this options->
I see the route Activate Solution Manager Enhacements in SPRO -> Cross Scenario Settings
And in enterprise extension I only see ( SM_CRON, SM_QC_AD, SM_SSP,SM_SUPP_VAR)
I guess that this in SP24 is done automatically, but you said, that don´t forget the step 5 after installation.
update:I check for updates of SP and this add-on don´t have SP for now

Solution Manager 3.2 Upgrade problem.

Hello all.
I am trying to upgrade Solution Manager 3.2 to version 4, my OS - Solaris 9 on SPARC, RDBMS - Oracle 10.2.0.2
On phase TR_QUEUE2HEAP of PREPARE module a get an error:
ERROR: Unable to expand queue.
       Return Code = -1, Reason = "Internal error: Attribute set 01 is missing for OCS package is missing for OCS p"
Check log file 'SPDA_EXPAND_QUEUE.LOG' for details.
SEVERE ERROR: (R3uppat.c:22890) RC = RC_ERROR
continue
cancel
After I select "Contunue", a get a "SEVERE ERROR(S) OCCURRED IN TR_QUEUE2HEAP !!!"
I cant find file SPDA_EXPAND_QUEUE.LOG.
This is log from TRQUEUE2HEAP.LOG:
1 ETQ201XEntering upgrade-phase "TR_QUEUE2HEAP" ("20070222162516")
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '02', GwService = 'sapgw02'
4 ETQ399 Environment variables:
4 ETQ399   dbs_ora_schema=SAPSM4
4 ETQ399   auth_shadow_upgrade=0
4 ETQ399 (trc) R3upExtendedInclusion: TRUE (default)
4 ETQ399 Parameter "spam_queue_with_syncmarks" has been reset from SAPup parameter file
4 ETQ399 (trc) Syncmark handling done by SPAM (gpv_spam_queue_with_syncmarks=TRUE)
4 ETQ399 (trc) R3upQueueExpand: Expand mode = REQUEST
4 ETQ230 Starting RFC Login to: System = "SM4", GwHost = "r3devsrv01", GwService = "sapgw02"
4 ETQ359 RFC Login to: System="SM4", Nr="02", GwHost="r3devsrv01", GwService="sapgw02"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "SPDA_EXPAND_QUEUE" by RFC
4 ETQ010 Date & Time: 20070222162517
I cant find any notes or messages regarding this error.
Please help me !

Dolores, may be You can help me once more ?
Next problem : phase Conflict Check,
Conflicts found.
       Check log file 'SPDA_CONFLCHK.LOG' for details.
       To resolve the conflicts you must repeat the module and change your Add-on or
       Support Package selection or add Conflict Resolution Patches (CRT).
From SPDA_CONFLCHK.LOG:
2EETN388 The following CRTs of the Add-On "ST" rel."400" must be included as well:
3WETN389 CRT &4"SAPKITL412" for Support Package &1"SAPKB70006" of the Software Component &2"SAP_BASIS" rel.&3"700"
3WETN389 CRT &4"SAPKITL414" for Support Package &1"SAPKB70007" of the Software Component &2"SAP_BASIS" rel.&3"700"
How I can add those CRT 's ?
I have unpacked them to EPS/in, but it didnt help me.

Solution Manager 7.1 Upgrade: Problems during LMDB Setup

Hi,
we upgraded our Solution Manager 7.0 EHP1 development system to 7.1 SPS3 (including all new sap notes).
During solman_setup we get the following error at -> System Preparation -> 6 Prepare Landscape -> 6.4 Set up LMDB:
No such namespace: "active"
Due to this error it is not possible to add a synchronization connection between our local SLD and LMDB, because there's no target namespace!
Does anyone know how to add the namespace "active" ??
Greetz
André Richter

Make sure that your SLD meet the requirements:
SAP NetWeaver Release
The following table gives an overview of the SAP NetWeaver versions for an LMDB-compatible SLD, and whether, and since when (which support package stack), an SLD satisfies the minimum requirements for LMDB:
SAP NetWeaver Release (SLD)
Supported Support Package Stack Level
SAP NetWeaver 6.40
not supported
SAP NetWeaver 7.0
not supported
EHP1 for SAP NetWeaver 7.0
not supported
EHP2 for SAP NetWeaver 7.0
SP6, patch 5
SAP NetWeaver 7.1
SP9
EHP1 for SAP NetWeaver 7.1
all SPs
SAP NetWeaver 7.2
all SPs
SAP NetWeaver 7.3
all SPs
If you cannot give your central SLD a required status, you can use another SLD which does satisfy the minimum requirements (e.g. the SAP Solution Manager SLD), and fill it with the data from your central SLD, using SLD bridge functionality.
Model and CR Content
The CIM model and SAP CR content requirements are:
 CIM model 1.6.16 or higher
 Newest SAP CR CONTENT, at least version 7.0
For more information about updating CR content, see SAP Note 669669.

Solution Manager 7.1 upgrade or configuration in Solman 7.0 EHP1

Hi,
We have a Solution Manager 7.0 EhP1 and there is a project now to configure several functionalities on it such as Charm and Services desk among others. We have the option of configuring all the functionalities in SOlman 7.0 EHP1 or upgrading to 7.1 and then configure the functionalities in the new version.
I would like to know if anybody has implemented an upgrade of Solman 7.0 EHP1 to Solman 7.1 with some functionalities implemented.
I would like as well if in the fact the the Solman 7.0 EHP1 has several functionalities implemented complicates the upgrade to Solman 7.1. The fact that the upgrade is more complicated due to all the functionalities configured, would be important factor to upgrade to 7.1 instead configure it in 7.0 EHP1.
Any information about this would be appreciated.
Many thanks in advance!
Raquel

Newer functionality and more holistically speaking, an ALM Tool, arguably one of the best in the market should be more than enough to take you to 7.1
if all you have is EWA, there is no major risk associated, the new 7.1 has new transaction types for ChaRM and Service Desk, the functionalities of which are better rounded and can support more enterprise wide processes.
Graphical Business Blueprint tool, my favorite feature in 7.1 and enhanced features in Project Implementation tools will only help you manage your implementations/support projects better.
If all you have is EWA, I have half a mind to ask you to do a fresh install, and not bother with the upgrade. Saves you time and lot of effort as well.

Solution Manager 3.1 upgrade to 3.2

Hi,
I have to upgrade Solution Manager to 3.2 SP Stack 15 or 7.0 SP Stack 09.
Now I have Solution Manager 3.1, in detail: SAPKB62052 and SAPKU31010
How can I do it?
My problem is:
I have to upragde Solution Manager because I have on my notebook Microsoft Internet Explorer 7.0 so SAP GUI doesn't display F1, F4 and so on.
I know it's the html problem, I want to use note 950975 but from last year due to this note I can do it only by Solution Manager
u2022     SAP Solution Manager 7.0 SP Stack 09
u2022     SAP Solution Manager 3.2 SP Stack 15 (with limited functionality)
So the first I have to upgrade SAP Solution Manager than implement the note.
Regards,
Betta Woroch

Hi,
I use 620 GUI because it was installed in 2005 when SAP was started in my company.
I use F1 when the focus is in field e.g. in transaction AS01 field ANLA.ANLN1
The same problem occurs in SBWP transaction, there the message is not display content.
In SR13 transaction is only one item: PlainHtmlHttp:
Variante: IWBHELP1
Platform: WIN32
Area: IWBHELP
Server names: HELP.SAP.COM
Path: saphelp_erp2004/helpdata
Language: EN
Default: Yes
In my company is SAP Fixed Assets:
SAP_BASIS SAPKB62048
SAP_ABA     SAPKA62048
SAP_APPL SAPKH47022
This problem occurs after upgraded Microsoft Internet Explorer to 7.0 in my notebook. There is Win XP Professional SP2
Regards
Betta Woroch

SAP Solution Manager key during upgrade

Hi,
Im upgrading my 4.7 Enterprice system to 7 (ERP)
When running the PREPARE im struggeling with the upgrade key from solution manager.
I have generated a key but it Sapup tells me its wrong.
I have deleted the system from smsy and the run the Landscape fetch job again but still I get the same key.
Any ideas?
BR
Henrik

>
Henrik Axelsson wrote:
> Hi,
>
> Yes i have entered
>
> LC2
> 43
> lc2as00 (linux-hostname)
>
> BR
>
> Henrik
If you provide these 3 values it will generate always same key only. please check once system number and host name?
Thanks,
Siva

About Solution Manager upgrade from 3.1 to 4.0

Hi colleague,
I am in progress of finalizing a planning for an Upgrade project of Solution Manager from 3.1 to 4.0 release.
The current usage of the Solution Manager usage is the following :
- Only Blue Print and Implementation function used,
- No modification (no repair),
- Very few customizing : document type, key word,
- More than 300 User : BRIDGE Program at Schneider Electric customer that uses Sol Man as implementation enabler and tool is very huge, with many SAP component - ECC, CRM, BW, SRM, EP, APO, XI ; + scope is all SE business organization worldwide,
- We us Template approach (Template Project + Implementation Project per Roll Out),
- DE/EN/FR installed and FR supplemented with EN,
- Landscape is mapped,
- We use Blue Print, business structure, few project administration function, IMG activities linked to Project/Structure, Dev objects linked to Project/Structure, documentation linked to Project/Structure, customizing distribution,
- There are around 6000 documents stored in 2 used Project (one Template, other Implementation).
Current plan is to perform 2 upgrade :
- One on a SandBox Sol Man on which we will have before copied the Sol Man plateform used for project implementation task,
- Another on the Sol Man plateform used (final).
Strategy is in a first step to perform an upgrade without implementation of additional/new Sol Man functions (to see and qualify in a further phase) : iso functionality is the strategy.
Now my concern / question.
I did estimate roughly the upgrade duration and workload to 3 days (only for upgrade, not for preparation, pre-step, post-steps, validation, ...,
I would like to know if such estimation is realistic, and if I have to check and pay attention to particular concern (I already collected all relevant SAP Note like 892412, 914910, 834534, ...).
I expect to have after upgrade the same content, without any bad surprise.
Thanks for your collaboration.
Regards.
Philippe Boyer SAP France (Project Management Team)

Hi,
I guess by now you would have started your upgrade. Sorry for the delay. That's a realistic/achievable estimate, goahead. Any specific queries about upgrade? feel free to revert back.
--Ragu
Downloading and installation of patches would consume more time.
Message was edited by:
Raguraman C

How to use solution manager in upgrade projects

Hi,
How to utilize/use the solution manager in upgrade project like R/3,BW,CRM or entire landscape.
if we are upgrading the r/3 4.6c to ecc6 and bw3.5 to bi7.0 how to use the solution manager
please help and thanks in advance.
Edited by: MAHIPAL REDDY on Jan 1, 2009 1:28 PM

Hi,
Check [this document|https://websmp208.sap-ag.de/~sapdownload/011000358700002696532005E/310_320_SOLMAN_URMP_EN.doc]. This will help you to proceed further.
This is a detailed documentation on using Solution Manager for your upgrade project.
This will solve your problem.
[This Pdf |https://websmp208.sap-ag.de/~sapdownload/011000358700000208052007E/Upgrade_FAQ_SolMan_70.pdf]of FAQs on upgrade project is rich in information.
Feel free to revert back.
--Ragu
Edited by: Raguraman C on Jan 3, 2009 5:27 PM

Solution Manager Stack upgrade

Hi,
I am downloading patches for Solution Manager 4.0 from stack 06 to stack 09.
However in the step 3 of download I am not getting new levels of components ST-SER.
Where as if I try to move from stack 06 to stack 08 I get 2 new levels of components ST-SER.
In the schedules for SP Stack 07 and 08 I can see levels SP04, SP05 and SP06
and in SP Stacks 09 it shows levels 700_2006_2 SP00 and 700_2006_2 SP01.
Any idea why I am not getting components of ST-SER when I try to upgrade from stack 06 to stack 09.
Thanks
Parvez Khan

Hello,
It indicates that your solman has java stack installed and you have to download java stack patches as well.
Please follow the solman ehp1 upgrade guide from service marketplace path given in following links and try to understand the process through some other links/search as well
Query related to Solution Manager 7.0 Upgrade to EHP1
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f09c8455-4036-2c10-c7a7-bc3c0879462b?quicklink=index&overridelayout=true
Solution Manager EHP1 Upgrade
Thanks

How does Solution Manager manage upgrade?

Except get the upgrade key from SM4.0, I do not see any other involvement of SM4.0 in the
upgrade.
However in a recent paper by Jon Reed , he says that you can use SM4.0 to manage your
upgrade.
Please share your opinions. Thanks!

Solution Manager's module Implementation Tools can help to you conduct from a "Fuctional" point of view your entire Upgrade project, further more can help you to rollout if necessary the Upgrade.
For Upgrade Projects the SAP Solution Manager supports both:
- restarting an upgrade project
- perform an upgrade project based on an implementation project
The scope of support for these upgrade-relevant activities with the SAP Solution Manager is the same as for an implementation project, plus some upgrade-specific functions:
a comparison tool which identifies release-specific changes or deletions, if you used SAP reference contents
an upgrade report which gets the upgrade-relevant configuration settings which you must adjust in upgrade or delta customizing, automatically, based on a connection to the target release system
Upgrade-relevant contents are also delivered with the SAP Solution Manager, as an upgrade roadmap and upgrade-specific business scenario and process contents. At the end of the upgrade project, changed or inserted business scenarios and processes and system information are put in a customer-specific repository (Solution Directory), where they are available for production processing.
Extracted from www.help.sap.com

1 Solution Manager System - Mulitple Companies.

Hi All,
Please provide some input/information regarding one Solution Manager system with multiple companies.
Situation:
We currently have one Solution Manager system(SMP) that belongs to a main company. Under this company there are 5 separate companies. Each company including the main company has multiple SAP systems with different landscapes. Main Company - ECC6 landscape, BI 7.0, Portal, XI and HR Landscape. All other companies have their unique systems/landscapes with their own support personnel.
Issues at hand:
How do we setup Solution Manager to run multiple companies? Do we setup different Solution Landscapes and add each company systems to their own landscapes. How does this effect Service Desk/Charm setup ?
We also want to implement Service Desk / Charm / EWA and all the other functionality that is available in Solution Manager. Is there any advise on this issue and what are the potential pitfalls.
Is it possible to be setup multiple clients and have each company work in its own client.
I would appreciate any advice and information that will assist us with making an informed decision on the best way to proceed with this. I have done research and cannot find any information pertaining to this type of scenario. I'm hoping there are other customers that have a similar problem/issue.
Thanks and regards,
Ricky

Dear Ricky,
You are right. You sould create multiple solutions u2013 a solution for each company. Each solution comprises the landscape (systems) relevant.
I don't think setting up multiple clients and have each company work on its own client is a good idea. The solution manager supports monitoring and managing multipal solutions. By creating multiple clients you are loosing the advantage of one-point-of-entery. Besides, a lot of the customization in the SolMan is cross client.
Regarding the service desk:
You may create a sold-to-party business partner for each of the companies (transaction BP) and assign each sold-to-party only to the relevant system/iBase in transaction IB52. This will allow you to screen the messages in the service desk by a sold-to-party/company.
Regarding the EWA:
The EWA monitors the systems in the solutions. You may have as many solutions as you want.
Regarding the Charm:
Sorry, we didnu2019t implement it yetu2026 you should keep asking abour that.
If you would want to use Business Process Monitoring - this is solution based, so I don't see any problem there.
Hope it was helpful.
Good luck!
Adi Skutelsky

Please suggest on: SAP Solution Manager Installation

Hi Experts,
We are going to install SAP Solution Manager in our landscape. Our present SAP version is: ECC 6.0 and Database is: Oracle 10.2.0.2 and OS is: AIX 5.3
1. Please suggest us which is the suitable Solution manager version for our environment?
2. What are the pre-requisites and needful steps to take before starting the installation?
3. Where can I get complete step by step documents for this activity?
4. Which OS & DB is suitable for our environment?
Thanks in advance!
Veera

Can I also ask for some confirmation about a couple of things. I have looked at the SAP documents but I can't find a definite answer to these questions:
1. David Kroone - you say that Solution manager should be set up on a new server but I understand that it is possible to run it on one of our existing R/3 servers. Is this correct? Does anyone have any comments about this?
2. David - you also say that we can pick any OS & DB for the Solution Manager server. We are running R/3 on Oracle/Solaris but would prefer to run Solution Manager on a Windows server running SQLServer. Is this definitely OK? (it would be cheaper though you advise that using the same platform could make it simpler - is this because Solution Manager works better on the same platform or is it just because we would then have a more homogeneous environment?)
3. We are currently on 4.7 but plan to move to ECC6 this summer. We want (need?) to install Solution Manager before we upgrade to ECC6. Should this affect our decision in anyway?
Sorry to re-ask the same questions but it's difficult to find a precise answer in the SAP documents.

Solution Manager 7.1 Upgrade - ST add on release Issue

Similar Messages

Maybe you are looking for