Reset Solution Manager configuration

Hello experts,
We are setting Solution Manager up for incident management but the configuration was started without SP15 and many things were manually done so now, there are a lot of users and even systems that weren't succesfuly created... bottom line, the configuration is a mess. Is there any way to reset this configuration and start over? I specially want to delete ibase's, systems and bp's.
What would you suggest?
Thanks in advance

Hi Maria,
There isn't an easy way to whipe everything out and start fresh. However, you can archive messages, update your iBase, retire BP's and fix your system landscape. You can even delete BP's if they are not assigned to messages. If they are, I read of a fix where someone replaced the BP's in the tables and then was able to delete them. If you can't delete your iBase it's because you don't have an SAP note installed.
If you browse the forum for each of the items you want to fix, you'll find the info.
regards,
Jason

Similar Messages

Solution manager configuration diagnostic host agent

Hi experts,
I am configuring the solution manager 7.1 SP9, I have one doubt whether our systems contains diagnostic host agent or not.
in sapmmc at the time of restarting the sap services i found that DAA is there.So i got this doubt. Please clarify what is diagnostic host agent and SAPHost agent and also please provide any material for solution manager configuration. I am not getting clarity from google.
Thanks&Regards,
Patan Thavaheer.

Hi,
I executed the given command successfully in daaadm user.In command prompt it is showing that "task completed with status success".But in solution manager it is not getting visible. I checked in log file SMDsystem.0.log , i found exception in the log.
find the exception
migsolman.milltec.com:8001 Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: 192.168.140.47 and port: 8001]
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       Detect possible changes in runtime.properties, reload data and restart the agent connection.
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       SLD configuration not found to register the agent, SLD Agent Registration is skipped.
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       Reconnection in progress...
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       [SMDConnector.reset] in progress ...
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       [SMDConnector.reset] invalid the agent handle com.sap.smd.agent.AgentHandle@1db9b30c.
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       Reading JStartup environment...
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       'SAPLOCALHOST' found, The value 'MIGDev' will be used to determine the Agent name.
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       InetAddress Resolving for 'MIGDev' - FQN: migdev.milltec.com SQN: MIGDev IP: 192.168.140.45
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       InetAddress Resolving for localhost - FQN: migdev.milltec.com SQN: MIGDev IP: 192.168.140.45
Sep 16, 2014 10:55:55 AM [Thread[Agent Configuration Monitor,1,main]   ] Info       [SMDConnector.reset] Done.
Sep 16, 2014 10:56:14 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] reset the p4 broker (close:true)
Sep 16, 2014 10:56:14 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] p4 broker closed.
Sep 16, 2014 10:56:14 AM [Thread[Connector,5,main]                     ] Info       Local P4 port opened on port '59704'.
Sep 16, 2014 10:56:14 AM [Thread[Connector,5,main]                     ] Info       Local P4 server configured with transport layer 'None'.
Sep 16, 2014 10:56:14 AM [Thread[Connector,5,main]                     ] Info       [P4ServerController] Remote object 'com.sap.smd.agent.remote.handle' (com.sap.smd.agent.AgentHandle@29bbbce6) is available in P4 Object Broker.
Sep 16, 2014 10:56:14 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] p4 broker initialized.
Sep 16, 2014 10:56:14 AM [Thread[Connector,5,main]                     ] Info       [p4://migsolman.milltec.com:8001] Checking server availability...
Sep 16, 2014 10:56:45 AM [Thread[Connector,5,main]                     ] Error      Failed to connect to SMD server - user: basisadm
Sep 16, 2014 10:56:45 AM [Thread[Connector,5,main]                     ] Warning    Connecting to SMD server p4://migsolman.milltec.com:8001 failed - error counter: 19 - com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: Cannot establish connection with any of the available instances:
migsolman.milltec.com:8001 Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: 192.168.140.47 and port: 8001]
Sep 16, 2014 10:57:20 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] reset the p4 broker (close:true)
Sep 16, 2014 10:57:20 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] p4 broker closed.
Sep 16, 2014 10:57:20 AM [Thread[Connector,5,main]                     ] Info       Local P4 port opened on port '59704'.
Sep 16, 2014 10:57:20 AM [Thread[Connector,5,main]                     ] Info       Local P4 server configured with transport layer 'None'.
Sep 16, 2014 10:57:20 AM [Thread[Connector,5,main]                     ] Info       [P4ServerController] Remote object 'com.sap.smd.agent.remote.handle' (com.sap.smd.agent.AgentHandle@29bbbce6) is available in P4 Object Broker.
Sep 16, 2014 10:57:20 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] p4 broker initialized.
Sep 16, 2014 10:57:20 AM [Thread[Connector,5,main]                     ] Info       [p4://migsolman.milltec.com:8001] Checking server availability...
Sep 16, 2014 10:57:51 AM [Thread[Connector,5,main]                     ] Error      Failed to connect to SMD server - user: basisadm
Sep 16, 2014 10:57:51 AM [Thread[Connector,5,main]                     ] Warning    Connecting to SMD server p4://migsolman.milltec.com:8001 failed - error counter: 20 - com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: Cannot establish connection with any of the available instances:
migsolman.milltec.com:8001 Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: 192.168.140.47 and port: 8001]
Sep 16, 2014 10:58:26 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] reset the p4 broker (close:true)
Sep 16, 2014 10:58:26 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] p4 broker closed.
Sep 16, 2014 10:58:26 AM [Thread[Connector,5,main]                     ] Info       Local P4 port opened on port '59704'.
Sep 16, 2014 10:58:26 AM [Thread[Connector,5,main]                     ] Info       Local P4 server configured with transport layer 'None'.
Sep 16, 2014 10:58:26 AM [Thread[Connector,5,main]                     ] Info       [P4ServerController] Remote object 'com.sap.smd.agent.remote.handle' (com.sap.smd.agent.AgentHandle@29bbbce6) is available in P4 Object Broker.
Sep 16, 2014 10:58:26 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] p4 broker initialized.
Sep 16, 2014 10:58:26 AM [Thread[Connector,5,main]                     ] Info       [p4://migsolman.milltec.com:8001] Checking server availability...
Sep 16, 2014 10:58:56 AM [Thread[Connector,5,main]                     ] Error      Failed to connect to SMD server - user: basisadm
Sep 16, 2014 10:58:56 AM [Thread[Connector,5,main]                     ] Warning    Connecting to SMD server p4://migsolman.milltec.com:8001 failed - error counter: 21 - com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: Cannot establish connection with any of the available instances:
migsolman.milltec.com:8001 Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: 192.168.140.47 and port: 8001]
Sep 16, 2014 10:59:31 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] reset the p4 broker (close:true)
Sep 16, 2014 10:59:31 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] p4 broker closed.
Sep 16, 2014 10:59:31 AM [Thread[Connector,5,main]                     ] Info       Local P4 port opened on port '59704'.
Sep 16, 2014 10:59:31 AM [Thread[Connector,5,main]                     ] Info       Local P4 server configured with transport layer 'None'.
Sep 16, 2014 10:59:31 AM [Thread[Connector,5,main]                     ] Info       [P4ServerController] Remote object 'com.sap.smd.agent.remote.handle' (com.sap.smd.agent.AgentHandle@29bbbce6) is available in P4 Object Broker.
Sep 16, 2014 10:59:31 AM [Thread[Connector,5,main]                     ] Info       [SMDConnector.resetBroker] p4 broker initialized.
Sep 16, 2014 10:59:31 AM [Thread[Connector,5,main]                     ] Info       [p4://migsolman.milltec.com:8001] Checking server availability...
Regards,
Patan Thavaheer.

IT Service Management (Solution Manager - Configuration)

Dear Expert!
We are using SM 7.1 SP11.
The System Preparation and Basic Configuration has been done
Now, we want to configure the IT Service Management under the Solution Manager Configuration.
There are some steps are manual in the standard configuration;
1) Configure Manually
2) maintain Transaction Types
3) Configure Automatically
4) Perform Additional Configuration
5) Create Template users.
I don't aware by the manually steps, what should be provide in the manual configuration.
I have downloaded document ITSM Configuration Part 1 and 2 but material does not discuss about the steps to executed in the configuration.
Please advise
Regards

