Adding existing systems to a new Solution Manager 7.0 Ehp1 system

Dear Experts,
We've just installed a new Solution Manager 7.0 Ehp1 system, we have a 3 system landscape in action, please need your help to connect these systems with this new Solution Manager system. The post installation Initial Configuration and Basic Configuration has been performed successfully. Also need your help with Maintenance Optimizer configuration and setting up EWA.
Please do share experiences, links and documents for the above.
Thanks in advance,
Best Regards,
basis-novice

Page 65-67 of Netweaver EHP2 Upgrade Guide found in service.sap.com/instguides.
You can use the explanation below to configure MOPZ and maintain systems in SMSY.
4.5.2Configuration of the Maintenance Optimizer
You have to configure the Maintenance Optimizer. For a list of configuration tasks, see the Maintenance Optimizer Configuration Guide.
Make sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully.
Related Documents
Available at...Maintenance Optimizer Configuration Guide http://service.sap.com /mopz (link at the bottom of the page)
4.5.3Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape. Therefore you have to maintain this data in SAP Solution Manageru2019s system landscape (transaction SMSY). In the following, you will find the description how to maintain this data. If you already have maintained the system landscape data, then check if the data is correct.
If you use the System Landscape Directory (SLD), then use it to capture the system data.
If you do not use the System Landscape Directory (for example, if you have a pure ABAP system), you use RFC connections to maintain the data.
Procedure
Maintaining the System Landscape Data Using SLD
1.
Register both Java systems and ABAP systems that you want to update in your central SLD.
The central SLD can either be on your SAP Solution Manager system, or you can have a separate system where you run the SLD (central runtime SLD). If you use a central runtime SLD, make sure that it is synchronized with the local SLD of your SAP Solution Manager system.
4.5.3Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape. Therefore you have to maintain this data in SAP Solution Manageru2019s system landscape (transaction SMSY). In the following, you will find the description how to maintain this data. If you already have maintained the system landscape data, then check if the data is correct.
If you use the System Landscape Directory (SLD), then use it to capture the system data.
If you do not use the System Landscape Directory (for example, if you have a pure ABAP system), you use RFC connections to maintain the data.
Procedure
Maintaining the System Landscape Data Using SLD
1.
Register both Java systems and ABAP systems that you want to update in your central SLD.
The central SLD can either be on your SAP Solution Manager system, or you can have a separate system where you run the SLD (central runtime SLD). If you use a central runtime SLD, make sure that it is synchronized with the local SLD of your SAP Solution Manager system.
4.
Create an RFC connection
1.
Choose the Client tab for your system.
2.
Maintain at least client 000.
3.
Create an RFC connection between the Solution Manager and the system you want to update using the RFC Assistant.
5.
Start the data transfer
To initiate the remote transfer of system data from the target system, choose the Read System Data Remote.
RECOMMENDATION
We recommend you to schedule automatic data transfers using transaction SMSY_SETUP.

Similar Messages

System monitoring configuration in solution manager EHP1

Hi all
I am in a bit of fix
We have upgraded our solution manager devlopment to EHP1
Now I have added one system through SMSY in solution manager to configure system monitoring
I have generated all the RFC's,I have created the logical component and solution and assigned the system to the solution
When I check my solution it is looking fine
Now when I go within solution and click on the tab system monitoring
It shows me on the left hand side -> Set up system monitoring
when I click on Set up system monitoring on the left part of SAP screen,strangely it doesnt take me to the activation of screen monitoring,it just shows me the best practices documents on the right side but nothing more than that
I have checked many guides,blogs and SAP tutors anfd have followed them but strangely I am not been able to go to the screen for activating system monitoring
Are there any activities that need to be done after upgrading to EHP1?
Are there any services to be activated for system monitoring?
Please advice
Rohit

I'm not 100% sure that it is necessary, but it won't hurt.
Perhaps the essential adjustment you need for system monitoring is being done in there.
It won't hurt

System copy guide for Solution Manager 7.0 SPS15

Hello,
a new hardware is needed for our SAP Solution Manager 7.0 SPS 15. I will install a new SAP Solution Manager and do a system copy from the old hardware to the new one. There is no migration neccessary, because OS and DB will be the same.
Now I'm searching for some informations and guides to do a system copy of a SAP Solution Manager. All I found was a system copy guide of Netweaver 04s SR3/SR2 with informations about Java Usage Types but not for Diagnostics.
Are there any guides or howtos to do a system copy with SAP Solution Manager ABAP+JAVA? Does anyone have experiences and advices?
Kind regards,
Sascha Piotrowsky

