Uninstall Solution manager 4.0

Dear All,
Solution Manager's Data disk crashed. Now I have replaced HDD and want to reinstall SM with same SID and DBSID. But it show error with it.
Once I have started with change SID and DBSID its stucking at ports, which are being used by older one SID/DBSID.
Now I want uninstall my old Solution Manager, while Database is already lost due to HDD crash. I am facing problem due to system configuration/software setting/registry on C: drive.
I don't want to format complete system.
Please let me know how uninstall old Solution Manager. I also want to use same SID/key/Lic on same machine.
Regards
Dharmendra

Hi,
to Remove SAP from Windows follow below steps:
1) remove entries of sapms<SID> and other <SID> related entries from services file located in C:\WINDOWS\system32\drivers\etc
2)Deregister services related SAP from registry
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
3) remove environmental variable related to SID from System Properties.
4)restart system.

Similar Messages

Solution Manager Install Error

Hi All,
I'm trying to to a clean install of Solution Manager 4 on Windows Enterprise Server 2003 SP1, SQL Server 2005 SP1.
I've run the Pre-Installation Check and all is OK.
At Step 10 of 42, Create/modify database schema I'm getting an error:
ERROR 2006-09-22 17:01:59
FCO-00011 The step CreateDatabase with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|9|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssSchemaCreate|ind|ind|ind|ind|9|0|CreateDatabase was executed with status ERROR .
Can anyone help?
Thanks in advance,
Nic

We resolved the problem.
Problem:
Installation of 7.0 using MaxDb on Windows x64 hangs on the sapinst at the step CreateDbSchema..
There is no error in the installation log.
We are using the specified JDK (JAVA development kit) as specified by OSS Note 723909 which is downloaded from a special website of SUN.com.
We have tried uninstalling the other versions of the JDK build and tried other builds.
Solution:
By searching message boards for the specific error CreateDbSchema, one of the threads mentioned that passwords for MaxDb can't have special characters. Searching OSS yielded a Note 674430 which confirmed that installing on MaxDb has to use alpha-numeric. We were using an @. We dropped the database and deleted the user so it would be a clean install, and ran again using a different password. Some other cleanup was done too, but we suspect it was the password.

Can't Install Solution Manager on Suse Linux Enterprise Server 10 - JAVA

Hello everyone!
I've been trying to complete the pre-requisites in order to install Solution Manager SR2 on Suse Linux Enterprise Server 10 x64 - SP1.
There's only one last condition that I haven't met, and it's the Java Runtime Environment version...
I checked the recommended note 867110 and it says that i need to have installed the J2SDK 1.4.2_08.
SLES10 includes the 1.4.2_13, so I had to uninstall it, and download the right version from Sun Microsystem's official webpage.
When I installed the version 1.4.2_08, i'm not able to run SAPINST because there's no Java Runtime Environment running on the server.
I started to investigate and I found in some forums [NOT EXPLICITLY] that there's no port for J2SDK 1.4.2_08 on x64 linux systems.
I can't believe this is true because SLES10 is recommended by SAP to install Solution Manager, so I hope somebody can help me on this.
My specific question is: Does anybody know if is true that J2SDK 1.4.2_08 is NOT COMPATIBLE with x64 Linux?
In case of being true, is there any way to be able to run SAPINST ? because if I enable the version SLES brings built in, i'm able to run the SAPINST but it detects that i'm not running version 1.4.2_08 and doesn't allow me to continue installation.
I hope somebody can help me soon...
Regards!

> SAPINST_JRE_HOME=/opt/IBMJava2-s390-142/jre/bin:$PATH
>
> JAVA_HOME=/opt/IBMJava2-s390-142/jre/bin:$PATH
You downloaded the wrong version - the one you have is for Z-Linux(Linux running on the mainframe - not for x64).
You need to download the x86_64 (or AMD64) version.
Install the correct one and try on a new console:
export JAVA_HOME=/opt/IBMJava2-amd64-142
export PATH=$JAVA_HOME/bin:$PATH
Then execute
java -fullversion
and it should show the correct version.
Markus

Solution Manager 4.0 install error logging in for DDIC step 29

