Evaluation system with Solution manager

has anyone added an evalaution system where a user who logged a support message can evaluate the Solution given, with Solution manager. Basically the same thing like SAP have. When you close a call you have to rank the messageeg in regards of qaulity of answer etc etc..,
Anyone that might have any ideas how to do this, could you please give me some direction to how I can implement an evaluation system.
I thought of having a URL added to confirmation message, where the user can click on to take him to some area where he could evalaute the message. This systems is then linked to Solution manager so that I can report on these messages and the evealuation received for these support answers.
I will appreciate any feedback and any ideas would be most welcome to help me to get to a method of implementing such a evaluation system or developing such a system.

Dear Johan,
Firstly the kind of scenario that you are trying to implement is not possible via the standard configuration of Support Desk.
What I can think of is probably creating an action while closing the message which generates a form for the user to be filled and saves the values into an custom table for questions based on evaluation of the solution.
Later you can generate reports based on this table.
Regards
Amit

Similar Messages

Transport Management System with Solution Manager

Dear all,
Do you know the function transport management system(TMS) with solution manager, I already search in SAP document but not found this function.
Do you know how to config solution manager for TMS and documents related with this function please guide for me!
Thanks all very much !

Hi,
Check this link.
https://websmp103.sap-ag.de/~sapdownload/011000358700000508502008E/ChangeRequestManagement.pdf
Hope this answers your questions.
Feel free to revert back.
-=-Ragu

EWA on Non-ABAP System with Solution Manager EHP 1

Hi Experts,
We have recently updated our solution manager from SP Stack 16 to EHP1 (sp 18). we are now planning to set up EWA for non-abap components (EP 7.0). however, the only SAP note that i have been able to find is "976054 - Availability of EWA for Non ABAP components" but this is only limited up to SP 17. I have not been able to find any guides relating to EWA thru Solution Manager EHP1.
I would greatly appreciate if anyone can refer any documents or SAP notes that would enable setting up EWA for non-abap components thru Solution Manager EHP1.
We have also gone through the note 1332428, but we have'nt found it useful. We are still struggling to generate EWA report on Non-ABAP system.
Looking forward to your kind help.
Thanks and Regards,
Sarthak Syal

Hi Sarthak,
Good!!
Please do the following:
1) include the system in the Solution and scheduled the EWA session.Logical component should refer to the Non-ABAP System with no ABAP instance as relevant under the SID definition in SMSY-systems.
2) Is the Non -ABAP ( assuming its java) has the Software component defined and is mentioned as relevant under the SID with the component name and type.
3) Having said that SMD - Root cause Analysis functionality is configured-> check whether you are getting the Details for the Non-ABAP systems in the analysis Tabs of Root Cause Analysis.
This should be good to go. Wait for the session to get completed.
Thanks,
Jagan

Add sap R/3 enterprise system in solution manager SLD

Dear All
Required solution manager configuration documents.
We have DEV QAS and PRD server on SAP mySAP ERP 4.7 ( SAP R/3 Enterprise )
And during the installation of solution manager I select u201CConfigure a Local SLD u201C
Which steps I follows to connect or configure my sap system with solution manager ( SLD ) then I will configure central monitoring, TMS management, Helpdesk etc
Who to Configure SLD Bridge ( in SLD Server ) ?
in which system Run Transaction RZ70 ( In SAP R/3 Enterprise ) ?
and how to Verify that my system is connected and working fine With SLD
Please help me regarding u201C configuration solution manager u201C
Regards
Shahid

Hi
Visit for step by step details of Standard Configuration of Basic Settings
http://service.sap.com/rkt-solman-->SAP Solution Manager 7.0->Technology Consultants & System Administrators->Technical Configuration->just drill out there you can find lot of simulator how to install and configure solution manager
http://www.wilsonmar.com/sap_solution_manager.htm
/people/federico.babelis2/blog/2006/04/14/service-desk-configuration-guide-for-dummies
Regards
Uday

SAP NW 7.4 as java system sync with solution manager system 7.1 issue