> Looking forwards to this event I'm afraid of forgetting some dependencies or configurations which have to be changed also, like SMD-Agents configuration,s trusted connections, wiley introscope, e2e and so on.
Wily is not part of the copy - you will need to copy this "manually". The connections et al must be re-done...
Markus

Confiuration of ides system in to the solution manager

Hi .
   We now installed new R/3 IDES server . Now we want to configure this new server into the solution manager maintenance optimizer . Kindly give me the steps for this configuration ..
Regerds
Selvan

Hi Ragu
         We already installed the new solution manager 4.0 server and IDES . Now we want to enable maintenance optimizer in our solution manager . As per one note i have to create one request as give n below .
     Create a new transport request (transaction SE09) in the source client of your Solution Manager system. Unpack the SOLMAN40_MOPZ_TTYP_SLMO_000.zip file from the attachment to this note. Copy the contents of the SOLMAN40_MOPZ_TTYP_SLMO_000.txt file into the transport request. Use transaction SCC1 to import the transport request into your Solution Manager client.
As per the above mentioned note , iam not able to attach the SOLMAN40_MOPZ_TTYP_SLMO_000.txt file in the tcode SE09 .
KIndly give the note for do this ,
selvan

System Monitoring Setup in Solution Manager

Hello Experts,
We are going to implement and configure Solution Manager - System monitoring setup for pre testing purpose
Currenly we have installed below SAP Systems
1.Solution Manager Server
2.ECC server (Without Ides) - Abap
3.CRM Server (Without Ides) -Abap + Java
We need to setup below tasks in Solution Manager
1.Early watch alert
2.System Monitoring
3.Central System Administration
4.Business Process Monitoring
5.Service Level reporting
1.Is it possible to setup the solution manager -above mentioned tasks without Ides system ?
Could you please someone give input reg this.
Thanks
Thirumal
Edited by: Thiru Thirumal on Aug 6, 2008 4:56 AM
Edited by: Thiru Thirumal on Aug 6, 2008 4:57 AM