Has anyone else seen the error 'Test logon to SAP System <sid> failed"? It states that it cannot login for DDIC. This is at step 29 during the install of the solution manager 4.0.
We are running on a Windows 2003 Server/Oracle 10g.
Any help would be greatly appreciated. We've been hitting this same error for the last couple of days.
Thanks,
DBB

Dear Derrick,
I have run into the exact same problem!!!!
During step 29 of the install does it ask you to enter the DDIC password?
It will ask you twice for a password if both the times the login fails then you will have no other option but to uninstall and reinstall Sol Man 4.
The tactic that worked for me is that when it will ask u the passowrd the first time.......before you enter the password.......login in to Sol Man 4 using the default DDIC password 19920706. then change the default password. And then go back to the install and give this new ddic password.
This is the only thing that worked with me.
Let me know if anything else works.
Email me @ [email protected] if you have any other questions.
thanks
Mikir

Error in RFC SM_DM1CLNT800_BACK to Solution Manager System Message no. STMWFLOW025

Hi,
I am facing an issue in our Test landscape. One of our team member uninstalled solman system which was connected to all other system. CHarms was partly configured in it, so other technical team used to reach to solman for creating TR# and also release the TR from Solman. Now that the system was removed abruptly we are facing this issue and I have checked few things as below:
1) Checked for domain link entries in STMS and TP profile file, could not find anything. Nor there is any option to delete domain link as there is for create
2) Checked the RFC its was working as new Solman with the same host name and other details has been brought back with out any settings yet in it.
3) I deleted the RFC SM_DM1CLNT800_BACK in the managed system and had a backup copy created before deleting it. But still get the error "Error in RFC SM_DM1CLNT800_BACK to Solution Manager System" in more help I see this Message no. STMWFLOW025
4) Message no. STMWFLOW025 - It gives me an indication that this is something to do with the domain link and the Workflow of the TMS.
5) Checked BCOS_CUST table and it has an entry for this RFC. - Should I be removing this entry and will this resolve the issue?
I need help in resolving this issue and also if one of you could share a blog for the proper configuration removal process of a managed system from Charms and ITSM I think it would be very helpful. I could only find process and step towards configuration and not how to unconfigure the system.
Thanks in advance
Ashish

Hi
The issue is now resolved, this is how I did it.
1) Removed entries from BCOS_CUST from client 000 for OSS_MSG which was pointing to the RFC name
Then got another error:
No RFC connection to the central lock information management system.
The project lock functionality is active in the local system, but there is no RFC connection to the Solution Manager system.
2a) Ran the report in SA38 TMW_CONTROL_PROJECT_LOCK with selection for Deactivate the "project lock functionality".
2) Filled the "Deactivate Project Lock" field with "X" then clicked EXECUTE.
Problem got Solved.
Thanks
Ashish

ABAP sneak preview (NSP) patch without Solution Manager after patch 11

I'm wondering if there is any plan to allow us ABAP sneak preview users to patch our system beyond patch level 11. So far I kept my NSP system up-to-date by patching it regularly. But now the Solution Manager is required to download the current patch level 12.
Is there any SolMan sneak preview available? Is there any add-on to upgrade the NSP itself into a SolMan system? - After all SolMan runs on 2004s ...
I noticed that trial version with SP12 is out - does this mean that the new strategy is to replace with each and every SP the Sneak-Preview-System? If there wasn't the lengthy (and often painful) setup I wouldn't mind. On top one would have to export and re-import all developments and configurations one would like to keep. Can you (SAP) not simply provide for us non-SolMan-havers the Service Packs as a simple and much more compact download (compared to the entire NSP download) ?