Hi Anwer,
Go to service.sap.com/instguides
from here you can go to S -> SAP Solution Manager -> on the right pane scroll down and click on
Planning, Installation, Upgrade Guides -> Look under Additional Guides - ITSM you will find the required documentation.

System registered in SLD invisible in solution manager configuration

Hi
I have installed Solution Manager EHP1 / Oracle 10g / Win2003 on a VM. I ran into a issue in the Managed system configuration. The first step in the maanaged system configuration would help us select the satelllite systems which and configured in the SLD. Since systems were not yet added to SLD just the solution manager system shows up.
Here is the problem
I have added one system to the SLD using "Add Technical system" from http://localhost:50000/sld. This is a ABAP sysystem. The addition went through successfully however this does not reflect when I check the same in solution manager configuration "Managed system configuration"
As per the guide in the same page, I have checked on "Maintain Technical systems" Here too when I search for the system I created in SLD , I am not able to find it. Is there another way of manually maintaining the system in the SLD?
Any ideas as to why this might happen? Does one have to bounce the instance after adding systems to SLD/.... just wondering?
Ideas?
thanks
Ravi

Hi Rajeev
Thanks for your response however I fixed it. It looks like I had incorrectly mentioned the host in RZ70. Instead of mentioning the hostname of the solution manager I had mentioned the host name of the satellite system
The below link helped me fix the issue
http://help.sap.com/saphelp_nwpi71/helpdata/en/e7/01503ede925441e10000000a114084/content.htm
thanks
ravi