Hi,
Q. Is it possible to setup the solution manager -above mentioned tasks without Ides system ?
A. Yes.
Check with links for
1.Early watch alert
This process helps you to identify potential problems early, avoid bottlenecks, and monitor the performance of your ABAP and JAVA systems and your most important business processes, regularly, automatically and effectively. The data collection infrastructure comprises the ABAP Service Data Control Center and the JAVA function module Data Provider. The SAP EarlyWatch Alert in the SAP Solution Manager is a service provided by SAP.
To be able to use it, you have:
maintained the non-ABAP systems correctly in the system landscape maintenance (transaction SMSY)
RFC u2013 Connections between: and an RFC u2013 Connections established.
your satellite systems and the SAP Solution Manager system
SAP Solution Manager and the SAP Service Marketplace
Solution Manager system and Solution Manager Diagnostics
Cf: Solution Manager IMG (transaction SPRO).
checked the availability of the tools required for the SAP Service sessions (add-on ST-A/PI), with the report RTCCTOOL.
activated Alert Monitoring and set-up the Automatic Session Manager (ASM) in the Service Data Control Center (SDCCN) of your satellite systems, for all SAP satellite systems and the central SAP Solution Manager of your solution
set-up your systems in a solution landscape in the SAP Solution Manager
configured Solution Manager Diagnostics
2.System Monitoring
The system monitoring in the SAP Solution Manager is, as described above, like a system-wide central CCMS. It can also contain the central CCMS (CEN) of satellite systems. These CENs can then monitor other components.
The graphical display in the SAP Solution Manager gives you access to the alerts of all systems in a solution. You can go to the local or central CCMS of the satellite systems.
The system proposes the most important alerts in the CCMS monitor collection, according to SAP experience, and their alert thresholds, for each system in the solution, in the system monitoring Session. You can activate or deactivate these alerts. The connection between the local CCMS and the SAP Solution Manager allows you to maintain the alert thresholds directly in the SAP Solution Manager, overwriting the values in the local CCMS.
3.Central System Administration
You activate the customizing for business processes in your solution, in the Business Process MONITORING session in the SAP Solution Manager. A monitoring tree element (MTE), or a monitor collection, u201EBPMu201C of several monitoring objects, is created in the local or central (CEN) CCMS of the satellite system.
The data is collected for the monitoring types of the business process monitoring in contrast to system monitoring, as follows:
● The system collects performance (dialog transactions), posting cancellations (V1 and V2) and u201EOther CCMSu201C and interface data, in the local CCMS of the satellite systems.
● The system collects background processing, application list, application monitors, delivery lists, and document size data, in the central SAP Solution Manager CCMS.
The SAP Solution Manager system copies the data from the local CCMS.
The graphical display in the SAP Solution Manager simplifies access to the alerts for the business processes, business process steps or the interfaces between the systems in a solution. You can go to the local CCMS of the satellite systems.
The connection between the local CCMS and the SAP Solution Manager allows you to maintain the alert thresholds directly in the SAP Solution Manager. These overwrite the values in the local CCMS.
4.Business Process Monitoring
The system and business process monitoring (including interface monitoring) in the SAP Solution Manager, both use the Computing Center Management System (CCMS) (transaction RZ20) architecture. This means that system alerts which occur in the local CCMS, are passed to the SAP Solution Manager via RFC connections between the SAP Solution Manager and the satellites. The system shows these alerts in a graphic or in Sessions. You can also handle the alerts centrally, without having to go to the local CCMS of the satellite systems.
You can see the alerts from several systems in a solution landscape in the SAP Solution Manager, in a graphical overview, in contrast to the local CCMS of the SAP Solution Manager satellite systems. This is the view of a central CCMS (CEN). You can also monitor non-SAP systems in a central CCMS (CEN) of a satellite system
5.Service Level reporting
http://service.sap.com/solutionmanager for all solman tasks as given below.
http://www.asap.net.cn/homepage_en/Solution%20Manager%20EN.pdf
http://help.sap.com/saphelp_sm32/helpdata/en/1b/f02c41ab78f66fe10000000a1550b0/content.htm
http://help.sap.com/saphelp_sm32/helpdata/en/9f/1f46570f8a4a268b3154e0e0f07280/content.htm
Regards,
Srini Nookala

System Copy based on Solution Manager 4.0

Dear All
How to install System Copy based on Solution Manager 4.0
Thanks

Dear All
How to install System Copy based on Solution Manager 4.0
Thanks

Solution Manager connection to Satellite system

Hi Gurus
I would like to find out on what kind of tests can I perform on business process management to ensure that the Solution Manager is communicating with the sattelite system.
Regards
Khuselwa

Hi Khuselwa -
Do you just want to ensure that a connection is established between Solution Manager and the satellite systems? You can do both a connection test and authorization test in the Configuration of RFC Connections transaction.
Transaction SM59
Expand ABAP Connections
Double click an entry
Choose Connection Test button.
You can also test the authorization by Utilities --> Test --> Authorization Test
Hope this helps,
Nathan

Building new Solution Manager / ChaRm Reports

Good Day
I looking for any documentation I can get my hands on to be able to build new Solution Manager/ChaRM reports.
Currently I am using u201C/TMWFLOW/REPORTINGu201D.
Thanks All
Don Newton

Hi Don,
Here you will find the first steps to work with Change Request Management scenario:
First steps to work with Change Request Management scenario in SAP Solution Manager 7.0
Hope it helps

Configure incident management for VAR in solution manager 7.0 ehp1

I want to configure incident management for VAR in solution manager 7.0 ehp1, now on service.sap.com all i can find is * SAP Solution Manager 7.1 SP3 VAR Config Guide V1 * under https://websmp204.sap-ag.de/var-partner/.
Can anyone point me to config guides on what needs to be done on the customer end and my end(partner side).
I am trying to fulfill the PCOE requirement below
5. Do you have a fully operational Incident Management System?
Thanks,

hi,
check out the below FAQ and
https://websmp208.sap-ag.de/~sapidb/011000358700000490172009E.HTM
Technical suppport
https://websmp208.sap-ag.de/~sapidb/011000358700000880802009E.PDF
and some more rkt and hw to guides on
https://websmp208.sap-ag.de/~form/sapnet?_SHORTKEY=00200797470000089947&
Thanks,
Jansi

Installation of Solution Manager 7.00 EHP1 on Windows Server 2008