Hi George,
Try to delete the registry keys mentioned here Re: How to uninstall Netweaver 7.0 ABAP trial version ?
To use it, run the clean up tool for the registry, press the radio button for 'Uninstall Service', enter 'NSP' for SID and '00' for the number.
This will only delete the registry entries for the application server, not for the database.
To access the DB via MMC, the service <b>SAP DB WWW</b> must be started. To do so, go to 'Start'->'Run...' and enter 'net start sapdbwww'. After the service is started, you can use the database manager within SAP MMC or just browse to <a href="http://localhost:8000/sap/bc/gui/sap/its/webgui?sap-client=000">http://localhost:8000/sap/bc/gui/sap/its/webgui?sap-client=000</a>, which will actually use the same HTML UI.
Anyway, if the uninstallation runs normal, you shouldn't have any problems with registry keys.
Try this:
- Unistall system and DB
- Use the registry clean tool
- Delete the folder of InstallShield (usually C:\Program Files\Common Files\InstallShield\Universal\SAP)
- Reboot your system
- Start the installation again without running any application (no firewall, antivirus etc.)
Hope this helps.
Regards,
Klaus

Can't repair or uninstall Desktop Manager Software

I'm trying to uninstall Desktop Manager 5.0.1 , When I tried to uninstall using the typical Add/Remove Programs from Control Panel, it appears the following error:
"Could not access VBScript run time for custom action"
How can I repair or uninstall the Desktop Manager??
Solved!
Go to Solution.

vermontgolfer wrote:
Am experiencing the same problem. I recently upgraded to Desktop Software 5.0.1 and somehow never properly uninstalled v4.2. I now have both on my system and am getting an annoying Roxio Message, each time I start my computer, which only started after this upgrade. I have tried repeatedly to uninstall version 4.2. It goes thru the process, but at the end I get the following message:
Error 1316.A network error occurred while attempting to read from the file C:\Windows\Installer\Blackberry Desktop Software's
I have complete Administrator authority, so that is not a reason.
The new 5.0 Desktop Software is working fine, but again, I think this Roxio pop up installer message is related to either not properly installing 4.2 or having multiple DM on my computer.
Any help is greatly appreciated.
Thanks.
Hi and Welcome to the Forums!
Given what you describe, I suggest the following steps (insert plenty of reboots of your PC...not just restarts, but full power down reboots). Also, it is advised that you be logged into the PC on an account with full admin rights. Further, under Vista/Win7, use the "Run As Administrator" option for everything.
1) Remove all device OS update packages from your PC (add/remove programs)
2) Cleanly uninstall any and all versions of the RIM DTM software:
KB02206 How to perform a clean uninstall of BlackBerry Desktop Software
Some have reported that there are more registry keys to remove than are discussed in that KB
Others have reported the use of a registry cleansing tool to also be helpful
You may further need to dig for and remove anything that is remotely Roxio...those can be somewhat hard to find at times.
3) Get a fresh download of the RIM DTM software:
https://www.blackberry.com/Downloads/entry.do?code=A8BAA56554F96369AB93E4F3BB068C22
Choose the version that is newest and (if applicable) compatible with your PIM (if you are synchronizing via USB):
KB12268 Applications supported by BlackBerry Desktop Manager for synchronization
If you don't really need Media Manager, then don't grab the version with it.
4) Download (to your PC) a fresh copy of your device OS package from your carrier:
http://na.blackberry.com/eng/support/downloads/download_sites.jsp
5) Install DTM to your PC
6) Install (also to your PC), the device OS package
7) Start the organizer configuration over:
KB17022 How to configure organizer applications for synchronization using BlackBerry Desktop Manager
Hopefully that will get things going again.
Good luck and let us know!
Occam's Razor nearly always applies when troubleshooting technology issues!
If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
Join our BBM Channels
BSCF General Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

How can I change the Solution Manager to Unicode?

Hi,
I have a no-Unicode Solution Manager... to make this system Unicode I need to re-install the system again or I can do this with some process or notes?
Thanks for the help!

The best resource for these procedures is http://service.sap.com/instguides. Every installation guide normally has a section near the end that describes the uninstall procedure. In a Windows environment, it is done through Control Panel -> Add/Remove programs. In a Unix environment, it is done using SAPINST.
The difference between Unicode and non-unicode during the installation is the check box that appears during the parameter entry. By default, it is normally checked to indicate that this will be a Unicode installation.

Create a Support Message in Production system showing up in Solution Manage

