Capabilities of Solution Manager

Hi all-
Commencing a fresh implementation of NW2004s with ECC, BI and Sol Mgr in-scope (EP and XI out-of-scope for now). Have to create numerous custom interfaces in ECC. Does Sol Mgr have the ability to monitor these interfaces and message (E.g. Email/pager/etc.) when exceptions are encountered in the ECC custom batch interfaces? If so, what is monitored? The system log, application log, events,...? Basically, would prefer to offload email/pager notification to Sol Mgr rather than code for these in ECC. Suggestions/recommendations appreciated.
Thanks,
Pat

Hi Pat,
please find the link with details on system monitoring details from SSM.
http://help.sap.com/saphelp_nw04/helpdata/en/5b/0c9ccfd262427685c245d7ea85cd7a/content.htm
The CCMS monitoring architecture is well defined in SSM as well and the link is as follows.
http://help.sap.com/saphelp_nw04/helpdata/en/c4/3a7da1505211d189550000e829fbbd/frameset.htm
A quick read on these would give you a good look of the fucntionality.
Caoming to Process monitoring you can also have ALerts customized for seperate Business processes in BPM and its a lovely feature over there.
using it is described here,
http://help.sap.com/saphelp_nw04/helpdata/en/9a/e435e7fa6f4e85a70885a36479be4e/content.htm
Let me know if the links are helpful, or am i confusing u with a lot of links.
Thanks for the points,
Br,
Sri

Similar Messages

Solution manager maintenance optimizer

Hi all,
I have what I think is an issue, and hoping someone could possibly point me in the direction to correct. I have setup our solution manager system and trying to get the maintenance optimizer option working fully. I have a java system that I pull the information from SLD perfectly fine, and it lists all installed software components via SMSY>SYSTEMS perfectly. I have assigned logical components etc. I can create a new maintenance optimizer transaction, select the proper system with assigned components, but when it lists the files to be downloaded automatically I expect to see alot more files available for download than it lists for me. I assume I am missing something, but not sure where to look.
Would anyone be able to possibly point me in the right direction on what I might be missing?
Regards,
Chris