SAP Solution manager configurations

Hi Experts,
I need to do Solution manager configuration ,but i don't have idea about this.could you please help me and before start the configuration what is the prerequisites for configuration.
I need all above steps information what is the use of every one and tell me prerequisites for all steps.
Please help me any one.It is helpful for me.
Thanks
J Jana

Hi Janardhan,
Please download the System Monitoring and technical monitoring guide
https://websmp103.sap-ag.de/~sapidb/011000358700000409042011E
Please watch the EEM demo
https://websmp103.sap-ag.de/~sapidb/011000358700000383412011E/index.htm
Please watch demo for connection monitoring
https://websmp103.sap-ag.de/~sapidb/011000358700000479272011E/index.htm
Please Downlaod Technical Administration guide
https://websmp103.sap-ag.de/~sapidb/011000358700000592062012E.pdf
ITSM:Part 1
https://websmp103.sap-ag.de/~sapidb/011000358700000608542012E.pdf
Part 2: https://websmp103.sap-ag.de/~sapidb/011000358700000608872012E.pdf
Happy Learning.
Vinod Palli

Solution Manager Configuration

Hi All,
I want to configure Solution Manager for Support Activities and their reporting like creation of tickets by end user, resoultion time according to category. I need a documentation on the same if possible some configuration document.
Help on the same!!!!
Anurag

Hi Raghav,
Kindly check missing authorizations of user solman_btc.
Regards,
Varenyam Trivedi

Solution manager configuration for EHP4 install (Product Version Problem)

Hi guys!
I'm new on SAP and SDN is a help all days and this time i really need some help from you guys!
Im installing EHP 4 and need the XML Stack file, so i go to the solution manager to generating them. But after configuring the logical components, make the associations, etc. on create maintenence transaction, the product version dropdownlist is empty...
It is configured but it dont appears... Anyone had this problem before and could give me some help!
I will appreciate that!
My regards,

Hi,
In SMSY, the system should have product version as SAP ERP 6.0.
Next the logical component created for ECC Server should also reflect this version.
The solution you create in DWSP should include this logical component via the Solution Landscape definition. Here again the logical component should show the product version.
If all above are in place, the MOPZ for the respective solution should have the product version list populated.
Regards,
Srikishan

Solution manager configuration for SRM

Hi all
we are goin to configure SAP SRM 5.0. we need to configure standard business scenarios in solution manager for the same.can somebody provide relevant links and documents regarding where to find these in solution manager and how to go about this?this would be really helpful.points would be awarded immediately.

Hi Harsa,
Here you can find the Webex recorded sessions
https://websmp207.sap-ag.de/~sapidb/011000358700000429402008E
Hareesha

Transport Solution Manager configuration between systems

Hello all,
I created a configuration project for service desk on spro_admin on development environment. Then configured all the basic steps for service desk. Now how can move things to quality system and then to Prodution? Is it enough to create a project transport or do I need anything else? Because when I created a project transport (from spro_admin) it only added a few things to it, not all objects I've customized. My concern is that BC sets for example won't be imported in the other systems or so.
Any guides on this?
Regards,
Ricardo

Hi,
>
Ricardo Dias wrote:
Is it enough to create a project transport or do I need anything else?
Create a Project Transport? what do you want to do? If there is anything in a Transport request it can be obviously imported into your QAS and to PRD, you need to decide if you have completed the config.
>
Ricardo Dias wrote:
Because when I created a project transport (from spro_admin) it only added a few things to it, not all objects I've customized.
> Ricardo
What did you actually do? were the changes not imported completely?
Feel free to revert back.
-=-Ragu

