Solution Manager Certificates

Hi All, I'm Searching for E-learning course on SAP Solution Manager certification. Thanks

SM001, SM510, SM520, SM530 and SM550 are available as eLearning courses from sap ... have a look at their training and certification shop (https://training.sap.com/shop/)...hope this will help you for your certification... GreetZ, AH

Similar Messages

Renew and Download maintainance certificate from solution manager

Hi Friends,
I am looking to renew and download maintenance certificate for MANAGED SYSTEM from Solution Manager (7.1) SP12.
Can you guys guide me on this how do I proceed.
Thanks & Regards,
Solman Starter

Hi
Please check
https://websmp204.sap-ag.de/~sapidb/011000358700000574752008
and
https://websmp204.sap-ag.de/~form/sapnet?_SCENARIO=01100035870000000202&_SHORTKEY=01100035870000716020&_OBJECT=011000358700000138222008E
check out FAQ abt maintenace certificate:
https://websmp204.sap-ag.de/~sapidb/011000358700000325262008E#6
The SAP Solution Manager triggers the generation of a valid maintenance certificate in SAP Support Portal, download it locally in SolMan system and manages the distribution to the managed system.
See detailed documentation http://help.sap.com/saphelp_sm71_sp01/helpdata/en/89/a7c08d740c4cffb491f98801f17d30
Thanks
Vikram

Error While Applying patch ST-PI 2008_1_700 to solution Manager

Dear Techies,
Thanks alot for your fast response.
We are trying to upgrade Solution Manager Stack from
ST-PI 2005_1_700 to ST-PI 2008_1_700 ,
While applying patch it was suddenly stopped with an error
"Manual modification adjustment is neccessary"
While I tried to adjust it.
In Note correction tree. This the message with " green tick"
"0001293326 EWA: Newest ST-PI Is Rated 'Outdated'; Wrong RTCCTOOL Date"
and is not allowing me to proceed further.
How to go about.
Thanks in advance.
regards,
Kiran

Hi Varun,
Thanks for your reply.
As suggested by you, I executed "RTCCTOOL" programme.
It Has given that 4 notes were in red status.
They are.
        1. [Note 69455 ]      Addon upgrade ST-A/PI 01N_700SOL
        Description     "Servicetools for Applications Plug-In" for Solution Manager 4.0-7.10 (Addon delta upgrade package)
        Implementation From http://service.sap.com/supporttools->ST-A/PI download the addon upgrade package ST-A/PI
                                 01N_700SOL. Upload to tx SAINT (just as you would do for an installation) and install as per note 69455
                                 Then restart report RTCCTOOL and choose 'List->Refresh from SAPNet'.
        4. [Note 539977 ]     ST-PI Support Packages
Description     Addon supportpackage level 4 for ST-PI 2008_1_700 for 7.00 [patches up to level 4 for Basis tools for services]
Implementation Open http://service.sap.com/supporttools-> ST-PI 2008_1_700 ->Supportpk. Add patch SAPKITLRD4 (and predecessors if not yet implemented) to download basket. Release basket via Maintenance optimizer. Upload from frontend int transaction SPAM, define a queue and import the queue.
        6. [Note 539977 ]     Note 1312413 for ST-PI
        Description     Maintenance Certificates for SPAM/SAINT may get periodically overwritten by invalid ones on ST-PI
                               2008_1_7* SP 00. Prevent this proactively,even if you do not yet use the automatic maint. certificate
                              distribution.
         Implementation We recommend that you implement the Supportpackage SP1 for ST-PI 2008_1* to solve the error. Only if
                                  not possible implement note 1312413   with not version >=12 using SNOTE. Regarding automatic maint.
                                  certificate distribution see http://service.sap.com/maintenancecertificate.
        9. [Note 1293326 ]    EWA serviceprep correct. in sequence.
Description     Wrong alerts appear in EWAlert Service preparation section (Newest ST-PI Rated Outdated / Wrong
                      RTCCTOOL Date) if Solution Manager ST-SER < 701_2008_2 SP1 and satellites on ST-PI 2008_1* / ST-A/PI 01L*.
Implementation Implement the coding correction of this note 1293326   with SNOTE to solve the wrong service preparation alerts. Else if you do not mind the wrong alerts simply set this recommendation manually to green after reading.
These are in green status
Successfully implemented addons/ transports/ notes
        2. [Note 69455 ]    Proc. after addon impl.
        3. [Note 539977 ]   Addon ST-PI 2008_1_700
        5. [Note 539977 ]   Note 1300023 for ST-PI
        7. [Note 539977 ]   Note 1293657 for ST-PI
        8. [Note 12103 ]    Collectors and TCOLL.
While I tried to implement the note "69455" system is giving the message that there are no valid corrections and is coming out of the process
"Note 0000069455 cannot be implemented since no valid correction is available."
And is same for other notes also.
How to go ahead.
Thanks in advance.
Regards,
Kiran

Solution manager Remote Connection issues

Hi
I'm currently in the process of setting up Solution Manager 7.1 on windows Server 2008r2 using central system.
I did the prerequisite check & the Solman installation and i'm actuallly working on the post-installation steps.
I'm experiencing difficulty with the step : "Configure Remote Connection to SAP".
I followed the informations provided on :   http://service.sap.com/remoteconnection
In the technical prerequesite you have to set up a connection to sap support.
So i have to choose a connection type : I selected Internet connection so my first question is : do we need "VPN with SNC" or "VPN OR SNC" ?
I personnaly understood VPN or SNC.
So from here i decided to use SNC.
The first step was to set up & configure the SAProuter. I decided to do it on an another computer on the same domain ( not on the same computer where Solution Manager is installed ) but i'm not sure it is necesary
I assume I can install Saprouter on the same location as the Solution manager? do you recommend it ?
The Basic Functions testing with niping is working.
The next step is : "establish Internet Connections"
So now i can choose between SNC or VPN : my goal is to establish the connection as fast as possible.
I actually don't have a switch available ( i can get one if necesary but time is running ... ) so i'm opting for the SNC solution.
I tryed to get the certificate for the saprouter but i don't have a register SAProuter, but when i opened a customer messager for component XX-SER-NET, SAP answered about the impossibility to access SAP service Backbone with an SNC , saying that i will need to register a VPN site to site connection to SAP => i don't get it .... Can someone explain it to me ?
So please can one of you guru's tell me how to set this remote connection :
-which materials ( server / switch / firewalls ) ?
-where to get the right documentation ?
-What about DMZ ?
-I have a single IP Address is that enough ? ( setting up nat for port 3299 )
- do i have to contact a service provider ?
My idea was initially to set up the SAProuter on the same computer as the SOLMAN setup & use SNC communication to communicate with SAP but it doesn't seems that easy. Do i need separate installation for Saprouter <=> Solution Manager. ?
What's the minimal infrastructure to establish this connection ?
In addition to that, after configuring the SAProuter, i had trouble with the SAPMMC : on my system , on the instance 0 , the process disp+work.EXE won't run ( yellow light )and i can't find where i made a mistake if you have suggestions ...
Really need your help, i'm on a short deadline ... Any help, even incomplete, would be appreciated.
Thanks a lot.

Thx for the answer.
I actually managed to register my saprouter with SAP and was granted with CN/OU & connection informations.
I followed this guide : http://service.sap.com/saprouter-sncdoc with the addition of this guide : http://wiki.sdn.sap.com/wiki/display/Basis/SAProuterviaSNC.
My first issue : I'm running with a Windows server 2008 r2 enterprise edition 64 bits with a processor Intel Xeon 2.4ghz ( dualcore). so i decided to use the crypto folder "nt-x86_64"
For the environment variable i set as System variables SECUDIR = C:\usr\sap\saprouter and SNC_LIB = C:\usr\sap\saprouter\nt-x86_64\sapcrypto.dll
The generation/install of the certificate is alright ( sapgenpse get_my_name -v -n Issuer is OK )
using the command :saprouter -r -K "p:CN=mycn, OU=myOUnbr, OU=SAProuter, O=SAP, C=DE" i have
I get the following message : trc file     dev_rout
                                                no ligging active
Its strange cause it looks like its running but when i check the services running on windows saprouter isn't started .... How to know if SAProuter is running right ?
If i folow the SAP procedure : Step 3 : test of the ip connection by the customer : SAP Remote Services : technical preparation ( see SAP Note 812386 ) : it's ask in the note to implement note 766505 via SNOTE : i get the following error msg : Error in remote connection to destination SAPOSS : Error when opening an RFC connection ( LB: Hostname or service of the message server unknown#DEST = SA
What's wrong ?
If i use T oss1 in parameter => technical setting => i set my saprouter info in SAProuter 1 ( at customer site ) with instance no. 99 and if SAProuter and SAPNet Message Server at SAP i put the following : Name : sapserv2 / IP Address 194.39.131.34 intance no. 99 and message server name oss001/ DB Name 001/ Instance no.01.
When trying to "Logon to SAPNet" i have an error Unable to connect to SAPNet message server ( default connection will be used ... )
and followed by the error screen : "partner '80.15.173.168:sapdp99' not reached WSAECONNREFUSED : Connection refused. do you want to see the detailed error description ? "
Details : module nixxi.cpp / line 3286 / Method : NipConnect2:80.15.173.168:3299 / Return code : -10 / System call : connect / Error No : 10061 / Error Text WSAECONNREFUSED: Connection refused / Counter : 10
Any idea ?
when doing niping.exe -c -H /H/mylocalSR/H/194.39.131.34/H/194/39.131.34 i obtain :
Wed Dec 07 21:20:09 2011
connect to server o.k
Wed Dec 07 21:20:09 2011
send and receive 10 messages (len 1000)
times -
avg   122.148 ms
max   193.731 ms
min   81.564 ms
tr 15.990 kB/s
excluding max and min :
av2   118.273 ms
tr2   16.514 kB/s
Is it the expected output ?
I've maintained system data in service.sap.com/system-data ( selecting the sap router ) then i tryed to use the SAP service connection, downloaded the .exe but i can't find the stfk.oez. I realized that in my maintain connection screen i have no space for entering any routestring. Seems wrong ?
Do i have to use the SAO?
i've made nat redirection from my router as this : from my public ip to my lan ip ( 192.168.x.x) what should i enter in the routestring : /H/public or lan or hostname ?/S/3299 ?
Hoping you can help me ! ( the goal of all this is to set up RFC connection for postinst step of Solution manager ).
Edited by: BLANCHARD Guillaume on Dec 7, 2011 10:47 PM

SAP Solution Manager Certification

Hi there!
I would like to give Certification exam in SAP Solution Manager 4.0.
Pertaining to this could anybody share the related PDF Files.
Regards,
Suresh

Hello,
I've tried to get to some Sample Questions here on Forum, but I couldn't get any.
I passed an exam on 14.11.2006 and I suggest to you to use course materials as suggested by SAP (SMI310). That is sufficient to pass the certificate. All the answers are there.
My general opinion: not easyYou have to be pretty much concentrated as there were questions put in negative expressions.You have to be really, really carefull.
They are taking a lot of details on subjects like Type of projects (Template projects, Roll out implementations, customer satisfaction) including its Roadmaps. (e.g. roll-out project phases and its content.)
I only saw 3 or 4 questions familiar to me (from Test your knowledge, SMI310 book), others were really related to course materials but spoken in their own words
If you have any questions, dont hesitate to contact me.
Good luck to you and best regards.
Nikolina

Managed System Configuration: SSO setup failed for Solution Manager 7.1 sp11

Hi Folks,
While doing Managed System Configuration for Soman system i am getting error in SSO Setup
Currently I am in
8. Configure Automatically :Single Sign On Setup
This is i am going for managed System (Solution Manager System Itself)
Below is error log..
SSO setup failed : a problem occured while attempting to add login modules for ticket authentication
Screen shot attached.
Found SID for SSO ACL entry : SMP
Found login.ticket_client for SSO ACL entry : 000
The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tc~webadministrator~solmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar
The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (619 bytes)
The SSO ticket Certificate <OU=J2EE,CN=SMP> has been successfully imported into ticket Keystore
SSO setup failed : a problem occured while attempting to add login modules for ticket authentication
SSO setup failed : error while updating login modules : Caller not authorized.; nested exception is:
java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
The SSO ticket Certificate <CN=SMP> has been successfully imported into ticket Keystore
SSO setup failed : a problem occured while attempting to add login modules for ticket authentication
SSO setup failed : error while updating login modules : Caller not authorized.; nested exception is:
java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Exception
java.rmi.RemoteException: Caller not authorized.; nested exception is:
java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:160)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: Caller not authorized.
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:634)
at com.sap.engine.services.security.resource.ResourceHandleImpl.checkPermission(ResourceHandleImpl.java:520)
at com.sap.engine.services.security.resource.ResourceContextImpl.checkPermission(ResourceContextImpl.java:45)
at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:170)
at com.sap.engine.services.security.restriction.Restrictions.checkPermissionRemote(Restrictions.java:158)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImpl.getPolicyConfiguration(RemoteSecurityImpl.java:63)
at com.sap.engine.services.security.remoteimpl.RemoteSecurityImplp4_Skel.dispatch(RemoteSecurityImplp4_Skel.java:225)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:336)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:201)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:137)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
at com.sap.engine.services.security.exceptions.BaseSecurityException.writeReplace(BaseSecurityException.java:349)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:910)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1024)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1344)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1316)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1260)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1065)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:282)
at com.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:147)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:338)
... 8 more
Regards,
San