Dear all,
I have installed SAP NW 7.4 system SP level is SP5 ,after that i have cheked in service marlket palce Now service market plkace latest SP level SP7.
For manula downlowd( directly from service market place) is difficult for java system and i have started sysnc with solution manager system to download patches through MOPZ.
Below are the activities completed:
1) Through template installed I have rgeisterd the system into Solman SLD.
2) Sync completed succfully exact product version is shwoing in solman SLD
3) after that I have checked in SMSY and LMDB its showing prefectly
4) But in SMSY its shwoing only under technical system,not showing product systems
5) I have assigned in product system in LMDB
Now the issues while selecting the system group and logical componensts I have created one logical componnets -but in that SAP NW 7.4 is not showing and I have assumed SAP NW 7.3 EHP1 after creating my newly create dsystem is not shwoing in drop down.
I ma getting belwo error.
No system found for this product/product instance
Message no. SOLAR_SPROJECT110
Please sugegst how to reslove the error ,and a;lso please let me know is there any way to download latest pathces to dpownload from service market place .
Advance Thanks

Hi,
re-check if the 7.4 system is correctly registered in the solman SLD system.
Re-check LMDB definition for your 7.4 as JAVA system. you have to manually created the Product system. Ensure all the Component and definitions are correct.
Also do a verrification run within the LMDB. This will confirm whether all the information is correctly defined.
Please note - SLD -> LMDB -> SMSY.
So, if the first 2 don't have the correct information, you wont have much joy with smsy.
Rgds
Deepak

System Monitoring with Solution Manager Ehp1

Hi,
I'm Tomas Piqueres, and I'm working in a VAR SAP with Solution Manager.
Recently, we installed Solution Manager Ehp1 and we are trying to configure it for System Monitoring. When I worked with Solution Manager SP17 I used to go to transaction RZ21 to add the system I wanted to monitoring and then put the SID and RFCs of the system.
Now with Solution Manager Ehp1, when I create the system in transaction RZ21, first I have to set the Component Type to Be Monitored and then the SID, Message Server Logon Group, the client and user are set automatically, and the password I've set to user CSMREG.
when I fill all the entries, I can see the RFCs used for the monitoring of the system. Those RFCs are set automatically:
<SID>_RZ20_COLLECT
<SID>_RZ20_ANALYZE
I can't edit those RFCs, so I have to create it manually. I check that RFCs destination works fine and both pass the authorization test, so when I try to save the system at transaction RZ21, I see the following errors:
<SID>_RZ20_COLLECT_123539Error when opening an RFC connection
Error during remote call of SAL_MS_GET_LOCAL_MS_INFO function: Error when opening an RFC connection
Error during remote call of SALC function: Error when opening an RFC connection
Error during remote call of RFC1 function: Error when opening an RFC connection
I've been looking for information about those errors and how to monitoring with Solution Manager Ehp1, but I haven't found anything usefull.
Please, Could you help me?
Thanks and regards,
Tomas.

Tomas,
I need to configure EWA from my Solman system and I completed the steps (defining and creation of RFC destinations to the target systems from my Solman system). I downloaded the lates ccmsagent file from the market place based my target system configurations.
Herewith attaching the logs while I'm trying to check the profile parameter.
tqaadm@saptqa01:/usr/sap/TQA/SYS/exe/run 5> sappfpar check pf=/usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
================================================================================
==   Checking profile:     /usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
================================================================================
***WARNING: Unexpected parameter: DIR_EPS =/usr/sap/trans/EPS/----
***WARNING: Unexpected parameter: SAPSECULIB =/usr/sap/TQA/SYS/exe/run/libsapsecu.o
***WARNING: Unexpected parameter: abap/buffersize_part1 =1200000
***WARNING: Unexpected parameter: auth/auth_number_in_userbuffer =5000
***WARNING: Unexpected parameter: dbs/io_buf_size =100000
***WARNING: Unexpected parameter: rsau/local/file =/usr/sap/TQA/DVEBMGS30/log/audit/audit_++++++++
***WARNING: Unexpected parameter: rsau/selector1/class =35
***WARNING: Unexpected parameter: rsau/selector1/severity =2
***WARNING: Unexpected parameter: rsdb/rclu/cachelimt =0
***ERROR: Size of shared memory pool 40 too small
================================================================
SOLUTIONS: (1) Locate shared memory segments outside of pool 40
               with parameters like: ipc/shm_psize_<key> =0
