Solution Manager - Basics

Hi Experts,
Can any one give me an overview of what can be done with Solution Manager.
Basically it is about the basics of solution manager.
any links or documents in this direction would really help me.
-Naveen.

Hello Naveen,
You can find all the world about solution manager at this location in the serviuce market place.
https://websmp210.sap-ag.de/solutionmanager
right from value propositions to installtion guides and FAQ and downloads.
Let me know if these links are not hekpful, i would try to clear ur queries possibly..
Br,
Sri
Thanks for the points if any.

Similar Messages

Solution Manager Basic Setting, Get SAP Component fail

Dear All
When I execute Solution Manager initial configuration wizard on step:
Initial configuration part II, it comes out an error: Fetch SAP
Component fail.
Can anyone tell me what's the problem, thanks.
Steps for Reconstruction
1) SPRO => Basic Settings => Initial Configuration Part II
2) Err: SAP Service Marketplace error
3) manually: Get SAP Components => Edit => Fetch SAP Components => No
RFC Authorization
[http://www.mountain.org.tw/sap/090322/B/000.png]
[http://www.mountain.org.tw/sap/090322/B/010.png]
[http://www.mountain.org.tw/sap/090322/B/020.png]

hello,
Check which user you are using. Use standard user with SAP_ALL authorisation in 000 client.
This is RFC authorisation issue.
Regards
Anju

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.

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.

Solution Manager 4.0 Configuration: SLDAPIUSER role

In SPRO, SAP Reference IMG -> SAP Solution Manager -> Basic Settings -> SAP Solution Manager System -> System Landscape -> Automatic System Landscape Data Capture -> Connection of System Landscape Directory to Solution Manager -> Generate authorization roles for SLD users
When I display user SLDAPIUSER in client 001, there are no roles defined. I cannot continue with Authorizations without this role. Does anyone know what the default role for this user should be?
Regards,
Vince Ingram

Hi Vincent,
After my 1st reply I was goind through "Component Installation Guide: SAP NetWeaver 2004s Java on Windows: MS SQL Server", this what I found want in that document:
In transaction SU01 create the following dialog users (you do not need to assign them to a role):
Caution
You must have changed the initial passwords of these users [page 77] before you start the installation of the Java system.
ADSUSER:
User for Adobe document services
SLD Data supplier user (optional):
You only have to create this user if you want to install SAP System Landscape Directory (SLD). The SLD data supplier user name that you enter later on during the Java system installation must be identical to this user.
Recommendation
We recommend that you name this user SLDDSUSER
SLD ABAP API user (optional):
You only have to create this user if you want to install SAP System Landscape Directory (SLD). The SLD ABAP API user name that you enter later on during the Java system installation must be identical to this user.
Recommendation
We recommend that you name this user SLDAPIUSER
I dont know I am still confused about these users because they have been used in services.
Thank You,
Indasena Janga

Solution Manager Addon Stuck BBPCRM SAPKU50008

Dear Experts,
When I am implementing ADDON BBPCRM SAPKU50008 in Solution Manager .In Queue Import It stuck in "Execution of report after put"
When I check SLOG .It show nothing.
START tp_getprots          SAL R      20101211160827              DDIC         testserver
STOP tp_getprots          SAL R      20101211160943              DDIC         testserver
STOP EXECUTION OF REPORTS SAL R      20101211160943              DDIC         testserver
START EXECUTION OF REPORTS SAL R      20101211161147              DDIC         testserver
START tp_getprots          SAL R      20101211161148              DDIC         testserver
But when I check \usr\sap\trans\log\SAPKU50008
2 EPU122XPost-import method "BEFB_AFTER_IMP" started for "BEFT" "T", date and time: "20101210153150"
A3 E/BEF/GENERATOR 008XGeneration of BE Application "CRMB" (Start Time "15:31:51")
A3WE/BEF/GENERATOR 010 Generation of application "CRMB" (user "DDIC") is already running
1AETR012XProgram terminated (job: "RDDEXECL", no.: "15313100")
1AEPU320 See job log"RDDEXECL""15313100""SAL"
1 ETP162 EXECUTION OF REPORTS AFTER PUT
1 ETP110 end date and time   : "20101211094736"
1 ETP111 exit code           : "12"
1 ETP199 ######################################
Transport is proper configure.
Whats the problem ?

Hello Pooja,
One thing you want to check is based on your SP level that the following notes have been applied on your system:
1172948 SAP Solution Manager: Basic functions (18 & 19)
1334252 SAP Solution Manager: Basic functions: SP20 and SP21
1405878 SAP Solution Manager: Basic functions: SP22 to SP24
1468591 SAP Solution Manager: Basic functions: SP25 and higher
If the relevent note is not already applied to your system, then please do so.
As Tom has already suggested you want to check the Job log for RDDEXECL.
You can do this with transaction code SM37.
Check for lines like:
ABAP/4 processor:...
Which indicates there was a short dump created and the program terminated.
You can look at the dump via ST22. This can be used for a Note search that may address the cause for the dump.
Hope this helps!
Regards,
Paul

EHP1 upgrade of solution manager-any effects in landscape due to common SLD

Hello All,
We have ECC,BI,SRM,XI,EP,MAM and BD in our setup and yes of course Solution Manager dev and prod
We have our SLD installed on solution manager production which is common for all the systems of the landscape
Now we have performed EHP1 upgrade if Solution manager dev and now we are planning on solution manager production
So just want to know,do you forsee any issues after we upgrade the solution manager production to EHP1 in respect to SLD or can there be any issues in the landscape because of this upgrade?
Please let me know your suggestions
Rohit

> So just want to know,do you forsee any issues after we upgrade the solution manager production to EHP1 in respect to SLD or can there be any issues in the landscape because of this upgrade?
The SLD is not affected.
However, SolMan EHP1 requires a LOT of separate notes to be applied.
Note 1172948 - SAP Solution Manager - Basic functions
Depending on what scenarios you use, you will also need to upgrade ST-PI in the external systems before EWAs will be again correctly created.
Markus

Where can i find the configuration guide for a solution manager beginner

dear all:
as the title,expect your reply.
thanks!

Hi Zuiyong,
the configuration guide of SAP Solution Manager contains only same general information like strategy, required SPs in sat. systems, authorization and notes.
The 'REAL' configuration guide can will find in the system in the transaction SPRO->Referenz.IMG ->Solution Manager->Solution Manager-> Basic Settings. These settings you have to make to use standard SAP Solution Manager. In the are enhanced settings you can find additional settings for additional features.
Regards,
Udo Lang

Solution Manager Document

Dear Gurus,
Can anybudy send me SAP Solution Manager basic Documents / Material .
Mail id : [email protected]
Thanks & Regards,
Ishwar

Check
http://service.sap.com/rtk-solman
http://service.sap.com/solutionmanager
--> Documentation
Markus

Early Watch Alerts Problem in Solution Manager

Hello,
I am trying to configure EWA for my SAP R/3 systems in Solution Manager 3.2. RFC connections are working fine. EWA report that is getting generated is showing me following problem :
EarlyWatch Alert - R/3 System**********
Download Problem
We could not perform a correct analysis because essential parts of the download data are missing. The cause is probably a problem with data collection or transfer.
Recommendation: Please check the log for this session in the Service Data Control Center (execute transaction SDCC or the new SDCCN in your system). If an error entry is listed, perform the Service Preparation Check.
Implementation: To perform the Service Preparation Check, execute transaction SDCC and choose Information-> Service prep. check or if you use SDCCN create a new task 'Service Preparation Check'.
The result of Service Preparation check ( as recommended) is not throwing any error.
Can anyone help me out on this.
Regards,
Yashodhan

Hello Yashodhan Mujumdar,
we have warnings about differences in the function interface, but all works, so we ignore them.
But the missing data interface seems to be the error.
Did you read note 781680?
Do you have the newest ST-PI (2005_1_xxx SP3) and ST/A-PI (01G_xxx, this is an installation, no patch)? Do you have the right flavour of ST/A-PI?
Are ST03N and ST06 working?
Do you refresh service definitions from sapnet? Did you generate (after service refresh) on the solution manager system the includes (SPRO -> SAP Solution Manager -> Basic settings -> SAP Solution Manager System -> Operations -> Setup Service Data Control Center -> Generate Includes....
If these checks are all ok you might deactivate SDCCN both in satellite system and solution manager (SMSY -> Goto -> Solution Manager Operations -> Administration SDCCN) and activate it again.
If this doesn't work you might use the big hammer:
1) delete all the service definitions in satellite system like described in note 727998
2) delete all entries in table /BDL/_GENER (satellite system)
3) create in SolMan system a new session in order to collect and send data for this session in satellite system; if you don't see the session in the satellite system please execute there the "Maintenance Package"
4) elaborate the data for this new session in SolMan system
If all this doesn't help, open a message in sapnet
Bye
Message was edited by: Riccardo Escher