Hi Sandeep,
It seems authorization issue. Please check the below SAP Note :
1988642 - Warning 'caller not authorized' in Step 'Single Sign On Setup'
Hope this helps.
Thanks & Regards,
Nisha

SAP Solution Manager Certification Examination

Hello,
I am planning to take up 'SAP NetWeaver - Solution Manager Implementation Tools' Certification Examination during SAP TechEd 06. I wanted to get some kind of sample qusetion/test papers for the same.
I would be grateful if anyone could guide me as to how to go about the preparation and where to get the sample paper & other study material from?
Also, I wanted to know what level of knowledge do they expect us to have?
Regards,
Kavitha

Hello,
I've tried to get to some Sample Questions here on Forum, but I couldn't get any.
I passed an exam on 14.11.2006 and I suggest to you to use course materials as suggested by SAP (SMI310). That is sufficient to pass the certificate. All the answers are there.
My general opinion: not easyYou have to be pretty much concentrated as there were questions put in negative expressions.You have to be really, really carefull.
They are taking a lot of details on subjects like Type of projects (Template projects, Roll out implementations, customer satisfaction) including its Roadmaps. (e.g. roll-out project phases and its content.)
I only saw 3 or 4 questions familiar to me (from Test your knowledge, SMI310 book), others were really related to course materials but spoken in their own words
If you have any questions, dont hesitate to contact me.
Good luck to you and best regards.
Nikolina