SOLUTION: Increase size of shared memory pool 40
          with parameter: ipc/shm_psize_40 =1472000000
Shared memory disposition overview
================================================================
Shared memory pools
Key:   10 Pool
            Size configured.....:   642000000 ( 612.3 MB)
            Size min. estimated.:   637597428 ( 608.1 MB)
            Advised Size........:   640000000 ( 610.4 MB)
Key:   40 Pool for database buffers
            Size configured.....: 1048000000 ( 999.4 MB)
            Size min. estimated.: 1468229308 (1400.2 MB)
            Advised Size........: 1472000000 (1403.8 MB)
Shared memories inside of pool 10
Key:        1 Size:        2500 (   0.0 MB) System administration
Key:        4 Size:      523648 (   0.5 MB) statistic area
Key:        7 Size:       14838 (   0.0 MB) Update task administration
Key:        8 Size:    67108964 ( 64.0 MB) Paging buffer
Key:        9 Size:   134217828 ( 128.0 MB) Roll buffer
Key:       11 Size:      500000 (   0.5 MB) Factory calender buffer
Key:       12 Size:     6000000 (   5.7 MB) TemSe Char-Code convert Buf.
Key:       13 Size:   200500000 ( 191.2 MB) Alert Area
Key:       16 Size:       22400 (   0.0 MB) Semaphore activity monitoring
Key:       17 Size:     2672386 (   2.5 MB) Roll administration
Key:       30 Size:       37888 (   0.0 MB) Taskhandler runtime admin.
Key:       31 Size:     4806000 (   4.6 MB) Dispatcher request queue
Key:       33 Size:    39936000 ( 38.1 MB) Table buffer, part.buffering
Key:       34 Size:    20480000 ( 19.5 MB) Enqueue table
Key:       51 Size:     3200000 (   3.1 MB) Extended memory admin.
Key:       52 Size:       40000 (   0.0 MB) Message Server buffer
Key:       54 Size:    20488192 ( 19.5 MB) Export/Import buffer
Key:       55 Size:        8192 (   0.0 MB) Spool local printer+joblist
Key:       57 Size:     1048576 (   1.0 MB) Profilparameter in shared mem
Key:       58 Size:        4096 (   0.0 MB) Enqueue ID for reset
Key:       62 Size:    85983232 ( 82.0 MB) Memory pipes
Shared memories inside of pool 40
Key:        2 Size:    31168040 ( 29.7 MB) Disp. administration tables
Key:        3 Size:   114048000 ( 108.8 MB) Disp. communication areas
Key:        6 Size: 1064960000 (1015.6 MB) ABAP program buffer
Key:       14 Size:    28600000 ( 27.3 MB) Presentation buffer
Key:       19 Size:    90000000 ( 85.8 MB) Table-buffer
Key:       42 Size:    13920992 ( 13.3 MB) DB TTAB buffer
Key:       43 Size:    43422392 ( 41.4 MB) DB FTAB buffer
Key:       44 Size:     8606392 (   8.2 MB) DB IREC buffer
Key:       45 Size:     6558392 (   6.3 MB) DB short nametab buffer
Key:       46 Size:       20480 (   0.0 MB) DB sync table
Key:       47 Size:    13313024 ( 12.7 MB) DB CUA buffer
Key:       48 Size:      300000 (   0.3 MB) Number range buffer
Key:       49 Size:     3309932 (   3.2 MB) Spool admin (SpoolWP+DiaWP)
Shared memories outside of pools
Key:       18 Size:     1792100 (   1.7 MB) Paging adminitration
Key:       41 Size:    25010000 ( 23.9 MB) DB statistics buffer
Key:       63 Size:      409600 (   0.4 MB) ICMAN shared memory
Key:       64 Size:     4202496 (   4.0 MB) Online Text Repository Buf.
Key:       65 Size:     4202496 (   4.0 MB) Export/Import Shared Memory
Key:     1002 Size:      400000 (   0.4 MB) Performance monitoring V01.0
Key: 58900130 Size:        4096 (   0.0 MB) SCSA area
Nr of operating system shared memory segments: 9
Shared memory resource requirements estimated
================================================================
Nr of shared memory descriptors required for
Extended Memory Management (unnamed mapped file).: 64
Total Nr of shared segments required.....:         73
System-imposed number of shared memories.:       1000
Shared memory segment size required min..: 1472000000 (1403.8 MB)
System-imposed maximum segment size......: 35184372088832 (33554432.0 MB)
Swap space requirements estimated
================================================
Shared memory....................: 2050.4 MB
..in pool 10 608.1 MB,   99% used
..in pool 40 999.4 MB, 140% used !!
..not in pool:   34.4 MB
Processes........................: 716.8 MB
Extended Memory .................: 8192.0 MB
Total, minimum requirement.......: 10959.2 MB
Process local heaps, worst case..: 1907.3 MB
Total, worst case requirement....: 12866.5 MB
Errors detected..................:    1
Warnings detected................:    9
After checking the profile parameter I tried to run sapccm4x in /run directory but got the below error and I'm not able tomove further.
Pls have a look at these two and let me know what could I do to proceed further.
tqaadm@saptqa01:/usr/sap/TQA/SYS/exe/run 5> sapccm4x -R pf=/usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
INFO: CCMS agent sapccm4x working directory is /usr/sap/TQA/DVEBMGS30/log/sapccm4x
INFO: CCMS agent sapccm4x config file is /usr/sap/TQA/DVEBMGS30/log/sapccm4x/csmconf
INFO: Central Monitoring System is [SMP]. (found in config file)
      additional CENTRAL system y/[n] ?   :