Configuration Solution Manager - Travel Management for Route Cause Analisys

Hi,
Can you describe how to configure Solution Manager to monitor (RCA-E2E) our Travel System (SAP Enterprise Portal + SAP HR)?
Best regards,
Diego.

Hi,
RCA configuration remain same for all the module/component
All the steps are there in RCA Configuration thread
SPRO>SAP SOlutionManager Implementation Guide> SAP Solution Manager>Basic settings> Root Cause analysis
here you can find all the information regarding setup, please follow one after the other.
Regards,
Shyam.

Basic Strategy / Best Practices for System Monitoring with Solution Manager

I am very new to SAP and the Basis group at my company. I will be working on a project to identify the best practices of System and Service level monitoring using Solution Manager. I have read a good amount about SAP Solution Manager and the concept of monitoring but need to begin mapping out a monitoring strategy.
We currently utilize the RZ20 transaction and basic CCMS monitors such as watching for update errors, availability, short dumps, etc.. What else should be monitored in order to proactively find possible issues. Are there any best practices you all have found when implimenting Monitoring for new solutions added to the SAP landscape.... what are common things we would want to monitor over say ERP, CRM, SRM, etc?
Thanks in advance for any comments or suggestions!

Hi Mike,
Did you try the following link ?
If not, it may be useful to some extent:
http://service.sap.com/bestpractices
---> Cross-Industry Packages ---> Best Practices for Solution Management
You have quite a few documents there - those on BPM may also cover Solution Monitoring aspects.
Best regards,
Srini
Edited by: Srinivasan Radhakrishnan on Jul 7, 2008 7:02 PM