Has anyone setup the link between creating a support message (under help) in a production system (like ECC) and SAP's Solution Manager.
I understand that it uses BADI SBCOS001 with the interface method PREPARE_FEEDBACK_BO, but when I try to run it, it tells me that Customizing for feedback functionality missing. What functionality is missing? And how to I correct this? And how do I ensure it shows in SAP Solution Manager under a solution or project?
Thanks
Paul

Hi Paul
The only way is to use the IMG. I have just completed this via the IMG info. BUT, it is not that simple.
Make sure your RFC's are trusted and that you have SAP ALL during config.
I hope this will help:
Setup Service Desk
Steps to follow while configuring support desk.
1) Implement the note 903587 .
2) Create all the relevant RFC objects in the satellite system and add the appropriate logical components using transaction SMSY.
3) Check all the objects in the table BCOS_CUST using transaction SM30.
Appl : OSS_MSG
+ :W
DEST :BACK RFC NAME (for solution manager system keep this field as 'NONE')
+ :CUST 620
+ :1.0.
*4) Check whether the BC sets are activated or not using the transaction SCPR20.If the BC sets are not activated then implement the note 898614.The steps to activate the BC sets are described below
4.1) Activate SOLMAN40_SDESK_BASICFUNC_000 BC Set.
4.2) Activate this in expert mode with option u201COverwrite everythingu201D.
4.3) Activation of the following components has to be done by replicating the previous steps
3.1) SOLMAN40_SDESK_TPI_ACT_AST_001
3.2) SOLMAN40_SDESK_ACTIONLOG_001
3.3) SOLMAN40_SDESK_ACT_ADVCLOSE_001
3.4) SOLMAN40_SDESK_TEXTTYPES_001
*Depends upon the number of inactive BC set objects that we have after the upgrade.
4.4) if the actions mentioned in 4.3 are not listed while executing the transaction SCPR20, then implement the note 898614.In the source client 000 of the solution manager system create a transport request using transaction SE09, unpack the file 'PIECELIST_SERVICE_DESK_INIT.ZIP' from the attachment of the note. Copy the contents of the file 'PIECELIST_SERVICE_DESK_INITIAL.TXT' to the transport request. And activate the actions. Use transaction SCC1 to import the transport request to the solution manager client. If any short dump occurs during the activation, implement the note 939116.
5) Check whether the number range is set correctly. If not set the number ranges of basic notification (ABA) and the support desk message (Service transaction SLFN).To be able to use the same number ranges for both message types, the internal number range for basic notification (ABA) must correspond to the external number range for the support desk message.
Number ranges for ABA notifications
5.1) create an internal and external number range using transaction DNO_NOTIF.
5.2) assign number range intervals to groups internal and external.
5.3) SLF1 is the internal number range group
5.4) SLF2 and SLF3 is the external number range interval
5.5) Use transaction DNO_CUST01 to assign message categories to the number range.
5.51) Go to transaction DNO_CUST01
5.52) From the GOTO menu select the menu item DETAILS
5.53) Now you can assign the number range of basis notification (ABA) into the notification type.
The number range for ABA notification is 12 characters in length and to make it compatible with the CRM service transaction insert 2 ZEROES at the beginning.
Number ranges for Support Desk notification
5.54) Use transaction CRMC_NR_RA_SERVICE, and define the internal and external number ranges. Intervals must correspond to the intervals of the basic notifications (ABA notification).
5.6) Then assign both the external and internal numbering
5.61) Go to SPRO and then to SAP Solution Manager
5.62) Then select General Settings and then select Transaction types
5.63) Select the transaction type SLFN and then select the menu item DETAILS from the GOTO menu.
5.64) In the Transaction Numbering block, assign the internal and external number range. The Number Range object should be CRM_SERVIC.
5.7) To view the priorities use transaction DNO_CUST01 and select the notification type as SLF1 and then select priorities from the left pane of the screen. The priorities of the first four cannot be deleted, but new priorities can be added.
6) Check the Action profiles for ABA Notifications (Action profiles are used for synchronization of ABA notification with the CRM Service transaction).
6.1) To check the action profiles use the transaction SPPFCADM and select the application type DNO_NOTIF then select u2018DEFINE ACTION PROFILE AND ACTIONSu2019.
6.2) Select the item u2018SLFN0001_STANDARD_DNOu2019 and then from the menu GOTO, select the menu item DETAILS.
7) The Action profile u2018SLFN0001_STANDARD_DNOu2019 has to be assigned to the message category SLF1 (ABA notifications) using the transaction DNO_CUST01.
8) The action profile for the support desk message can be set to u2018SLFN0001_ADVANCEDu2019.
8.1) From SPRO select SAP Solution Manager then Scenario Specific Settings.
8.2) Select the item Service Desk and then to general settings.
8.3) Execute the category u2018Define Transaction Typesu2019.
8.4) Select the transaction type as SLFN
8.5) From the GOTO menu select the menu item u2018DETAILSu2019 and assign the action profile as SLFN0001_ADVANCED .
9) Activate the partner/ Organization
9.1) Go to CRM->MASTER DATA->BUSINESS PARTNER->INTEGRATION BUSINESS PARTNER ORGANIZATION MANAGEMENT->SET UP INTEGRATION WITH ORGANIZATIONAL MANAGEMENT.
9.2)Find the entries starting with HRALX
HRALX-HRAC WITH VALUE 'X'.
HRALX-OBPON WITH VALUE 'ON'.
HRALX-PBPON u2018ONu2019.
HRALX-MSGRE u2013 u20180u2019.
9.3) If entries are not found create it.
10) Generate Business partner screens
10.1) Go to transaction BUSP.
10.2) Execute the report with the following parameters
CLIENT - Client in which business partners should be created (solution manager client)
APPLICATION OBJECT-
SCREEN - *
Generate all/ selected screens - All screens.
delete sub screen containers -
11) implement SAP note 450640.
11.1) Go to transaction SA38 and select the report CRM_MKTBP_ZCACL_UPDATE_30.
11.2) Execute it with test mode box unchecked.
If a new relationship is to be created then steps 12 and 13 has to be followed
12) To create a relationship category
12.1) Go to transaction BUBA
12.2) Select the entry CRMH00: Undefined relationship
12.3) click on copy
12.4) Rename CRMH00 to ZCRMH00.
12.5) CREATE A RELATIONSHIP CATEGORY.
IN GENERAL DATA FILL LIKE ' FROM BP1 : HAS THE ACTIVITY GROUP '.
' FROM BP2 : IS A PART OF ATTUNE
13) Add the relationship category to the support team partner function
13.1)Use SPRO
IMG GUIDE->SAP SOLUTION MANAGER->SCENARIO SPECIFIC SETTINGS->
-> SERVICE DESK->PARTNER DETERMINATION PROCEDURE->DEFINE PARTNER FUNCTION.
13.2) FIND THE PARTNER FUNCTION SLFN0003 (SUPPORT TEAM).
13.3) In the field relation ship category, Select the newly created relationship category and save.
14) Steps 12 and 13 should be repeated for various business partner types like sold-to-party, message processors if new relationship is to be created for the respective business partner types.
15) Create a new access sequence for the support team determination
15.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Configuration ->
-> Scenario Specific Settings ->Service Desk -> Partner Determination Procedure ->
->Define Access Sequence
15.2) Click on New Entries
15.3) Define a new access sequence with sequence name as u2018Z001u2019 and description u2018NEW BP RELATIONSHIP ACTIVITY GROUPu2019
15.4) Create an new Individual Access with the following value:
u2022 Batch Seq: 10
u2022 Dialog Seq : 10
u2022 Source : Business Partner Relationship.
u2022 Detail on the source:
u2022 Partner Function : Reported By (CRM)
u2022 Mapping/restrictions
u2022 Flag Mapping/definition for partner being Searched
u2022 Partner Function in Source: Support Team (CRM).
Save it.
This Access Sequence will give us the Partner which has the relationship assigned
to the Support Team in the Reported By partner data.
16) Adapt the partner determination schema/Function
16.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Scenario Specific Settings ->Service Desk ->
-> Partner Determination Procedure -> Define Partner Determination Procedure.
16.2) The two options to adapt partner determination schema are
16.21) Adapt the standard Procedure (SLFN0001) or to create a new one by copying the standard one.
16.22) select the line starting with SLFN0001 or the newly created procedure.
16.23) Double Click on Partner Function in Procedure.
16.24) Select the Partner Function "Support Team", and click Details.
16.25) in the detail view only change the Partner Determination/access Sequence to
the one we've just created. Save your entry.
17) Create a root organizational model.
17.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration-> Scenario Specific Settings ->Service Desk -> Organizational Model ->Create a Root Unit for Your Organizational Structure.
17.2) creating an organizational unit by entering the data in the BASIC DATA tab.
17.3) enter the organizational unit, the description and save it.
18) Create the support team organization
18.1) go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Scenario Specific Settings ->Service Desk -> Create Organizational Objects in the Organizational Structure. Or use transaction (PPOMA_CRM).
19) Create the business Partners.
19. 1) Key users- End user (Business Partner General) ,Address should be specified.
19.2) go to the transaction BP.
19.3) create a new Person, Select the role: Business Partner (Gen).
For Identification of the key user
19.31) click on the identification tab
19.32) enter a line in the identification number formatted as follows
IDTYPE : CRM001.
Identification number : <SID><INSTALL NUMBERS><CLIENT><USERNAME>
eg: USER NAME : USER1.
CLIENT : 100.
SID : ER1.
INSTALL NUMBER : 123456789.
IDENTIFICATION NUMBER : ER1 123456789 100 USER1.
20) Message Processors- Support Team members .
20.1) they should be created first as the users in the corresponding client of the solution manager.
20.2) As business partners they will have the role 'EMPLOYEE'.
20.3) Go to transaction BP .
20.4) Create New Person with the role employee.
20.5) In the Identification tab you should enter the user name in the employee data/User Name.
eg: username: proc1
enter proc1 in the field User name.
21) Organizational Business Partner- Organizational BPS have the same country in there main address tab. They should be created through the organizational model. Business partner corresponding to the root organization have the role 'SOLD TO PARTY'.
22) Assign the business partners (Message Processors) to the previously created support team.
22.1) Go to transaction PPOMA_CRM.
22.2) Select the support team 1.
22.3) Click on create
22.4) select position
22.5) call it 'MPROC_T1/Message Processors for team 1
22.6) Replicate it for the other support teams.
22.7) Select the position MPROC_T1/Message Processors for team1 and click assign,
choose owner/Business Partner find and select the business partner
22.8) Validate and Save it.
22.9) If the assignment of business partner is not possible then implement the note 1008656
Or 997009
23) Create the iBase component
23.1) IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings -> Standard Configuration of Basic Settings -> Solution Manager -> iBase -> Initially Create and Assign the Component Systems as iBase Components.
23.2) or use the transaction IB51 to create the installed base.
23.3) it is also possible to create the SOLUTION_MANAGER, select the solution and go to menu Edit -> Initial Data Transfer for iBase.
24)Assign Business Partners to iBase Components
IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings
-> SAP Solution Manager System ->ServiceDesk-> iBase -> Assign Business Partners to iBase Components.
*--optional--
If you want to be able to assign the System Administrator: Go to the IMG: SAP Solution Manager Implementation Guide -> Customer Relationship Management -> Basic Function -> Partner Processing -> Define Partner Determination Procedure.
Select the entry "00000032 Installed Base/IBase" and double click on Partner Functions in Procedure.
Then copy the Entry "Contact Person (CRM)" to a new entry with the partner Function "System Administrator (CRM)" , save it.
Go back to transaction IB52, select a component, and Goto -> Partner, you should be able
now to assign the partner Function "System Administrator".
25) Assign the SAP Standard Role to the user. Message Creator should have the role : SAP_SUPPDESK_PROCESS.
26)Define the transaction variant for the message processors
Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration -> Scenario Specific Settings ->Service Desk -> General Settings -> Specify User Selection Variant.
Here we will create variants for the central message processing transaction CRM_DNO_MONITOR.so that the user will have direct access to there dedicated message.
27) Go to transaction PFCG
27.1) Enter the role name as Z_MSG_PROCESSORS and choose single role.
27.2) Give a description Message Processor role and save it.
27.3) Go to the menu tab and choose add report
27.4) select the report type : ABAP Report
27.5) And in the report enter the report name as 'CRM_DNO_SERVICE_MONITOR'.
27.6) Enter the previously created variant.
27.7) flag the skip initial screen box.
27.8) flag the SAPGUI for windows.
27.9) Create a new transaction with tcode starting with Y or Z.
27.10)Display this transaction and check the values at the bottom of the screen
in the subscreen Default Values, you should have the following parameters:
u2022 D_SREPOVARI-REPORT = CRM_DNO_SERVICE_MONITOR
u2022 D_SREPOVARI-VARIANT = MY_TEAM_MSG
u2022 D_SREPOVARI-NOSELSCRN = X
And also all the user should have the correct role.