No active master Solution Manager destination maintained. [Maintenance Pack

Hi,
I want to activate Automatic Maintenance Certificate Renewal via solution manager system as per SNOTE: 1280660.
SOL MAN: ST400 SP 18
SCM : ST-PI 2008_1_700 SP 01
when i run Maintenance package in my managed (satellite) system i got the log as below.
Updating license data not possible Maintenance Package
No active master Solution Manager destination maintained. Maintenance Package
Updating license data completed from destination Maintenance Package
Maintenance Package completed
when i run Maintenance package in my Solution Manager system i got the log as below.
Refresh sessions from destination SM_KSMCLNT000_BACK started Maintenance Package
error reading function module interface DSWP_API_SESSIONLIST_GET from SM_KSMCLNT000_BACK
Logon not possible (error in license check)
Sessions cannot be refreshed from destination SM_KSMCLNT000_BACK ( KSM , 0020472195 )
Refresh sessions from destination SM_KSMCLNT000_BACK finished Maintenance Package
Refresh sessions from destination SM_KSMCLNT001_BACK started Maintenance Package
error reading function module interface DSWP_API_SESSIONLIST_GET from SM_KSMCLNT001_BACK
Logon not possible (error in license check)
Sessions cannot be refreshed from destination SM_KSMCLNT001_BACK ( KSM , 0020472195 )
Please anyone facing the same or related issue, give me a suggestion..
Thanks,
Manikandan B

HI Paul,
Thanks for ur suggestion. I have resolved this issue. now certificates are automatically updated.
But i got the error from maintenance task... for all system.
"RFC error when trying to report license key status back to Solution Manager System SM_KSMCLNT200_"
on report name "/SDF/SAPLLICENSE_KEY_UPDATE"
Kindly advise me..
Thanks,
Manikandan B

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

Solution Manager Certificates

Similar Messages

Maybe you are looking for