INFO: found ini file /usr/sap/TQA/DVEBMGS30/log/sapccm4x/sapccmsr.ini.
INFO:
      CCMS version 20040229, 64 bit, multithreaded, Non-Unicode
      compiled at   Jun 28 2010
      systemid      324 (IBM RS/6000 with AIX)
      relno         6400
      patch text    patch collection 2010/1, OSS note 1304480
      patchno       335
INFO Runtime:
      running on    saptqa01 AIX 3 5 00069A8FD600
      running with profile   /usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
INFO profile parameters:
      alert/MONI_SEGM_SIZE = 200000000
      alert/TRACE          = 1
      SAPSYSTEM            = 30
      SAPSYSTEMNAME        = TQA
      SAPLOCALHOST         = saptqa01
      DIR_CCMS             = /usr/sap/ccms
      DIR_LOGGING          = /usr/sap/TQA/DVEBMGS30/log
      DIR_PERF             = /usr/sap/tmp
INFO:
      pid           4165682
INFO: Attached to Shared Memory Key 13 (size 200141728) in pool 10
INFO: Connected to Monitoring Segment [CCMS Monitoring Segment for application server saptqa01_TQA_30, created with version CCMS version 20040229, 64 bit single threaded, compiled at Oct 3 2008, kernel 6400_20020600_254, platform 324 (IBM RS/6000 with AIX)]
        segment status     ENABLED
        segment started at Tue Sep 14 09:35:56 2010
        segment version    20040229
ERROR: Shared Memory misconfiguration ==> can not monitor SAP application server saptqa01_TQA_30
       Dispatcher Admin Shared Memory (Key 01) and CCMS Shared Memory (Key 13) both in pool 10.
       Please change configuration with profile parameters
           ipc/shm_psize_01 = -<different pool nr>
       xor
           ipc/shm_psize_13 = -<different pool nr>
EXITING with code 1

SMD Configuration on MDM 7.1 with Solution Manager 7.01 SP19

Hi,
Kindly let me know if someone has faced issue with configuring SMD on SMD 7.1 with Solution Manager 7.01 SP19. Presently I have configured that and System is being shown in Wily Introscope Webview but Saposcol is greyed out in that.
Also system is not showing any data in Introscope Dashboard. Any guess for this?
Earlier while I was configuring SMD, error related to null installation directory (...Invalid root directory: /usr/sap/SID/null ) were occuring. After that when I created a softlink for saposcol service from /usr/sap/hostctrl/exe/saposcol to /usr/sap/SMD/SMDA97/exe.
Still no data and still in SMD Agent logs saposcol service warning is there.
Thanks & Regards,
Manish Singh