Hi Markus,
The system is SAP EHP1 for SAP Netweaver 7.0. It has the following components installed and specified in logical components:
Adobe Document services
Application server Java
EP Core
Enterprise Portal
Along with the kernel files I also get the following files available for download via maintenance optimizer (6 in total)
FORUMS06_0-10005892.SCA SP06 for FORUMS 7.01
BP_PROJ_PORT_DESIGNCOLL
BPPPMDC17_0-10003174.SCA BP PROJ., PORT. & DCOL. 4.0 SP17
BP ERP05 PROJ SELF-SERV
BPERP5PSS17_0-10003284.SCA BP ERP05 PROJ SELF-SERV 1.0 Support Package 17
BP ERP05 MAINTENANCE TECH
BPERP5MTC07_0-10004455.SCA SP07 for BP ERP05 MAINTENANCE TECH 1.2
BP ERP SITE TECHNICIAN
BPIS7TST07_0-10004458.SCA SP07 for BP ERP SITE TECHNICIAN 1.20
BP ERP ICM ANALYST
BPIS7ICMAL06_0-10006119.SCA SP06 for BP ERP ICM ANALYST 1.41
When I look at installed system components via SMSY it correctly shows everything installed which includes:
ADOBE DOCUMENT SERVICES 7.01 0006 SP006 ADOBE DOCUMENT SERVICES 7.00
BI BASE SERVICES 7.01 0006 SP006 BI BASE SERVICES 7.01
BI INFORM. BROADCASTING 7.01 0006 SP006 BI INFORM. BROADCASTING 7.00
BI META MODEL REPOSITORY 7.01 0006 SP006 BI META MODEL REPOSITORY 7.01
BI REPORTING AND PLANNING 7.01 0006 SP006 BI REPORTING AND PLANNING 7.01
BI UNIVERSAL DATA INTEGRATION 7.01 0006 SP006 BI UNIVERSAL DATA INTEGRATION BI UDI 7.01
BI WEB APPLICATIONS 7.01 0006 SP006 BI WEB APPLICATIONS 7.00
BI WEBDYNPRO ALV 7.01 0006 SP006 BI WEBDYNPRO ALV 7.01
BP ERP FIN MDM 1.40 0006 SP006 BP for Financial MDM 1.40
BP ERP HR EIC 1.40 0006 SP006 BP für HR Employee Interaction Center 1.40
BP ERP ICM ANALYST 1.41 0004 SP004 BP for ICM-Analyst 1.41
BP ERP RECRUITER 1.40 0006 SP006 BP for Recruiter 1.40
BP ERP RECRUITING ADMIN 1.40 0006 SP006 BP for E-Recruiting Administrator 1.40
BP ERP SITE TECHNICIAN 1.20 0006 SP006 BP for Site Technician (Telecommunications) 1.20
BP ERP UT XSS 1.40 0006 SP006 BP ERP UT Definition für Self Service BP 1.40
BP ERP05 BUS UNIT ANALYST 20 1.0 0017 SP017 BP for Business Unit Analyst (mySAP ERP) 1.0
BP ERP05 COMMON PARTS 1.41 0006 SP006 BP ERP05 COMMON PARTS 1.41
BP ERP05 ESS 1.41 0006 SP006 BP for Employee Self-Service 1.41
BP ERP05 HR ADMINISTRATOR 1.41 0006 SP006 BP for HR Administrator (mySAP ERP) 1.41
BP ERP05 MAINTENANCE TECH 1.2 0006 SP006 BP for Maintenance Technician 1.2
BP ERP05 MSS 1.41 0006 SP006 BP for Manager Self-Service 1.41
BP ERP05 PROJ SELF-SERV 1.0 0016 SP016 BP for Project Self-Service (mySAP ERP) 1.0
BP ERP05 SELF-SERV ADMIN 1.0 0017 SP017 BP for Self-Service Administrator (my SAP ERP) 1.0
BP ERP05 TALENT DEV 1.01 0010 SP010 BP for Talent Development Specialist 1.01
BP_PROJ_PORT_DESIGNCOLL 4.0 0015 SP015 BP for Project Portfolio Management and Design Collaboration 4.0
CAF EU 7.01 0006 SP006 SAP Net Weaver End User 7.01
DI BUILD TOOL 7.01 0000 SAP BUILD TOOL 7.01
DI CHANGE MANAGEMENT SERVER 7.01 0006 SP006 CHANGE MANAGEMENT SERVER and SXMAN 7.00 701
DI COMPONENT BUILD SERVER 7.01 0006 SP006 COMPONENT BUILD SERVER 7.01
DI DESIGN TIME REPOSITORY 7.01 0006 SP006 DESIGN TIME REPOSITORY 7.01
FORUMS 7.01 0005 SP005 FORUMS 7.01
J2EE ENGINE BASE TABLES 7.01 0006 SP006 BASETABLES
J2EE ENGINE CORE TOOLS 7.01 0006 SP006 CORE TOOLS J2EE ENGINE
JAVA LOG VIEWER 7.01 0006 SP006 SAP JAVA LOG VIEWER 7.01
JAVA SP MANAGER 7.01 0006 SP006 JAVA SP MANAGER 7.00
KMC BASE COMPONENTS 7.01 0006 SP006 KMC BASE COMPONENTS 7.01
KMC COLLABORATION 7.01 0006 SP006 KMC COLLABORATION 7.01
KMC CONTENT MANAGEMENT 7.01 0006 SP006 KMC CONTENT MANAGEMENT 7.01
KMC UI LAYER 7.01 0006 SP006 KMC UI LAYER 7.01
KMC WEB PAGE COMPOSER 7.01 0006 SP006 KMC WEB PAGE COMPOSER 7.01
LIFECYCLE MGMT PORTAL 7.01 0006 SP006 LIFECYCLE MGMT PORTAL 7.01
LIFECYCLE MGMT TOOLS 7.01 0006 SP006 LIFECYCLE MGMT TOOLS 7.01
MI ADMINISTRATION 7.01 0006 SP006 MI ADMINISTRATION 7.01
MI DRIVERS 7.01 0006 SP006 MI DRIVERS 7.00
MI WD LAPTOP 7.01 0006 SP006 Net Weaver Mobile Infrastructure Web Dynpro LAPTOP 7.00
PDK PORTAL SERVICES 7.01 0006 SP006 PDK PORTAL SERVICES 7.00
PORTAL CORE SERVICES 7.01 0006 SP006 EPBC 7.01
PORTAL FRAMEWORK 7.01 0006 SP006 EPBC2 7.01
PORTAL PLATFORM 7.01 0006 SP006 EP - Portal Server PORTAL 7.01
PORTAL WEB DYNPRO 7.01 0006 SP006 PORTAL WEB DYNPRO 7.01
RTC 7.01 0006 SP006 RTC 7.00
RTC-STREAM 7.01 0006 SP006 RTC-STREAM 7.00
SAP CAF 7.01 0006 SP006 SAP CAF 7.01
SAP CAF-KM 7.01 0006 SP006 SAP CAF-KM 7.01
SAP CAF-UM 7.01 0006 SP006 SAP CAF-UM 7.01
SAP CPS BASIC (SCHEDULER) 7.01 0004 SP004 Job scheduling capabilities of SAP NetWeaver 7.01
SAP ESS 603 0006 SP006 SAP ESS 603
SAP INTERNET KNOWLEDGE SERVLET 7.01 0006 SP006 SAP Internet Knowledge Servlet 7.00 (SAP J2EE IKS)
SAP J2EE ENGINE 7.01 0006 SP006 SAP J2EE Engine 7.01
SAP J2EE ENGINE CORE 7.01 0006 SP006 SAP J2EE ENGINE CORE 7.01
SAP JAVA TECHNOLOGY S OFFLINE 7.01 0006 SP006 SAP JAVA TECHNOLOGY S OFFLINE SAP TECH S OFFLINE 7.01
SAP JAVA TECHNOLOGY SERVICES 7.01 0006 SP006 SAP JAVA TECHNOLOGY SERVICES (Schicht 3 Dummy) SAP JAVA TECH SERVICES
SAP MI CLIENT 7.01 0006 SP006 SAP Mobile Infrastructure Client 7.0
SAP MSS 600 0017 SP017 SAP MSS 600 (Manager Self Services)
SAP PCUI_GP 603 0006 SP006 SAP PCUI_GP 603
SAP SOFTW. DELIV. MANAGER 7.01 0000 SAP JAVA SL 7.01
SOFTWARE LIFECYCLE MANAGEMENT 7.01 0006 SP006 SOFTWARE LIFECYCLE MANAGER 7.01
UME ADMINISTRATION 7.01 0006 SP006 UME ADMINISTRATION 7.01
UWL COLL PROCESS ENGINE 7.01 0006 SP006 UWL COLL PROCESS ENGINE 7.01
VISUAL COMPOSER BASE 7.01 0006 SP006 VISUAL COMPOSER BASE 7.00
VISUAL COMPOSER BI KITS 7.01 0006 SP006 VISUAL COMPOSER BI KITS 7.00
VISUAL COMPOSER FLEX 7.01 0006 SP006 VISUAL COMPOSER FLEX 7.00
VISUAL COMPOSER FRAMEWORK 7.01 0006 SP006 VISUAL COMPOSER FRAMEWORK 7.00
VISUAL COMPOSER GP KITS 7.01 0006 SP006 VISUAL COMPOSER GP KITS 7.00
VISUAL COMPOSER XX KITS 7.01 0006 SP006 VISUAL COMPOSER XX KITS 7.00
WEB DYNPRO EXTENSIONS 7.01 0006 SP006 WEB DYNPRO EXTENSIONS 7.01
I expect to see more than the 6 previously mentioned files available for download, also the option for EHP2 which I know is available, or am I wrong in expecting this.