Define Service Desk Destination in the Solution Manager System (Dump creen)

hi,
in SPRO when i click on Define Service Desk Destination in the Solution Manager System
i got dump screen with the error below
any help?
Runtime Errors         SAPSQL_EMPTY_TABNAME
Except.                CX_SY_DYNAMIC_OSQL_SYNTAX
Date and Time          13.07.2008 14:05:57
Short text
    A dynamically specified FROM clause has an unexpected format.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLSHI2" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SYNTAX', was not
     caught in
    procedure "STREE_READ_NODE_GENER" "(FUNCTION)", nor was it propagated by a
     RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    The running ABAP program attempted to execute an Open SQL statement in
    which a FROM clause was specified dynamically in the field "TABLE_NAME". In
     this
    FROM clause, either a table name after a join operator is missing, or an
     alias name after the key name "AS". The field "TABLE_NAME" could be empty as
    well.
regards

Hi,
I am facing the same problem. What is SP15 ?
Is there any SAP Note that can be applied to correct this ?
Thanks.

Implementing the Enterprise Support in Solution Manager

Hi Experts,
Can anybody tell me what are the pre requisites to implement Enterprise support in solution manager?
Also let me know what are steps involved in implementing the enterprise support.
Thanks in Advance
Hari

Hello Hari,
In order to implement Enterprise Support your organization should registered as a Value Added Reseller(VAR) with SAP. You can get all the required documentation under https://websmp104.sap-ag.de/solutionmanager --> Information for VARs, ASPs and AHPs which is in the left hand side of the page. However, you need to have a S-user ID of the VAR.
The following are the steps need to perform in implementing the Enterprise Support firmly known as Service Desk for VARs.
1. SAP Solution Manager basic settings (IMG)
a) Initial Configuration Part I
b) Maintain Profile Parameters
c) Maintain Logical Systems
d) Maintain SAP Customer Numbers
e) Initial Configuration Part II
     1) Activate BC Set
         a) Activate Service Desk BC Set
         b) Activate Issue Monitoring BC set
         c) Set-up Maintainance optimizer
         d) Change online Documentation Settings
         e) Activate Solution Manager Services
         f) Activate integration with change request Managemnt
         g) Define service desk connection in Solution Manager
   2)Get components for SAP Service Market place
        a) Get SAP Components
   3) Get Service Desk Screen Profile
       a)generate Business Partener Screen
   4)Copy By price list
       a)activate Service Desk BC Set
       b)Activate Issue Monitoring BC set
       c)Set-up Maintainance optimizer
      f) Business Add-In for RFC Connections with several SAP customers
      g) Business Add-In for RFC Connection of Several SAP Cust. no.
      h) Set-Up SAP Support Connection for Customers
      i) Assign S-user for SAP Support Portal functionality
      j) Schedule Background Jobs
      k) Set-Up System Landscape
      l) Create Key Users
      m) Create Message Processor