Hi Jansi,
Thanks for the reply..
Here is our scenario. SAPOSCOL was not there in /usr/sap/SMD/SMDA97/exe first place. So I made the softlink from /usr/sap/hostctrl/exe/saposcol to /usr/sap/SMD/SMDA97/exe and than re-ran setup again but still of no use.
Our Soltuion Manager saposcol version and MDM saposcol version is same. Below is the SMD Agent log of MDM server:
Apr 20, 2011 2:36:19 PM [Thread[Thread-22,5,main]] Error      com.sap.smd.wily.hostagent.config.AgentConfigVO - finalizeDestination(): Initialization failed
[EXCEPTION]
com.sap.smd.wily.hostagent.PermanentException: Error: cannot connect to destination SapHostControl_Default. Probably saphostctrl is not installed. This error can be ignored if saposcol is available.
at com.sap.smd.wily.hostagent.saphostcontrol.SapHostControlDestination.open(SapHostControlDestination.java:98)
at com.sap.smd.wily.hostagent.config.AgentConfigVO.finalizeDestination(AgentConfigVO.java:85)
at com.sap.smd.wily.hostagent.config.AgentConfigXmlHandler.endElement(AgentConfigXmlHandler.java:174)
at com.sap.engine.lib.xml.parser.handlers.SAXDocHandler.endElement(SAXDocHandler.java:156)
at com.sap.engine.lib.xml.parser.XMLParser.scanEndTag(XMLParser.java:1953)
at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1846)
at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2442)
at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1843)
at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2845)
at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:165)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245)
at com.sap.engine.lib.xml.parser.Parser.parse_DTDValidation(Parser.java:260)
at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:271)
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at com.sap.smd.wily.hostagent.config.AgentConfigParser.parseXml(AgentConfigParser.java:59)
at com.sap.smd.wily.hostagent.SapAgent.loadConfiguration(SapAgent.java:430)
at com.sap.smd.wily.hostagent.SapAgent.start(SapAgent.java:93)
at com.sap.smd.wily.hostagent.WilyHostService.startAgent(WilyHostService.java:118)
at com.sap.smd.wily.hostagent.WilyHostServicep4_Skel.dispatch(WilyHostServicep4_Skel.java:168)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:721)
at java.lang.Thread.run(Thread.java:664)
Caused by: javax.xml.rpc.soap.SOAPFaultException: Method 'SOAP-ENV:Envelope' not implemented: method name or namespace not recognized
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.buildFaultException(MimeHttpBinding.java:747)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.processDocumentFault(MimeHttpBinding.java:870)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1451)
at com.sap.smd.agent.wsclients.saposcol.SAPOscolStub.getCpuConsumption(SAPOscolStub.java:142)
at com.sap.smd.agent.wsclients.saposcol.SAPOscolStub.getCpuConsumption(SAPOscolStub.java:157)
at com.sap.smd.wily.hostagent.saphostcontrol.SapHostControlDestination.open(SapHostControlDestination.java:94)
... 25 more
Apr 20, 2011 2:36:19 PM [Thread[Thread-22,5,main]] Warning    com.sap.smd.wily.hostagent.SapAgent - startActions(): Action SAPOsColWs
[EXCEPTION]
com.sap.smd.wily.hostagent.TransientException: Destination not available:SapHostControl_Default
at com.sap.smd.wily.hostagent.saphostcontrol.SapHostControlAction.init(SapHostControlAction.java:74)
at com.sap.smd.wily.hostagent.SapAgent.startActions(SapAgent.java:396)
at com.sap.smd.wily.hostagent.SapAgent.start(SapAgent.java:94)
at com.sap.smd.wily.hostagent.WilyHostService.startAgent(WilyHostService.java:118)
at com.sap.smd.wily.hostagent.WilyHostServicep4_Skel.dispatch(WilyHostServicep4_Skel.java:168)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:330)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:721)
at java.lang.Thread.run(Thread.java:664)
Apr 20, 2011 2:36:20 PM [Thread[Thread-22,5,main]] Warning    com.sap.smd.wily.hostagent.action.SapOsColAction - launchDaemon(): saposcol exited with 255***********************************************************************
This is Saposcol Version COLL 21.01 711 - AIX v12.01 5L-64 bit 090324
Usage: saposcol -l: Start OS Collector
        saposcol -k: Stop OS Collector
        saposcol -d: OS Collector Dialog Mode
        saposcol -s: OS Collector Status