Configuring Solution Manager: Alternative Role to SAP_ALL

This is a general question regarding configuring Solution Manager and note 834534. I am configuring Solution Manager 7.0 at a client site. The main components that I am configuring are on the Monitoring and Operations side; for example, System Monitoring, Service Desk, Issue Management, and Change Management for Maintenance Optimizer. CHaRM will follow later on. Additionally, the client would like to use the project side of Solution Manager.
When I took training for Solution Manager from SAP, the SAP instructor advised the class to have SAP_ALL when configuring Solution Manager The problem I am having is that the client will not issue me SAP_ALL in the Solution Manager instance, regardless of the recommendation in note 834534. I can understand the client's reluctance to issue SAP_ALL, even though Solution Manager is not a financial system in of itself, however, I have found that I am constantly having to ask for authorizations as I step through the wizards and the Scenario-specific settings. When I run into issues which require further investigation by running transactions to check certain settings that are not specifically tiedd to a wizard or scenario-specific setting transaction, I run into further delays as I ask for additional authorizations to troubleshoot issues.
We have implemented the roles and assigned them to my ID in Solution Manager as outlined by the SAP Solution Manager Security Guide to the fullest extent possible; and I have been issued "Basis Roles" that the client issues to their Basis team. Regardless of these actions, I still run into authorization issues.
My question is, apart from the SAP Solution Manager Security Guides recommendations (which does not mention SAP_ALL), is there a role being developed, or has been developed that can be assigned to the Solution Manager configurator in lieu of SAP_ALL (as per note 834534)? I would think that this issue has been raised before, particularly since many companies have implemented SOX controls and are skittish about issuing SAP_ALL.
Your feedback is most appreciated.

Thanks for the reply, Nesimi.
While I appreciate that you do not use SAP_ALL, is that the case when you are configuring a brand new, clean system? Are you using the Configuration Wizards with out SAP_ALL? I ask this because when I ran the first configuration wizard, one of the steps is to create a "configuration user", which creates a user with SAP_ALL. However, I cannot use that wizard generated user ID because it has the role SAP_ALL.
In general, I am operating on 3 sources of information that says I need SAP_ALL to configure the system (not necessarily to operate it):
1. An SAP Instructor for the Solution Manager Operations and Monitoring Class
2. The IMG Activity "Create Configuration User" documenation in SPRO
3. Note 834534
I will review the english version of the link http://help.sap.com/saphelp_smehp1/helpdata/de/40/8ac473d40943ddb23def12bdb33437/frameset.htm that you have thoughtfully provided.
With respect to note 123640, I am not sure if that solves my problem or answers the fundemental question that I have in that given the 3 sources I quoted above. It seems to me that SAP's approach in indicating clearly that they prefer that the configuration user should have SAP_ALL is flawed given today's corporate governence policies. Clearly this recommendation is only for the initial configuration, and SAP_ALL can be taken away and replaced by the roles and recommendations in the SolMan security guide; to maintain Solution Manager. But when it comes down to the question "what do you need to configure Solution Manager, because we won't give you SAP_ALL", I am hard pressed to give an answer despite literally spending hundreds of hours researching "documenation" which does not give clear cut answers. I think SAP needs to address this issue instead of taking the easy way out and saying you need "SAP_ALL" as illustrated in the 3 sources of readily available information cited above.

Configuring the Alert monitoring of Solution Manager 4.0

Dear all,
How can I notify from the central monitoring system when alerts happened?
I have already create and assign auto-reaction method to specific monitor attribute with alerts, but nothing happend. I even looked at the table CSMCENTOOL where the alert data suppose to stored, and the table is still empty.
I will be greatfull if anyone can provide me appropriate document in this matter, or guide me with a list of things that need to be done.
Kind regards,
Yagel

Hi Kai,
Thanks for your quick response.
I have already create and assign the central auto-reaction method exactly as in the example,
and when I try to start the auto-reaction method I receive the alert information "Cannot determine data for method DUMMY_TOLL_FOR_DOUBLEHOP".
I have overcome this alert information by changing the excute method of the defined central auto-reaction from Only in central system, trigged by CCMS agents to Periodically in process(Short running program), and still, nothing notify when alert happened.
Should I configure the "Related Solution Manager configuration guides on SDN" which describe in the bottom blug as well?
I also didn't understand you when you say to send from SAP-System to another account?
Thanks in advance,
yagel.

Solution manager charm configure