Dear Experts,
We are installing Solution Manager 7.00 EHP1 on Windows Server 2008 Enterprise Edition 6.1 on a 64 bit platform. When running the pre-requisite checker it shows that the OS build 6.1 is not supported. Does anyone know which version of OS WIN 2008 server is supported or whether the Solution Manager can be installed on Build 6.1. Kindly suggest.
Regards,
Rohan

Found this note: [Note 1383873 - Windows Server 2008 R2 Support|https://service.sap.com/sap/support/notes/1383873]...
and also this forum thread: [Is Windows Server 2008 R2 Enterprise Supported]
Hope it is helpful...
Hector Asiain
Map-h

Error installing Solution manager 7.0 EHP1

Hi All,
I am installing Solution manager 7.0 EHP1 on Windows server 2008 64 bit. I have downloaded the installation DVD's from service market place (Named: 51036441_part1, 51036441_part2 and 51036441_part3).
But i am getting error while giving the path for LABELASC. It is saying that Found the label SAP:WEBAS:7.01:SAPINST..WINDOWS_X64_64. but need the label SAP:UT_SOLMAN70:NW701...*
Please help
Regards
Akshay Korade

Dear Achsay,
u can download this below files in following link.
https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_Developer-Site/en_US/-/USD/ViewFilteredProducts-SingleVariationTypeFilter
j2sdk-1_4_2_17-windows-amd64.exe
+ u can download suitable jce policies.
Regards
kesavan

Solution Manager Upgrade to EHP1 7.01

Hi
Need some help. Could you please share upgrade doc/exp with me, we are planning for upgrade solution manager from sp17 to sp19.
Stack level 18 or 19 is the part of EHP1 of Solution Manager version 7.01.
What is the process to upgrade the support pack to sp level 19? i have no exp to upgrade to EHP1 level..Any difference ?
Thanks in advance
Amar

Hi Amarjit,
Solution manager upgrade to EHP1 is same like other stack upgrade. You can do it using SAINT/JSPM. But only thing you need is good preparation.
Check upgrade guide on http://service.sap.com/solutionmanager.
Also, check SAP Note 1276895 - Add. info. about Upgrading to SAP Solution Manager 7.0 EHP1 and SAP Note 1169247 - Enhancements to Solution Manager 7.0 EHP1 upgrade
Thanks
Sunny

Adding system to ITSM in Solution Manager

We have ITSM implemented and is being used by some of the systems in landscape. We have a requirement o add few more systems to add to ITSM. The users of the systems should be able to create incidents, RFCs & UCs in ITSM. We are using Solman 7.1 SP8. Can you please provide with the process documents to implement it. Your hekp is highly appreciated.
Thanks in advance.

Hi Venu,
Please note that for CHARM you need to create the project and add the logical components there and activate the charm functionality, you will be then able to create the RFCs and UCs, however For ITSM, as soon as system is managed in SMSY/LMDB, ibase will get generated (governed by IB_GEN_AUTO in t-code DNO_CUST04),
Its always advisable to run the managed system setup (till RFC connections) for the systems you want to include.
For the configuration guides and help, go to below link
Configuration and Administration of ITSM - SAP IT Service Management on SAP Solution Manager - SCN Wiki
Thanks
Rishav

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.

How define ECC 6.0 system in smsy? Solution Manager 7.0 SP15

Hi Colleagues,
I have to define ECC 6.0 in my Solution Manager 7.0 SP15.
At smsy transaction -> Landscape Components -> Systems I don't find name SAP ECC to create new system. So I created it on SAP ERP.
My problem is when I go to create a logical component to assign my ECC system. So I go to transaction smst-> System Groups and Logical Components -> Logical components -> SAP ECC -> SAP ECC Server, I've created a Z New logical componets and at the right frame I am not able to assign my define system under SAP ERP. I get a pop-up "No system found for this product/main instance".
Please could you help me?
Thanks and Regards
Raul

Hi,
The problem is solved.
When I defined the system in smsy transaction, I made a mistake because I define it like a ERP 2005 and not a ECC 6.0, so in the next step when I want include this new system in a ECC 6.0 logical group, it wasn't able to find any ECC 6.0 system defined.
Thanks, René for your reply.
Regards

Adding existing systems to a new Solution Manager 7.0 Ehp1 system

Similar Messages

Maybe you are looking for