The OS Collector (PID 1552388) is already running .....
Apr 20, 2011 2:36:23 PM [Thread[SAPOsCol,5,main]] Error      com.sap.smd.wily.hostagent.action.AbstractAction - run(): Action throws exception, will be terminated: SAPOsCol
[EXCEPTION]
java.lang.NullPointerException:
at com.sap.smd.wily.hostagent.action.SapOsColAction.reportProperty(SapOsColAction.java:293)
at com.sap.smd.wily.hostagent.action.SapOsColAction.dumpSection(SapOsColAction.java:239)
at com.sap.smd.wily.hostagent.action.SapOsColAction.processXml(SapOsColAction.java:164)
at com.sap.smd.wily.hostagent.action.SapOsColAction.doRun(SapOsColAction.java:417)
at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:53)
at com.wily.EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:728)
at java.lang.Thread.run(Thread.java:664)
Our MDM is 7.1 version and Solution Manager is 7.01 (EHP1) with SP19 so we should configure our MDM system as 7.1 version which we did but still data is not coming in Wily properly. Its not showing SID name under the hostname in Wily Introscope and neither is MDM Servers (Master Data Import Server, Master Data Server & Master Data Syndication Server under SID).
Now the interesting thing is that if we configure our MDM server as 5.5 version with Solution Manager and do the configuration than its showing in Wily but in that case MDM Cockpit doesn't work.
We want both to work Wily as welll as MDM Cockpit since our MDM and Solman version matches for both configuration.
Any ides or help steps to do that?
Thanks,
Manish Singh

How to setup CCMS with Solution Manager

Hi, All
My question is how to setup or satallite connection with Solution manager 4.0 for CCMS alerts
Is that RFC connection using both sites, trusted and satellite system ?
I would like to setup CCMS alerts through Solution manager and R/3 ccms
please anyone has some guide or URL or any idea send me
We are using SAP NW 2004 620 4.6C (SLD=DV,QA,PR) and solution manager 4.0
Thanks in advanced
J
Edited by: issue2008 on Sep 19, 2008 12:13 PM

you need to install CCMS agents(sapccm4x, sapccmsr) on satellite systems & configure them with the central system(solman).

Big Problem With Solution Manager EHP1 ?

Dear all,
I have already installed SAP Solution Manager EHP1, after the installation sucessfuly. I check the function: Project Administration ( T code : Solar_Project_Admin), then select New project button.
The program inform that:
"Runtime Errors: Message Type Unknow
What happened:
Error in ABAP Application program
The current ABAP program "SAPLSPROJECT_SYSTEM_LANDSCAPE" had to be terminated because
it has come across a statement that unfortunately cannot be excuted.
etc
Do you know about this problem, what is the errors ?
Thanks all.

Dear all.
With Solution Manager EHP1
SAP Basis: SAPKB7001-SAPKB70016, SAPKB70101-SAPKB70102
SAP ABA: SAPKA7001-SAPK70016, SAPKA70101-SAPKA70102
Detail log as below:
Runtime Errors MESSAGE_TYPE_UNKNOWN
Date and Time 28.04.2009 16:47:15
Short text
Message type " " is unknown.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSPROJECT_SYSTEM_LANDSCAPE" had to be terminated
because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
Only message types A, E, I, W, S, and X are allowed.
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_UNKNOWN" " "
"SAPLSPROJECT_SYSTEM_LANDSCAPE" or "LSPROJECT_SYSTEM_LANDSCAPEU28"
"SPROJECT_SYSL_CHECK_CENTRAL_SY"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
Information on where terminated
Termination occurred in the ABAP program "SAPLSPROJECT_SYSTEM_LANDSCAPE" - in
"SPROJECT_SYSL_CHECK_CENTRAL_SY".
The main program was "SAPLS_IMG_TOOL_5 ".
In the source code you have the termination point in line 29
of the (Include) program "LSPROJECT_SYSTEM_LANDSCAPEU28".