hello everyone
i want to configure the charM scope with our R3 and BW at two domain .
R3 landscape
                    DEV(101sandbox,201-develop,301-customizing ,800unit testing)
                    QAS(800- testing)
                    PRD(800-prduct)
tranport   from DEV TO QAS and delivery to PRD ,also you can export the object from QAS to PRD for special .
domain controller is PRD
BW landscape BWD(client 100)--BWQ(client 880)BWP(client 880)
domain controller is BWP
if we use the charM for manager the change requst ,how we configure in all system for prepare the charM like the stms configure .
we notice our test system and prd system have same client number ,so it is ok for configure ?
expect your help!
thanks a lot!
frank

Hi,
1 QAS client and PRD client can be the same(need not to be different).
2. Make sure that the system landscape you mention under system landscape tab of SOLAR_PROJECT_ADMIN should match with TMS configuration of Solution Manager.(This is very important).
You should create a maintenance project with system landscape DEV-201->QAS-200->PRD-200 using SOLAR_PROJECT_ADMIN. Repeat this step for BW also.
   You need to configure TMS of Solution Manager in Client 000 as follows:
    SLM->DEV-201->(Consolidation Route)QAS-200->(Delivery Route)PRD-200
    SLM->BW-100->(Consolidation Route)BW-880->(Delivery Route)BW-880
No more document is required better than SPRO. Just follow this SPRO path to configure TMS:
SPRO->SAP Solution Manager->Configuration->Scenario-Specific Settings->Change Management
->Change Request Management->Standard Configuration->Transport Management System(Read IMG activity of each step).
Let me know if you have aby issues.
Regards,
Sanjai

How to start the Solution Manager Implementation

Hi Gurus , I am in Solution manager implemnetation project , and i wanted built the exsisted landscape into Solman so any one can help me out in this like where to and how to start.

Hi Gurus, i wanted to implement these concepts
Configuring Solution Manager
Configuring Solution Manager
1)      Solution Monitoring
a       SAP EarlyWatch Alert
a1      Setting-Up EarlyWatch Alerts    Y
a2      Manually Executing Downloads    Y
a3      Create Report and Display Session Details       Y
a4      Save, Retrieve and Archive EarlyWatch Alert     Y
b       Service Level Reporting
b1      Service Level Reporting Change Mode     Y
b2      Maintain General Settings       Y
b3      Specify Systems and Contents for Service Level Report   Y
b4      Select Business Processes for the Service Level Report Y
b5      Select Business Processes from the Business Process Monitoring Y
b6      Process Service Level Report Data Manually      Y
b7      Create Service Level Report     Y
b8      Create, Save and Archive Service Level Report Manually Y
b9      Process Service Level Report Session    Y
b10     Send E-Mail Automatically       Y
b11     KPI Calculation Y
2       Configuring Alert Monitor
       Central System Administration (Part of ALERT Monitor)
c2.1    MTE Classes and Attribute Groups        Y
c2.2    Methods Y
c2.3    Operating the Alert Monitor     Y
c2.4    Actions in the Alert Monitoring Tree    Y
c2.5    Selecting Nodes in the Alert Monitoring Tree    Y
c2.6    Elements of the Alert Monitor   Y
c2.7    General Properties of Monitoring Tree Elements Y
c2.8    Properties of Monitoring Objects and Attributes Y
c2.9    Customizing the Alert Monitor   Y
c2.10
Changing Properties in the Alert Monitoring Tree
       Y
c2.11
Changing Properties in Customizing Transaction RZ21
       Y
c2.12
Triggering a Heartbeat Alert if No Values Are Reported
       Y
c2.13
Changing the Frequency of Method Execution
       Y
c2.14   Defining, Releasing, and Transporting Methods
       Y
c2.15
Assigning Methods to MTE Classes or Individual MTEs
       Y
c2.16   Assigning Methods to MTE Classes or Individual MTEs     Y
c2.17
Editing Monitors and Monitor Sets
       Y
c2.18
Creating and Editing Monitor Sets
       Y