Sap Solution Manager 7.1 SP11 Basic Configuration

Hi Experts,
I am in fresh installation for Sap Solution Manager 7.1 SP11. At Basis Configuartion Phase in step " Configure CA Introscope".
I have successfully installed, but it shows the following message: " Offline - The EM Connection cannot be established (caused by :com.sap.smd.introscope.em.IntroscopeException: java.lang.reflect.InvocationTargetException_) "
Need suggestions how to proceed from here.
thanks

Raja,
I assume you're using Linux/UNIX.
Here's the solution. It worked for me.
In /usr/sap/ccms/apmintroscope/config/users.xml, update the Guest password with this MD5 hash: c4582df82299e0581a9fc6bb34c53
In user management screen of "Configure CA Introscope", choose "Guest" as connection user with password "guest12" (without quotation marks)
If it's still not working, then delete the EM and re-install the introscope.
Go to expert mode -> Delete references -> Remove the line
Delete folder /usr/sap/ccms/apmintroscope
Install introscope and management modules againdon't forget to re-set the permission for diagnostic agent user
Go back to solman_setup "Configure CA Introscope" and do import CA again
Save, you'll have a green status
Regards,

Basics and any documentation on solutions manager

Hi,
I would really appriciate it if i can get any documentation/ information/links on the Solutions manager and the different functionalities in the module.
Thanks in advance,
Kanishka

Solution Manager is designed to assist entire life cycle of your solutions....
During implementation / upgradation ->it will help you manage your project by giving road maps, tools to blue print, tools to configure your systems according to your blue prints, testing workbench to test configured systems, Learning Maps to educate team by creating lessons.
During support ->
Support desk -> A tool to manage problems faced in your systems.Once configured users can raise support messages from any of the system and they can be managed in solution manager.. and from there they can be sent to SAP for their support...
Change request management -> A tool to handle change managment
BPM- Business process monitoring..
You can get reports of your systems.. like EWA,SLA
Please check http://help.sap.com/saphelp_sm40/helpdata/en/45/51fbdbd4941803e10000000a1553f7/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ce89c290-0201-0010-5985-dd64605111fd
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ce0b74e3-0601-0010-29a0-f2a6af98ef06
If you require any specific information about solution manager do come back..
regards
Mrutyunjay
Reward points if found helpful

Problem with BI activation in Solution Manager

Hello SAP experts.
I have problem with BI Content Activation in Solution Manager solman_workcenter - test management - settings - Bi reporting
The customizing in client 010 is ok. I have BW client 001. RFC connections
are ok. After activation of BW content in workcenter only new job in sm37
has been planned but the button Status Report has not appeared. I installed
newest add-on SAPK-70405INBICONT.
Detailed description:
After customizing in:
SPRO-Basic Data-BW Setup
and
SPRO-Scenario-Specific Settings - Test Management - BW-based Reporting.
The Activation of BW content in transaction solman_workcenter - Test
Management - Settings - BI Reporting Settings the message appears:
"Test Workbench Reporting - BI Content not active", after pressing save:"Settings of Test Workbench Reporting saved"
and
"Activation of BI Content for Test Workbench Reporting started".
In test evaluation the button Status report doesnt show. After repeated
activation appears the same message as in beginning: Test Workbench
Reporting - BI Content not active.
Thank you

Hi Marian,
Could you please provide me with details on how to setup test workbench reporting. I have a BW system external to Solution Manager. I have setup the RFC conncections and all is okay. I have also setup the source system in BW and installed the web templates. However, when activating the content via solman_workcenter - test management - settings, I get the following error:
Content Activation Log
Log for Setup ID 20100819135323
20100819 135323[ERROR ]: Current Status: ERROR
20100819 135323[INFO ]: Job CCMS_BI_SETUP successfully scheduled
20100819 135323[ERROR ]: Incorrect system setting: standard transport is active
20100819 135323[ERROR ]: Change system settings or set user parameters RSOISCONTENTSYSTEM and RSOSTANDARDCTOACTIVE
20100819 135323[ERROR ]: Prerequisites check failed
20100819 135323[ERROR ]: Jobname/count: CCMS_BI_SETUP 13532300
I am sure there is something wrong in my setup but I cannot figure out what it is. A step by step help on how to do it will be greatly appreciated.
Regards,
Rue.

Solution Manager - Basics

Similar Messages

Maybe you are looking for