Problem starting with solution manager

hi guy, i have a problem with Solution Manager version 4.0 During an istallation of support package I had a network problem and the system went down fore some minutes. After that, is not possible logon on system. I try startsap and is ok, db seem up but is not possible connect by sapgui.
These are some errors that I can find in workdir
Tue Jan 27 15:08:51 2009
ERROR => GwIConnect: GwRead to SAPSM01 / 3301 failed, rc: NIETIMEOUT [gwxx_m
t.c    473]
***LOG S90=> SAP_CMREGTP2, GwIConnect ( 223) [r3cpic_mt.c 9618]
ERROR => ErrTrace: no error info available [err_mt.c     1507]
Connect_PM TPNAME=IGS.SM1, GWHOST=SAPSM01, GWSERV=3301
no SAP ErrInfo available
>TS> Tue Jan 27 15:10:51 2009
T:4398099755584 ======> Connect to SAP gateway failed
Connect_PM TPNAME=IGS.SM1, GWHOST=SAPSM01, GWSERV=3301
no SAP ErrInfo available
System is a Suse/Linux ppc64, with MaxDB as database
Please help me!!
hi guy, i have a problem with Solution Manager version 4.0 During an istallation of support package I had a network problem and the system went down fore some minutes. After that, is not possible logon on system. I try startsap and is ok, db seem up but is not possible connect by sapgui.
These are some errors that I can find in workdir
Tue Jan 27 15:08:51 2009
ERROR => GwIConnect: GwRead to SAPSM01 / 3301 failed, rc: NIETIMEOUT [gwxx_m
t.c    473]
***LOG S90=> SAP_CMREGTP2, GwIConnect ( 223) [r3cpic_mt.c 9618]
ERROR => ErrTrace: no error info available [err_mt.c     1507]
Connect_PM TPNAME=IGS.SM1, GWHOST=SAPSM01, GWSERV=3301
no SAP ErrInfo available
>TS> Tue Jan 27 15:10:51 2009
T:4398099755584 ======> Connect to SAP gateway failed
Connect_PM TPNAME=IGS.SM1, GWHOST=SAPSM01, GWSERV=3301
no SAP ErrInfo available
System is a Suse/Linux ppc64, with MaxDB as database
Please help me!!

hi,
there is anyone who can help me?
Many Thanks
Fabrizio

Cannot run HP QTP 11 in integrated mode with Solution Manager 7.1

Hi,
I have setup qtp to work with solution manager 7.1. QTP works in standalone mode with no issues. as soon as I try and use it in integrated, i.e. launch qtp from solution manager, the message "failed to start external test tools quicktest professional" displays. When I click the back button the message "error during method call in OLE API" displays.
Using qtp in integrated mode worked previously on the solution manager 7.1 system. Since the solution manager 7.1 system was moved to a new datacenter it stopped working. I am not sure if this could have had an impact.
I have tested qtp with several different solution manager boxes and it works perfectly in integrated mode. please advise what server side settings i need to consider to solve the issue.
Sincerely,
David
Edited by: David Snyman on Mar 2, 2012 7:38 AM

Hi Sida,
Can you check SapLogon.ini file maintaining below location please.
let me know it resolve the isse, can you forward your details to <email removed by moderator>
looking forward your response.
Regards
Naveen
File Location
Use
C:\Windows\saplogon.ini
Enable QTP to identify the Solution
Manager Server
C:\Users\nav\AppData\Roaming\SAP\Common\saplogon.ini
Auto log on to SAP Systems for testing
C:\SAP\FrontEnd\SAPgui\saplogon.ini
Set Record and Run settings in QTP for
64 Bit OS
C:\Program Files
(x86)\SAP\FrontEnd\SAPgui\saplogon.ini
Set Record and Run settings in QTP for
32 Bit OS
Message was edited by: Manish Kumar

How to add a system into Solution Manager directory.

Hi!
Can anybody tell me how to add a system into Solution Manager directory before generating license key for ECC installation .
Also,
How to connect the XI in same box with SolMan and ECC in defferent server to SolMan 3.2 .
I am going to install SolMan and than XI in and box and after that ECC in a seperate box.
AM I right?
regards,
Pratip Bhattacharyya