c2.19   Transporting Monitor Sets and Monitor Definitions       Y
c2.20   Copying, Renaming, and Deleting Monitors        Y
c2.21   Creating and Changing Monitors Y
c2.22   Rule Node: Rule Description and Use     Y
c2.23   Defining Monitors with the DEFINE_R3_SYSTEMS/GET_MTE_BY_CLASS Ru        Y
c2.24   Defining Monitors with the Rule GET_MTE_BY_CLASS_AND_OPTIONS    Y
c2.25   Defining Monitors with the Rule GET_MTE_BY_CLASS_AS_VIRTUAL     Y
c2.26   Copying a Monitoring Properties Variant Y
c2.27   Create Monitoring Properties Variant    Y
c2.28   Change Monitoring Properties Variant    Y
c2.29   Activating a Monitoring Properties Variant      Y
c2.30   SAP-DEFAULT     Y
c2.31   Creating a New SAP-DEFAULT Variant      Y
c2.32   Monitoring Multiple Systems     Y
c2.33   Monitoring Multiple Systems: Defining RFC Connections   Y
c2.34   Monitoring SAP R/3 3.x Systems Y
c2.35   Creating the CSMREG User        Y
c2.36   Monitoring Multiple Systems with an Identical System ID Y
c2.37   System Groups in the Alert Monitor      Y
c2.38   Deactivating and Reactivating Monitoring Tree Elements Y
c2.39   Deleting and Restoring Nodes in the Alert Monitoring Tree       Y
c2.40   Display Options of the Alert Monitor    Y
c2.41   Saving and Resetting the Layout of a Monitor    Y
c2.42   Extending the Shared Memory Area        Y
c2.43   Setting Up a Central Data Cache         Y
c2.44   Configuring the Caches of the Monitoring Architecture   Y
c2.45   Working with All-Clears (Green Alerts) Y
c2.46   Displaying the History of the Threshold Values of Performance No        Y
c2.47   Availability Monitoring with CCMSPING   Y
c2.48   Installing Availability Agent CCMSPING Y
c2.49   Changing the Monitoring Frequency and Timeouts of CCMSPING      Y
c2.50   Adding Systems to the Availability Monitoring Manually Y
c2.51   Finding and Correcting Errors with CCMSPING     Y
c2.52   Configuring Availability Monitoring     Y
c2.53   Creating and Changing Monitoring Rules Y
c2.54   Changing Monitoring Setting of Servers and Groups       Y
c2.55   Using Multiple CCMSPING Agents Y
c2.56   Creating and Changing a Monitoring Pause        Y
c2.57   Monitoring System Groups with CCMSPING Y
c2.58   Availability and Performance Overview Monitor   Y
c2.59   Monitoring Log Files with CCMS Agents   Y
c2.60   Structure of the Log File Template of the Log File Agent        Y
c2.61   Example Log File Templates      Y
c2.62   Logfile Monitoring Monitor      Y
c2.63   Monitoring Selected Processes with SAPOSCOL     Y
c2.64   Monitoring Response Times of Transactions or Clients    Y
c2.65   Monitoring Database Tables with the Alert Monitor       Y
c2.66   Self-Monitoring of the Alert Monitor    Y
c2.67   Selected Alert Monitor Methods Y
c2.68   Forwarding Alerts to Alert Management (ALM)     Y
c2.69   Interpreting a Text Attribute as File Name/URL and Display Content      Y
c2.70   Displaying a Subtree as ALV Grid Control        Y
c2.71   Defining an Automatic Alert Notification        Y
c2.72   Auto-Reaction Method: Execute Operating System Command Y
c2.73   Setting Up Central Auto-Reaction Methods        Y
c2.74   Installing CCM4X        Y
c2.75   Activation in the background,if the Host restarts       Y
c2.76   Creating RFC Connection Y
c2.77   Copying File from Solution manager to agents    Y
c2.78   Copying version for SAPCCM4X    Y
c3      Central User Administartion(CUA)
c3.01   Create manaintain landscape     Y
c3.02   Creating RFC    Y
c3.03   Create Logical clinets in SM1   Y
c3.04   Field distribution parameters   Y
c3.05   Transfering users from child system     Y
2       Service Desk
a       Set-Up Message Creation in Web Browser Y
b       Create support messages with NOTIF_CREATE       Y
c       Process Messages in Service Desk        Y
d       Search for Solutions to Support Messages        Y
e       Copy Support Message into Solution Database     Y
f       Forward Support Message to SAP Y
g       WebClient Interaction Center    Y
h       Create Messages with Interaction Center WebClient       Y
i       Process Messages in the Interaction Center WebClient    Y
j       Service Desk for IT Service Providers   Y
k       Using an External Service Desk Y
l       Connect an External Service Desk        Y
m       Service Desk Customizing Error Analysis Y
it's very high prioriety
Cheers

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.

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

Reset Solution Manager configuration

Similar Messages

Maybe you are looking for