2. Multiple SAP Customer Numbers
      a) Business Add-In for RFC Connections with several SAP customer numbers
      b) Set-Up SAP Support Connection for Customers
3. Data transfer from SAP
      a) Data Transfer from SAP
4. Create u201COrganizationu201D Business Partner
5. Service Provider function (IMG)
      a) Business Add-In for RFC Connections with several SAP customer numbers
      b) Business Add-In for Text Authorization Check
      c) Activate BC Set for Service Provider
      d) Activate Text Types
      e) Adjust Service Desk Roles for Service Provider Menu
6. Service Provider: Value-Added Reseller (VAR)
      a) Business Add-In to Process Actions (Post-Processing Framework)
     b) Activate BC Sets for Configuration
     c) Create Hierarchy and Product Category
     d) Set-Up Subcategories
     e) Create Business Partner as Person Automatically
     f) Set-Up Automatic Confirmation of Messages
    g) Maintain Business Partner Call Times
    h) Set-Up Incident Management Work Center
7. Work Center (Web UI)
    a) Activate Solution Manager Services
    b) Assign Work Center Roles to Users
Hope it helps.
Regards,
Satish.

Install Solution Manager in RedHat Enterprise 6 with Oracle 11

Hello ,
In the marketplace-PAM, RedHat Enterprise 6 is not listed as approved for EHP1 Solution Manager 7.0 64 bit (unicode) with Oracle.
Does anyone have any information on this subject?
Has anyone installed the Solution Manager 7.0/Oracle with RedHat Enterprise 6?
tks