Hi Bratip Bhattacharyya,
SolMan 3.2 needs SLD only for automatic data gathering of the sap landscape; you can choose between SLD and LIS in transaction SMSY_SETUP (which simply uses the TMS-domain controllers for information gathering).
XI needs SLD, but XI needs also a netweaver04 (s) system (Abap WAS 6.40). SolMan 3.2 isn't a netweaver04 system (Abap WAS 6.20). So you have to install XI as an own central instance (Abap + Java) on the same windows server, if you like. In this case you have to install for XI an own SLD. Different SLDs can create bridges between themselves. Please look at the SLD configuration guide (quicklink /netweaver -> installation guides).
But don't ask me how to install two sap systems on one server on windows (on Linux it's easy I have done so); basically it will have an own SID and own "service" numbers (which means own tcp port numbers).
If you can't dedicate to XI an own server, it's only a question of hardware sizing. For the different combinations of netweaver components you should study the master guide for netweawer.
Bye
Message was edited by: Riccardo Escher

How to create Rfc for EP system in Solution manager

Dear experts,
I am doing ChaRM configuration for my EP system ( java only).
I also configured CTS+ successfully but we want to integrate this with Chram in solman.
I have done all configuration according to standard doc for ChaRM.
But when creating project from solar_admin it is giving "   NO RFC for DEP system"
so please suggest me how to create RFC for java system in Solution manager.
thanks in advance
dhiraj

Hello,
You need to setup an ABAP communication client and system, that's done through the TMS settings:
For source system:
- CTC                                              1
- CTS_SYSTEM_TYPE                          JAVA (others for a MDM system)
- NON_ABAP_SYSTEM                          1
- COMMUNICATION_SYSTEM:              (SAPSID of the ABAP communication system (e.g. the domain controller))
- NON_ABAP_WBO_CLIENT                    (Client of the ABAP stack on which the Transport Organizer Web UI (CTS_BROWSER) is activated and will run.)
- WBO_GET_REQ_STRATEGY                 TAGGED
- WBO_REL_REQ_STRATEGY                 MANUAL
For quality and production Java system (target systems):
- CTC                                              1
- CTS_SYSTEM_TYPE                          JAVA (others for a MDM system)
- NON_ABAP_SYSTEM                         1
- COMMUNICATION_SYSTEM:                 (SAPSID of the ABAP communication system (e.g. the domain controller))
- DEPLOY_WEB_SERVICE                       CTSDEPLOY
- DEPLOY_DATA_SHARE:
When this is done correctly, you will see the fields ABAP communication system and client populated in SMSY.
When ChaRM needs to operate on the non ABAP systems, it will take the RFCs for the communication system and client.
Best regards,
Miguel Ariñ

Integrating third party system with solution manger

Dear All,
How we can do integration between third patrty system and solution manager. As part of our implementation we have got some other application to be integrated with SAP . We have got ECC 6.0 and Solution manager.Can any one guide me how to do this,
Thanks
Hany

Hi Pankaj,
Yes this is possible.
Create an RFC using SM37 transaction.
Build the logic to retrieve the data.
The 3rd party system also should have the necessary logic to be triggered once there is a call from RFC & get the primary keys based on which it will retrieve data & pass it to SAP.
Best regards,
Prashant

BCP Microsoft Platform integration with Solution Manager

Hi
Is it possible to integrate BPC Microsoft platform 7.0 and 7.5 with Solution Manager?
If so how? Is there documentation available explaining the process?

Hi Johan,
There is some level of integration available with Solution Manager. To set up your system for Diagnostics, refer to "End-to-End Root Cause Analysis System Landscape Setup Guide", which is available on Service Marketplace at [https://service.sap.com/sapidb/011000358700000074392009E|https://service.sap.com/sapidb/011000358700000074392009E], and follow the chapters that apply to Planning and Consolidation.
You can also access this document by going to [http://service.sap.com/diagnostics|http://service.sap.com/diagnostics] and selecting the Media Library link under the "More Documentation" section. The document is labeled "SAP Solution Manager Landscape Setup Guide".
Thanks.

Evaluation system with Solution manager

Similar Messages

Maybe you are looking for