Copied Business Role in Solution Manager ITSM

Hi All
This is eunhwa.
I have a question regarindg copied business role in Solution Manager ITSM.
To copy business role, I copied technical roles Navigation profile, configuration key and PFCT Role ID. And then I copied
a business Role. And assign copied technical roles to copied business role.
And I changed Direct link group UI. For example, in copied business role ZSOLMANPRO, There were many
direct links, I only left ‘incident’ and ‘problem.
However when I selected incident’ in direct link, there was no transaction ‘zmin’ assign. I couldn’t create a incident.
Why this error happened? Is there anything which I miss?
Thanks.
Best Regards,
Eunhwa Park

Hi,
Well, there are multiple things you can check.
1. If you are using IE
You have to add the page/pop-up to the compatibility mode of your Browser.
IE -> EXTRAS -> Settings for Compatibility Mode -> Add -> Refresh the CRM WEB UI
2. Check if you had assign SM-CREATE in the ZSOLMANPRO Navigation profile. (In Assigning the direct link groups to Nav. Bar profile.
3. Check whether you had authorizations for ZMIN in PFCG profile.
4. Additionally check
1905448 - How to restrict the suggested transaction codes when creating an ITSM
Incident using CRM Web UI - Solution Manager
5. In define transaction types corresponding transaction types are active. (In SPRO under solman ->Capabilities->ITSM-> Transactions)
6. Check the copy control whether they are fine. (In SPRO under solman ->Capabilities->ITSM-> Transactions)
7. Ensure that the transaction type's channel definition in customizing is set to 'CRM Web-Client UI'
If your issue is still not resolved yet, please paste the error/screen you are getting.
Regards
Rishav

Questions in Solution manager

Hello friends,
Can any one answer these questions
SAP Solution Manager Overview Key points
-       Scope of Solution Managers capabilities
-       Work required to implement and configure Solution Manager i.e. how much is out of box vs. customer/implementation specific?
-       How it can be customized
-       Reports / metrics that solution manager offers
Thanks

Hello,
what is Solution Manager? A platform that provides integrated content, tools and methodologies for implementing, supporting, monitoring, upgrading and operating your enterprise SAP solutions.
My recommendation would be, if you have a chance to attend any of the SAP Solution Manager Seminars www.sapsolutionmanagerseminar.com/ would be the best to do. I am just back from the Amsterdam session. I have mainly worked in SAP Solution Manager projects, but still learned a few things even in areas I have been involved in.
Can you use SAP Solution Manager out of the box without any customizing? No. You need to execute basic customizing and maintain your landsape at the minimum.
For example you have to maintain your landscape. Generate RFC connections, setup up monitoring if required. Configure EWA reports if needed. Service Desk and Change Request Management would be large configurations. There are some reports you can use.
How can it be customized? Check out in transaction SPRO to get some idea, but not everything is in there covered you still need to configure.
There is a SAP Solution Manager book published since this year.
Regards,
Markus

Daily Monitoring of PRD of BI, XI, ECC, through Solution manager

Dear all ,
I have only configured Earlywatch alert for BI , ECC 6.0 on Solman(every week monday i got EWA report and I have taken action as per the EWA report).
Now my question are ,
Daily Monitoring of PRD of BI, XI, and ECC is possible ?
Weekly Monitoring of DEV & QAS of BI, XI, ECC, ?
EWA for XI is possible ?
Finally how can i completely use Solman server for monitoring ,etc....
Kindly advise
Regards

Hello,
Daily Monitoring of PRD of BI, XI, and ECC is possible ?
Of course possible, what kind of monitoring are you looking for?
Using the System administration functionality you can perform the pro-active monitoring, which will also trigger auto reaction methods whenever the thresholds are reached, as per the setup performed.
There are SAP standard parameter monitoring available, in addition you can define your own parameters to be monitored in the System administration workcenter functionality.
Weekly Monitoring of DEV & QAS of BI, XI, ECC, ?
You can use the central system monitoring functionality which enables you to perform monitoring tasks as per the period/frequency specified.
You can also input your/teams monitoring notes/observations and generate it as a separate report.
EWA for XI is possible ?
It is possible; for ABAP stack, perform the same steps as you performed for other ABAP (ECC) systems, for Java stack of XI, configure the Solution Manager Diagnostics which will trigger the EWA for Java part. Finally you receive a consolidated (ABAP+Java) EWA next Monday.
Finally how can i completely use Solman server for monitoring ,etc....
EWA, SLR provide you with a reporting functionality which again is a result of monitoring your system over the previous week.
Using System administration and Central system monitoring you can leverage the monitoring capabilities.
Using SMD, Wily you can extend the monitoring of Java and dual stack systems
Using BPMon you can attain the Business process monitoring.
In addition, in the work center you can see additional monitoring options, like. RFC monitoring.
Hope this helps.

Extend Wily Introscope in Solution Manager

Hello, Could I monitor other non SAP solutions in Solution Manager?
I need to integrate all systems that are intended for monitoring (SAP
and non SAP systems) to Solution Manager
What is the scope of Wily Introscope in Solution Manager? Is the scope
only with SAP products or I could extend Introscope's capabilities to
other products?
Thanks for your help
Best regards
Edgar Rafael Escobar Molina

What is the scope of Wily Introscope in Solution Manager? Is the scope
only with SAP products or I could extend Introscope's capabilities to
other products?
The Introscope coming with SolMan is only a part of the full Introscope suite. It contains only those applications necessary to monitor SAP systems. For other non-SAP systems you would need different agents which are not delivered and must be purchased separately. I´m also not sure if the Solman license permits the usage of those agents in non-SAP environments.
Markus

SLAs in Solution Manager 7.1

Hello all,
i've noticed some interessting changes in the SLA implentation in the new SolMan 7.1, like a constantly new calculation of end time, response time etc.
My first trys to get the sla determination for incidents running were not succesful.
Is there any one with some expierence with sla in solman 7.1? Are contracts still required? Is there a configuration guide which shows how to to config the slas?
Any help would be much appreciated.
Best Regards
Daniel

Hi Daniel,
the configuration of SLA's is described the Implementation Guide of SolMan 7.1 under:
SAP Solution Manager --> Capabilities --> Application Incident Management --> SLA Escalation
In addition we have some new guides in the Installation Guides Section for SolMan 7.1
https://service.sap.com/instguides
--> Solution Manager --> SolMan 7.1 --> Additional Guides
Here the direct link to the overall configuration guide for IT Service Management:
https://service.sap.com/~sapidb/011000358700000514762011E/ITSM_Guide_AIMConfig_final.pdf
Hope that helps...
Best Regards,
Michael

Solution Manager Integration with Tivoli and TSRM

Hi,
Has anyone done an integration of SAP Solution manager with Tivoli or TSRM. Solution Manager can perform the same capabilities of Tivoli or TSRM of monitoring and Service desk. However we want to use the best of both. I would appreciate if if someone can share thier thoughts on this.
Regards
Jasvinder

Hi,
Heres a good news for you.
IBM Tivoli Service Request Manager version 7.1 software has now SAP-certified for integration with SAP Solution Manager 7.0 via the service desk interface scenario (SMG-SDI 4.0).
[The News|http://www.cbronline.com/news/ibm_launches_new_service_to_help_automate_it_service_desk_operations_091013]
To Inegrate refer [this guide.|http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e3eeb4a8-0b01-0010-bd99-f4a700a49d32]
Hope this will solve your problem.
Feel free to revert back.
-=-Ragu

Solution Manager to Solution Manager connection

Hello everyone,
I am searching for an answer for such a question: is it possible to connect one SolMan (the one from the service provider) to another SolMan (customer's one) in a way that tickets would go from customer's ERP to their SolMan (as it is now) and afterwards would be automatically forwarded to the other SolMan where the tickets should be processed?
If you have any idea, experience or relevant document, please share it - I will be really grateful.
Best regards,
Katarzyna Klys

Hi Katarzyna,
Please check the External service desk functionality for this. You can check SPRO entry for this:
SPRO --> SAP Reference IMG --> SAP Solution Manager Implementation Guide
     --> SAP Solution Manager --> Scenario-Specific Settings --> Solution Manager - External Integration --> External Service Desk
Also check below link:
http://help.sap.com/saphelp_sm40/helpdata/en/8a/b0278648ac4f058a7111c3f9b60feb/frameset.htm
(All in One line)
In Solman 7.0 system:
1. T-code SM59   > Define an RFC connection to 7.1 system;
2. T-code ICTCONF   > Add an entry for the 7.1 service desk, specify the RFC Destination as the one you defined   > Activate -> Generate default value mapping (you may find the button on the top of ICTCONF).
In Solman 7.1 system:
1. T-code SM59   > Define an RFC connection to 7.0 system;
2. T-code ICTCONF   > Add an entry for the 7.0 service desk, specify the RFC Destination as the one you defined   > Activate -> Generate default value mapping;
3. Customize your own value mapping including the transaction type. You will find the details in:
    IMG -> SAP Solution Manager -> Capabilities (Optional)
    -> Application Incident Management (Service Desk)
    -> External Integration -> External Service Desk
Most fields of SIVA and SMIV are the same (for example, priority) so you do not need to care about the value mapping if you do not havespecial requirement. However, some fields only exist in SIVA (category, subject) and others only exist in SMIV (multilevel categories). You may need to implement your own code according to your requirement.
Notes might help:
1159722
1136816
Thanks
Vikram

Moving Solution Manager content across platforms

I have a pretty good understanding of Solution Manager's capabilities but need to make a decision about the platform to install it on for our project.
We want to get something up and running quickly so we can learn from it, but this probably wont be the final platform that we use for our implementation and production running.
How difficult is it to take Solution Manager content from an installed server and move it to another one? Can this be done? Will it result in much "downtime" for our project?
What if the final platform is totally different from the initial one - say from SQL Server/Windows to Oracle/AIX - will we still be able to move developed content from old to new?

> What if the final platform is totally different from the initial one - say from SQL Server/Windows to Oracle/AIX - will we still be able to move developed content from old to new?
You can do system copies - but the "content" (means solutions, EWAs) are not that easy to transfer since they depend on the CRM structure (Businesspartners, roles of them etc.)
We are in the same situation of having an upgraded SolMan (initally started with 2.1 over 3.1/3.2 to 4.0 with Unicode conversion) with > 7.000 support desk messages which we don't want to loose. Our research to move those messages to a freshly installed SolMan turned out to be too complicated and needing too much time - thus we decided to freeze the current SolMan at some point soon and install a new one and start the implementation from scratch.
It may be possible to export/import certain configurations/settings but as far as I know there is no standard procedure for this.
Markus

Customer attributes in SAP Solution Manager

Hi,
I have created Customer Attributes in SAP Solution Manager, SPRO--> SAP Solution Manager-->Capabilities-->Implementation/Upgrade-->Blueprint and Configuration-->Object Attributes--> Definition of Customer Attributes for Object Types. I have assigned the Customer Attributes for Project/Solution.
Now I have the attribute in the project nodes but I can't enter Attribute Values. How can I solve this problem?
Regards.

Hi,
you need assign value in solar02, when you assign attributes to the object. check out
Adding customer attributes to objects in Project and Solution
Thanks
Jansi

Question about how to connect two solution manager

Hello experts
one of our clients wants to connect his SOLMAN to our SOLMAN, that way
when they receive a case in his ICM we can monitor the case and respond
It, if the situation requires or they ask for our help.
Can you please tell me if theres a way to connect them and what is the
best way to do that?
Thanks for your help,
Regards,

You are going to connect a Solution Manager to another Solution Manager, so I think it is enough to use the RFC destination on the connection.
I suppose you want to send a message from 7.0 to 7.1, so you may:
In Solman 7.0 system:
1. T-code SM59   > Define an RFC connection to 7.1 system;
2. T-code ICTCONF   > Add an entry for the 7.1 service desk, specify
the RFC Destination as the one you defined   > Activate -> Generate default value mapping (you may find the button on the top of ICTCONF).
In Solman 7.1 system:
1. T-code SM59   > Define an RFC connection to 7.0 system;
2. T-code ICTCONF   > Add an entry for the 7.0 service desk, specify the RFC Destination as the one you defined   > Activate -> Generate default value mapping;
3. Customize your own value mapping including the transaction type. You will find the details in:
    IMG -> SAP Solution Manager -> Capabilities (Optional)    -> Application Incident Management (Service Desk)    -> External Integration -> External Service Desk
Most fields of SIVA and SMIV are the same (for example, priority) so you do not need to care about the value mapping if you do not have special requirement. However, some fields only exist in SIVA category, subject) and others only exist in SMIV (multilevel categories). You may need to implement your own code according to your requirement.
Thanks
Vikram

Readiness of Solution Manager

Dear All,
Just need a clrafication, Our solution has the following setup and configuration which is ready for use
1-Chain Request Managment
2-Mainatence optimizer
3-System Mointering ( centerlized Monitering)
4-Service Desk
Just want is this solution manager is ready for use of functional consutant i.e creation of project, prepartion of business blue print document, Support or any setup or area need to configure for solution manger for use of functional consultant ?
Might be my question is not clear, simple I mean which area need to setup/configure in the solution manager for use of functional consultant or project implementation ?
Would be thankful if you guide me.

Hi,
The ones you have configured definitely acts as a base for the rest. However additional configurations would also be required. Hence they would not be ready now, but can be configured for use.
http://service.sap.com/rkt-solman helps in configuring solution manager capabilities as per mapped to the various stages of the Application Lifecycle Management.
Regards,
Srikishan

Solution Manager SMD Question

Hello,
I have few questions below. Please help.
1) Do we need to configure the SMD for solution manager alert configuration. Or we can configure the solution manager alert configuration for ABAP stack without SMD.
2)Stpes to configure Solution Manager diagnostics.
3) How to do solution manager alert configuartion.
Regards,
Deepak

Hi Deepak,
One thing is monitoring using CCMS on ABAP to monitor JAVA and ABAP systems. For that you will be able to find the complete information on the following PDF:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f08287c4-a4ee-2a10-b0a2-c863755fdb94
In this case you only need an ABAP 7.0 system where you can use auto reaction methods and/or the Alert Framework provided by ABAP for sending alerts to email or pagers and you do not need Solution Manager or Solution Manager Diagnostics.
On the other hand you have the End-to-End Root Cause Analysis that use Solution Manager Diagnostics as tool for workload analysis, exception analysis, trace analysis and change analysis, for this you will need Solution Manager (ABAP and JAVA) and WilyInstroscope. You will find the main installation guide in the following link:
https://service.sap.com/~sapdownload/011000358700000271732008E
The installation guide for Wily Introscope for SAP is on:
https://service.sap.com/~sapdownload/011000358700000271852008E
Currently SMD does NOT provides any alerting capabilities it is only for reporting and problem analysis.
Zareh

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.

Capabilities of Solution Manager

Similar Messages

Maybe you are looking for