Yes, you are correct. Apart from PAM, following Note confirms this. RHEL 6 is not supported yet for Oracle, is in planning stage.
Note 1565179 - SAP software and Oracle Linux
Thanks

System landcape in large enterprise with solution manager

Dear Guru,
Do you have any ideas of how to set up Solution Manager in a big national enterprise? Let's suppose
a big company has a headquarter and serveral branches.
Every branch has its ERP, BW, etc, do you think it is better to set up respective Solution Manager system
for each branch or just create a powerful one centrally in the headquarter. Of course the latter means
less management but more authorization seperation related actions.
Is there any recommendation for this situation? Your opinion and insight is highly appreciated.
Thanks
Ray

Dear Gugu,
I know Solution Manager support some scenarios for multiple customer .e.g VAR in service desk.
But is it possible for hide solution or project infomation, especially content of respective business blueprint
to different customers?
I mean we want to use one single Solution Manager for multiple customers, but customers do not want their
owned document and business process information shared with other customers.
e.g. one customer log on to SOLMAN, then he could view project or solution information of other customer,
furthermore, he could also build up his business blueprint referring to other customer's business blueprint.
Is it possible to segregate this infomation?
Thanks a lot.
Ray

Logical systems while implementing charm in solution manager

Hello Everybody,
I just wanted to know how many logical systems we need while implementing charm in solution manager 7.0. I have 3 clients in development , 3 clients in Quality and 1 client in production.
Thank you,
vikram.

