Solution Manager implementation sequence
Hi Experts,
Need some quick advice, please
I am done with my Solution Manager 7.0 ehp1 Installation, Post Installation activity. Further so far I have configured the SAP ROUTER.
Now, could you please let me know in what sequence are the following to be taken up
1. Connecting Satellite systems with Solution Manager System.
2. Initial/Basic & Managed System Configuration
3. Maintenance Optimizer Configuration
4. Service Desk and EWA Configuration
Kindly let me know whats the sequence I should be following and also if I have missed something important please point it out.
Many Thanks in Advance..
Hi
Simply run Solman_setup tcode and just follow the steps
https://websmp106.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700000066952009E
it is wizard in which you first do initial or basic setup
followed by managed system and other config
so in short your sequence will be automatically guided by this transaction
later you can configure EWA and service desk
hope it ans ur query
regards
prakhar
Similar Messages
-
Solution manager implementation tool certification(SMI310)
hi all,
How's the question pattern for Solution manager implementation tool certification(SMI310)
- partial marking(old pettern) or SAP will mention the option of correct answers(new pattern)?
regards
jaichanHi,
From my basis certification exam experience, i learned that anyone shouldnt be thinking about examination assessment. But rather one should be concentrating on the objectives of each lesson. If you dont do handson part of each chapter exercise, then you are in danger!
You can test yourself, by checking whether you can explain each lesson objectives/goals in detailed or not.
One more trick to get prepared well yourself well is to bringout opposite version of the sample questions after each chapter.
This will help you building up confidence on the subject matter.
I wish you will definitely qualify the certification.
Cheers,
Srikar -
New to Solution Manager Implementation
Hi Experts:
We have implemented SAP ECC 6.0 in our company, our Organization decided to implement SolMan SP15. I will be a part of the team to implement SolMan. Just give a background of my experience, I am a MM Consultant.
I need some direction from the Experts, first from where to start. Any relevant links to the right documents will be very helpful.
Secondly for a SolMan consultant what should be the prerequisite from the previous experience point out view. It is required that the candidate to have SAP Basis knowledge.
Any helpful guidelines and links to the material will be highly appreciated.
Thanks
JamesHi Bill
For you it is better to go to Solution manager functional role...or Solution consultant
which is actually involved in implementation point of view.
For you it is not required to learn basis........for e.g u r gng to do a ECC implementation ....wht is req from u will be
Basis will set up landscape RFC logical component etc
And you will create a project in solmaan do the blueprint in Solar01 etc.......for satellite ECC system
and Even in the operation like Service Desk /CHARMS etc....can BASIS go and understand client processes ....and implement it in solman service desk.
I dont think so....basis install solman and activate bc sets and do some basic configuration.....
there after there are lot of CRM sort of configration like Sold to party and other BP creation with determination rule which is ofcourse can be done by you as u being functional role understand the ORG hierarchy of the client.SLA implementation etc.
I hope it clarifies ur doubt
Regards
Prakhar -
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 -
Solution Manager Implementation
Hi All,
I am new to Solution manager,my company decided to implement Solution manager.Can anybody tell from where to start in implementing this.Is there any alternative for infopack.What is the best practice for implementing and what need to be considered.
Thanks in AdvanceHi,
Please check below links are very useful:
sap solution manager configuration setup:
http://wiki.sdn.sap.com/wiki/display/SMSETUP/Home
Change Request Management scenario:
/people/dolores.correa/blog/2009/08/27/change-request-management-scenario-retrofit-functionality
Service desk configuration guide:
/people/federico.babelis2/blog/2006/04/14/service-desk-configuration-guide-for-dummies
How to Configure Solution Manager through maintanance optimizer:
How to Configure Solution Manager for 1.Download SuppPacks 2. Monitoring 3
System monitoring Configuration guide:
/people/federico.babelis2/blog/2006/04/25/system-monitoring-configuration-guide-for-dummies
CCMS Rule Based Monitors configuration guide:
/people/federico.babelis2/blog/2006/04/26/ccms-rule-based-monitors-configuration-guide-for-dummies
Service Data Control Center configuration guide
/people/federico.babelis2/blog/2006/04/23/sdcc--service-data-control-center-configuration-guide-for-dummies
Guides download link:
https://websmp102.sap-ag.de/sizing
https://websmp102.sap-ag.de/instguides
https://websmp102.sap-ag.de/solutionmanager
https://websmp102.sap-ag.de/EWA
https://websmp102.sap-ag.de/swdc
Regards,
kalees -
SAP Solution Manager Implementation on iSeries
Hi All,
Is it possible to install SAP Solution Manager on iSeries with an existing SAP R/3 installed? If so, is it advisable to install SAP SOLMAN in an iSeries machine with SAP R/3 Production system? Can you also send me documents related to SOLMAN installation on iSeries? Thanks!
John
Edited by: Francis John Tuazon on Feb 20, 2009 5:12 PMYou will have to load the Unicode kernel and here is the link to OSS where you can get get the download of SOLMAN for AS/400
https://websmp110.sap-ag.de/solutionmanager , then choose this one: ZIP 51033506_7 NW 7.0 SR3 UC-Kernel 7.00 OS/400 Info 550479 24.04.2008 .
The install manuals are out there as well. -
Solution Manager 4.0 Implementation Tools Experience Information
Hi,
We are looking at implementing the Blueprint, Configuration and Test Manager implementation tools for SM 4.0 to assist with our ERP2005 upgrade from 4.6C.
We have gone through pretty much everything that is available online for SM in SAP Service Marketplace and have taken SM training SMI310. We are at the next step of proceeding with the implementation.
I am looking for <b>anyone who has gone through an SM implementation</b> and can help with documented standards, templates and defined processes and user roles for Solution Manager implementation of the Blueprint, Configuration and Test Manager implementation tools.
Anything that can give us a better understanding and a head start to our SM implementation would be appreciated.Hi
To answer some of your questions:
Keywords: We have used keyword "In scope" on structure nodes (processes, process steps) to allow the consultants to add relevant processes and documentation which is not relevant for the current project but must likely will be later. The keyword can then be used as a filter when generating blueprint.
Furthermore we have used keywords related to prototypes - so it is easy to apply a filter to show eg. which scenarios/processes are included in prototype1, prototype2 and so on,
We have a long list of documentation types, based on the best practice templates. Too many to list here.
Solution manager keeps track of document versions (history), so we use the standard status codes: "in process", when worked on. "review", when submittet to approval and "released" when finished.
There is no technical difference between doing config from SM vs in dev system - as you basically access the img. But for people used to workíng in Dev system directly, it is a quite new way to work. And there are some configuration items not in the IMG - which then cannot be linked into SM.
IMG objects will appear in several processes, and one option is to link in the same img objects in several processes, and then place the documentation along with the objects in a way where the consultant use the "where used" function on img objects to check if it has already been used elsewhere, and then create a link to the documentation there, and work in the same document. But in several cases they would have to start a new document, if it is not logical to add to other documents containing info on how the img object is configured.
You can use the standard roles for application consultant and project manager - they should cover implementation needs.
Hope some of this information is useful
Regards
Lars -
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
PaulHi 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. -
Upgrade ASAP roadmap content in Solution Manager
Hello,
Does anyone of you know how to upgrade the ASAP roadmap content in solution manager?
Current we have solution manager 4.0, SP12. The version of the ASAP roadmap content is V3.6 (Dec. 2006). We currently found from the service marketplace the lastest ASAP implementation roadmap (V3.7)
https://websmp106.sap-ag.de/roadmaps.
Is it possible to somehow "upload" this new version into Solution Manager roadmap to replace the older version? Or how should we get the roadmap content upgraded?
Many thanks for your input!!
Regards,
LiIt is delivered in ST-ICO SAP Solution Manager Implementation Cont. Ver 3.6 is in SP11, I would imagine V3.7 is in SP 13.
You would have to up your service pack or use the standalone one until then.
Derek -
Solution Manager Enterprise Edition upgrade slow
Hi
I am performing SOMAN 7.0 upgrade to Enterprise edition by upgrading kernel 701 and SP stack 18. I have already upgraded the kernel and java stack and now in the process of upgrading ABAP. I am expereincing really slow performance of this upgrade. I have checked tp and R3trans version which is uptodate as I updated kernel. I cant see any problem with CPU utilization as well swapping. I checked the SLOGs and there are no alerting errors. I see its moving and its very slow. I am just wondering if any of you guys experienced this - is this normal since this is a upgrade?Thanks a lot, i realize the installation following the standard add-on installation procedure!
Now i have the ST-ETP
ST 400 0024 SAPKITL434 SAP Solution Manager Tool
ST-A/PI 01M_CRM570 0000 - Application Servicetools for CRM 500 - 7
ST-ETP 100 0000 - SAP Solution Manager Enterprise Edition
ST-ICO 150_700 0025 SAPK-1507PINSTPL SAP Solution Manager Implementation Cont
ST-LV 100 0001 SAPK-10001INSTLV SAP Landscape Verification Wizard
ST-SER 701_2010_1 0002 SAPKITLOS2 SAP Solution Manager Service Tools
Then don't forget to perform step 5. After the installation steps.
Step 5 says this:
5. After the installation
To activate SAP Solution Manager Enterprise Edition, the Enterprise Addon SM_APPLM has to be activated in the IMG of the Solution Manager System. This is done via IMG activity SAP Solution Manager->Configuration->Scenario-Specific Settings->Activate Solution Manager Enhancements.
a) In the case of ST-400 SP15-SP17
To use Extended Tracebility in Change Request Management activate BC-Set SOLMAN40_CHARM_CONTEXT_001 in transaction SCPR20
b) In the case of ST-400 SP18 or higher
The activation of BC-Set SOLMAN40_CHARM_CONTEXT_001 will be done automatically.
In my spro i don't have this options->
I see the route Activate Solution Manager Enhacements in SPRO -> Cross Scenario Settings
And in enterprise extension I only see ( SM_CRON, SM_QC_AD, SM_SSP,SM_SUPP_VAR)
I guess that this in SP24 is done automatically, but you said, that don´t forget the step 5 after installation.
update:I check for updates of SP and this add-on don´t have SP for now -
Solution Manager enterprise edition.
Hi, all, How can I check if my version of solution manager is stardart or enterprise edition.
I need that information because in one of the presentation slides of the enterprise service "SAP Modification Justification Check"-
The prerrequisites are.
"Sap Solution Manager Enterprise Edition Must be available". Scope and Architecture of bussiness processes must be documented according to the Minimum Documentation standard.
The solution manager enterprise edition have any special component in system -> status??? or how can i check if i have the enterprise edition of SOLMAN..
Thanks.Thanks a lot, i realize the installation following the standard add-on installation procedure!
Now i have the ST-ETP
ST 400 0024 SAPKITL434 SAP Solution Manager Tool
ST-A/PI 01M_CRM570 0000 - Application Servicetools for CRM 500 - 7
ST-ETP 100 0000 - SAP Solution Manager Enterprise Edition
ST-ICO 150_700 0025 SAPK-1507PINSTPL SAP Solution Manager Implementation Cont
ST-LV 100 0001 SAPK-10001INSTLV SAP Landscape Verification Wizard
ST-SER 701_2010_1 0002 SAPKITLOS2 SAP Solution Manager Service Tools
Then don't forget to perform step 5. After the installation steps.
Step 5 says this:
5. After the installation
To activate SAP Solution Manager Enterprise Edition, the Enterprise Addon SM_APPLM has to be activated in the IMG of the Solution Manager System. This is done via IMG activity SAP Solution Manager->Configuration->Scenario-Specific Settings->Activate Solution Manager Enhancements.
a) In the case of ST-400 SP15-SP17
To use Extended Tracebility in Change Request Management activate BC-Set SOLMAN40_CHARM_CONTEXT_001 in transaction SCPR20
b) In the case of ST-400 SP18 or higher
The activation of BC-Set SOLMAN40_CHARM_CONTEXT_001 will be done automatically.
In my spro i don't have this options->
I see the route Activate Solution Manager Enhacements in SPRO -> Cross Scenario Settings
And in enterprise extension I only see ( SM_CRON, SM_QC_AD, SM_SSP,SM_SUPP_VAR)
I guess that this in SP24 is done automatically, but you said, that don´t forget the step 5 after installation.
update:I check for updates of SP and this add-on don´t have SP for now -
Solution Manager vs Enterprise Solution Manager
Dear All,
We already have solution manager installed in our SAP System landscape.
But a visiting consultant give a new word to managers about enterprise solution manager with following benefits.
1-If we have enterprise solution manager then SAP AG can access our system and inform us about system health.
2-If we have enterprise solution manager then SAP AG will react on our ticket not on what we send but on the the actual actual condition of system.
3-We can only utilize our support services in a right way if we have enterprise solution manager.
1- Now first where I can check that the installed solution manager is standard or enterprise?
2- The benefit which is listed above is really available in enterprise solution manager?
3- Any tutorial or link defining how to install and configure enterprise solution manager.
Any response will be highly appreciated
regards,
Syed Saifuddin
SAP BASIS AdministratorDear Paul
Following is the current Status of our Solution Manager
S / W Comp / Rels / Level / Highest support Package / Short Desc of Software Component
SAP_BASIS 700 0011 SAPKB70011 SAP Basis Component
SAP_ABA 700 0011 SAPKA70011 Cross-Application Component
PI_BASIS 2005_1_700 0011 SAPKIPYJ7B PI_BASIS 2005_1_700
ST-PI 2005_1_700 0006 SAPKITLQI6 SAP Solution Tools Plug-In
SAP_BW 700 0011 SAPKW70011 SAP NetWeaver BI 7.0
SAP_AP 700 0007 SAPKNA7007 SAP Application Platform
BBPCRM 500 0007 SAPKU50007 BBPCRM
CPRXRPM 400 0007 SAPK-40007INCPRXRPM SAP xRPM/cProjects/cFolders 4.00 (ABAP)
ST 400 0010 SAPKITL420 SAP Solution Manager Tool
ST-A/PI 01J_CRM500 0000 - Application Servicetools for CRM 500 / 5
ST-ICO 150_700 0005 SAPK-15075INSTPL SAP Solution Manager Implementation Cont
ST-SER 700_2006_1 0003 SAPKITLOG3 SAP Solution Manager Service Tools
Bachup Solution I will manage with Tivoli Storage Manager.
But give me a path to upgrade my Solution Manager to EHP1 or Solution Manager Enterprise Edition.
regards
Syed Saifuddin -
Integrating Solution Manager in EP
Hi Experts,
We have a requirement of integrating SAP Solution Manager with EP.Is it the same procedure that we normally followed at the time of integrating R/3 or CRM like creating a system in the landscape and establishing SSO.
Regards
Indranil
Points will be awarded for useful answer.Hi
Indranil Chakrabarty
Thanks for replying.I have already created a system to integrate solution manager & implemented SSO via log in/pwd.I am able to execute the transaction like solar01,solar02 through a SAP transaction iVIEW.
The link you have send is describing about creating an iview of type epsolman type from par.By setting this can we execute all the transactions through iview...?
creating an iview of type epsolman from par is used to create an iview in portal to send Support desk message to solution manager and this has nothing to with working with functions of solution manager in portal.
i guess you wish to use functions of solman in portal.
as people said here basic requirements are
1) sso between solman and portal
2) solution manager system in portal
Regards,
Vijay. -
Question about setup ewa in solution manager 4.0
Hi
I tried to setup ewa in solution manager 4.0, but when I clicked on the "setup EarlyWatch alert", it told me that:
the Service is not available, Fehlercode:ICF-NF-http-c:000-u:SAPSYS-l:D-i:saptux04_SM4_04-v:0-s:403-r:Forbidden
HTTP 403 - Forbidden
any one can help me?
best regardsHello,
You will have to activate the service first in transaction SICF.
SAP recommends to do so via the the SAP Solution Manager IMG following the respective IMG path:
<i>SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Confiugration -> Basic Settings -> Standard Configuration of Basis Settings -> Solution Manager -> Activate Solution Manager Services</i>
Enhanced configuration of SAP EarlyWatch Alert (Service: /sap/bc/webdynpro/sap/dswp_rating_4_monitoring)
This application is fairly new and contained in SAP Solution Manager 4.0 SP12 onwards. Information on the respective functionality can be found right here in the SAP Solution Manager SP News:
http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000538663&_SCENARIO=01100035870000000202&_OBJECT=011000358700000478802007E
I hope this helps to solve your issue.
Regards,
Doreen -
Solution Manager 4.0 Title says "SAP Easy Access CRM"
Hi,
We installed Solution Manager 4.0 on Solaris/Oracle.
Solution Manager 4.0 Title in Easy Access page says "SAP Easy Access
Customer Relationship Management"
I want to change the title. So I created a customer message with SAP. They gave following steps. I followed these steps. It just displays the title. I don't see any option to edit the existing title.
Did you come across this situation?. If so, can you please shed some light?. Thank you very much for your time.
Steps
The menue which is displayed as initial menue can be defined in the IMG
(transaction SPRO) under the following path:
SAP Solution Manager Implementation Guide
- SAP Customizing Einführungsleitfaden
- SAP NetWeaver
- Application Server
- System administration
- Definition on initial menu
Please change this to: AI_SOLAR -SAP Solution ManagerWhat was the solution?
Hamed
Maybe you are looking for
-
Transport Error - DS does not exist in Source system
Dear All, I am getting below Error while transporting the DSO from DEV to Quality. DataSource 8ZM_ALT does not exist in source system DCQCLI041 of version A. I have checked the dataosource is active and available in Development system. But Its gi
-
Trouble connecting my iphone to my home wifi
I have just recently bought an iphone 4, however it wont connect to my home wifi. when i select my bt-homehub from the networks the circle just keeps spinning as if its loading, everything else like laptops etc are connected to the wifi so it cant be
-
I am new to Lightroom and have a file naming question. I previously used Capture NX2 to import and rename my files. My convention is "YYYY-MM-DD-HH-MM-SS-JAH". Capture NX2 had an option where it would add a "-n" after the seconds field (SS in above)
-
Alternative download - Creative Suite 5.5 Design Premium
Hello, I have been trying to download the CS5.5 Design Premium from Other downloads However, when I click the link I get an Access Denied message: "Access Denied You don't have permission to access "http://trials2.adobe.com/AdobeProducts/MDIA/CS5/win
-
Download assistant doesn't work
When I try to start the download assistant all i get is: What do I do?