Hi Vikram,
Yes, i1n ChaRM we always work with logical systems, I mean clients.
The standard is:
DEV -> QAS -> PRD
However, you can also use:
- Minimum
DEV -> PRD
- Target groups
DEV -> QAS -> PRD
- > TST
DEV -> QA1 -> QA2 -> PRD
DEV -> QA1 -> PR1
-> QA2 -> PR2
There are a lot of combination possible.
BR
Fernando

XI 3.0 and BW 3.5 system type/logical component in Solution Manager

We are in the process of performing an upgrade for ERP 2004, XI 3.0 and BW 3.5. Initially this is being done in the sandpits. All systems are configured and connected our Solution Manager to download the packages.
We are unable to determine what type of system the XI 3.0 and BW 3.5 should be configured under. For example, previously we had an issue where ERP was configured as ECC 5.0 rather than ERP 2004. This was causing an issue in MOPZ where the upgrade option wasn't visible in a maintenance transaction. The same issue is now happening for XI and BW.
Please advise on the system type (logical component to use) for XI 3.0 and BW 3.5 in Solution Manager as SAP have made it very confusing. Currently both are under type Netweaver 04.
Regards,
-Rohan

Hi
I believe that SAP hasn't upgrade option for BW 3.5, Check link:
https://service.sap.com/solman-mopz
Upgrade
a "straight" upgrade for SAP Business Suite (upgrade from SAP ERP 2004 to SAP ERP 6.0, for example) is not supported by Maintenance Optimizer
Upgrade with an Installation of an Enhancement Package is supported for SAP ERP, SAP SCM, SAP SRM and SAP CRM
Regards
William Neira

Uninstall Solution manager 4.0

Similar Messages

Maybe you are looking for