Logical systems while implementing charm in solution manager

Hello Everybody,
I just wanted to know how many logical systems we need while implementing charm in solution manager 7.0. I have 3 clients in development , 3 clients in Quality and 1 client in production.
Thank you,
vikram.

Hi Vikram,
Yes, i1n ChaRM we always work with logical systems, I mean clients.
The standard is:
DEV -> QAS -> PRD
However, you can also use:
- Minimum
DEV -> PRD
- Target groups
DEV -> QAS -> PRD
- > TST
DEV -> QA1 -> QA2 -> PRD
DEV -> QA1 -> PR1
-> QA2 -> PR2
There are a lot of combination possible.
BR
Fernando

Similar Messages

Problem in CHaRM Configuration - Solution Manager 4.0 SP16

Hi All,
We are in the process of configuring CHaRM in Solution Manager 4.0 with SP16. We have created the project and the activated CHaRM for that project and created the task list as well.
We are able to create the Change Request transaction and also approve the transaction successfully.
ISSUE
The popup of selecting a maintenance cycle while approving the Change Request is not appearing.
When we go to the document flow and select the next document it says
No maintenance cycle is open for the current system
Message no. SOCM_ACTION_LOG011
Maintenance Cycle is very much active when we check from transaction /tmwflow/cmsconf --> Environment --> Scheduling --> Display maintenance cycles.
We are not able to see any maintenance cycle from transaction code crm_dno_monitor
Any help would be highly appreciated.
Thanks and Regards
Siddarth

I have a question regarding the organization of Solutions in Solution Manager.
First, I have 3 solution manager boxes
1 Sandbox
2 Dev
3 Prod
In sandbox, I have a sandbox 'solution' that contains all sandboxes
In dev, I have no 'solution'
In production, I have all dev through production boxes lumped into one 'solution'.
I was thinking that maybe I should break up the solution in Production to have only prod boxes, and then build one in dev that contains dev and qa boxes.
My question is that when I configure CHARM to manager transports, will that work to separate DEV/QA from Prod OR will I need all the dev, qa, prod boxes in one 'solution' since that is how transports flow??

How to get the ASAP 7.0 Implementation roadmap in Solution manager system?

Hi,
We are on SOLMAN 7.0 SP19 and we wanted to use the ASAP 7.0 roadmap for an implementation project. But currently we dont see this roadmap in the list of Roadmaps available. Can some one tell how it can be brought in and made available in Solution manager system. Is it done through a SAP note? If not where do we can get this roadmap? I know the HTML version is available in service matketplace but we want the roadmap to be assigned in Solution manager project.
Regards,
Kathir

Hi Lori,
Thanks for your reply. Do you have information on what support pack level of ST-ICO will have the Roadmap ASAP 7.0?
The currentl level of my system is ST-ICO 150_700 0018.
Regards,
Kathir

Manage transports (without ChaRM) in Solution Manager?

Hi,
How do I manage transports in target systems (ECC, APO, etc.) using Solution Manager. We have the Dev systems (ECC, APO) connected using RFC to Solution Manager. Configuration (SOLAR02) will be done using Solution Manager. So the question is - how do we manage transports (without ChaRM being present) using Solution Manager?
Any suggestions/recommendations? I would greatly appreciate any feedback.
Edited by: GiveMeFood on Sep 22, 2011 10:05 PM

Hi,
One of the main features available with the Solution Manager is ChaRM. It has been introduced to basically deal with the diverse transports management and related control framework over the SAP lanscape. Having a Solution Manager and not using ChaRM defeats the purpose of installing a Solution Manager in the first place. A better approach would be to incorporate the features provided by the system.
In my opinion - you should configure ChaRM, else it would not make sense to have the SolMan in the landscape. You would start using one of the features which you already have !
Regards,
Srikishan

ChaRM in solution manager

Dear experts,
We had implemented the SM3.2 (change request management ,EWA and Support desk) in 3-tier landscape, my question is whether we can implement the Change Request Management in 2 tier landscape .
The scenario which we have is 2-systems -
Production with 700 & 900 client and Development with 200 , 300 , 400 .
200---Development client
300---Customizing client
400---Testing client
700---Pre production client
900---Production client
Usually by normal transport system we use to take the request from 200 & 300 to 400, after that we again test it in 700 then take it to 900 production client.
Now please suggest that how we can configure change request in this scenario, if not possible can clients within the system be configure as different system.
can we configure the ChaRM as 200>400>900 where 200 & 400 are the clients of same server or 200>700>900 .
Thanks in advance|| urgent
Chirag Kohli

Dear cherry , prakash and tom..
See i think i am still not able to clear the scenerio.....
1. Dev box is having 200 300 400 clients
2. Prd is having 700 900 client ..now i want to take the request by both of following routes -->
1. 200--> 900....as the 200 is workbench client so testing not required
in this case i got stuck after releasing the request frm dev server .........now no option in change document for importing it directly to production is there .
2. 300-->400 for testing in dev customzing scenerio.
then 300--> 700 for testing in PRD customzing scenerio.
then from 300 --->900.
no idea how to do this.
i hav done all the customizing required alongwith CTC=1 extended tr. control as i have already had configured CHARM in 3-system landscape
simply i want to ask that what should be the TMS route structure for such kind of scenerio.
Also u have mentioned that it can b done through transport gr.........is it transport gr or transport target group u are talking abt.
it will be very grate full if u can forward me the e-mail id at [email protected]
chirag

Need help on implementing functionalities of solution manager

Hi solution manager gurus, i have to propose a method to implement SOLMAN functionality
Landscape consists of around 15 servers
SAP users 800
typical 3 system DEV-CONS-PRD landscape on all instances
Till now only Upgrade service functionality has been used in SOLMAN, they would like to implement the services below
   1. Engagement and Service Delivery u2013 service delivery and issue management
   2. System Administrations (Solution Monitoring, Root Cause Analysis, System Diagnostic, including non-SAP IT environments)
   3. Implementation/Upgrading SAP Solutions (Scenario Management)
   4. Business Process operations (Incident Management, System Landscape (cross IT landscape)
   5. Change management (for functional enhancements and updates)
   6. Test Management
Can anyone suggest the right approach in implementing those services
also can anyone suggest a rough possible time line in implementing this with rough FTE?

Hi,
my suggestion is to check the standard documentation of the interface IF_EX_ME_GUI_PO_CUST.
After that you can check the method IF_EX_ME_GUI_PO_CUST~TRANSPORT_TO_DYNP in the example implementation class CL_EXM_IM_ME_GUI_PO_CUST.
Usefull links:
[Re: Implementing badi ME_GUI_PO_CUST;
[Re: ME21N - PO Enhancement using BADI;
Kind Regards.
Andrea

Good guide over implementation features of Solution Manager

Hi Gurus,
Iam new to Solution Manager . We currently hv Solution Manager 3.2 installed in our scenario.Iam being asked to xplore athe features of SM. Can somebody send me good pdf/word guides detailing the features of SM like Solution Manager Diagnostics,Project Simulation, Change request Management and System Monitoring etc and their benefits of implementation along with scope.I currently want good guides over these features.My Email Id is [email protected] .
Regards,
Saumya

Hi All,
Iam sorry i think i hv put up my question in a wrong way ,actually i am looking forward to implement only two features in Solution Manager as of now :
Solution Manager diagnostics and Project Simulation
So i require good detailed pdf/word guides on their implementation along with their requirement details .Plz dont provide Help links as i already know them.My Email id is [email protected] .
Regards,
Saumya

ERROR while CREATING RFC FOR SOLUTION MANAGER DIAGNOSTICS

Dear all,
Hi,
I am configuring solution manager 7.0.
In SPRO>basic setting >operation>solution manager diagnostics > create RFC for solution manager diagnostics i am getting this error
program WEBADMIN not registerred.
can any one tell me how to register this program in sap gateway.
best regards
azeem

Hi Azeem,
Just before creating the rfc connection do this step.
Set-Up Solution Manager Connection to Solution Manager Diagn
Use
Check the connection to function Solution Manager Diagnostics.
Default Settings
The function Solution Manager Diagnostics is installed on the Java instance of the Solution Manager system by default.
Activities
If the default values are correct, save the settings.
To run the Solution Manager Diagnostics in another system, enter the required data and save.
Also check that your java is active.
Regards
Ashok

Required "/" (root) file system size on UNIX for Solution Manager.

Hello SAP Gurus,
   I am setting up SAP Solution Manager 3.2 on HP-UX. It is asking me about 350MB free sapce on "/" file system for Central Instance installation and about 120MB free sapce on "/" file system for Database Instance installation.
   I am installaing everything on to shared disk which mounted under /usr/sap. Why it needs free sapce in "/" file system. Is there any workaround to get rid of this requirement, as I have very less free sapce on "/" file system and I don't want to take the risks involved in increasing this size.
   Are there any SAP recommended sizes for "/" file system?
   I stuck in the middle of setting up SAP landscape on HP-UX (11.23). I searched through the Installation documents but I couldn't find any thing helpful in this regard. It is urgent requirement to set up this so please let me know any solution or workaround ASAP.
   Any help is greatly appriciated.
Thanks in advance.
Regards,
cvr/

Hi Vaibhav.
Normally "canonical path not available for (folder name)" means:
1. Wrong username/password. Please double check you credentials.
2. The resource cannot be linked from the portal server. Please be sure that you can connect to the next ports in windows server from the Unix Server:
a. NetBIOS Session Service TCP 139 This port is used to connect file shares for example.
b. TCP 445 The SMB (Server Message Block) protocol is used among other things for file sharing in Windows NT/2000/XP. In windows NT it ran on top of NetBT (NetBIOS over TCP/IP), which used the famous ports 137, 138 (UDP) and 139 (TCP). In Windows 2000/XP/2003, Microsoft added the possibility to run SMB directly over TCP/IP, without the extra layer of NetBT. For this they use TCP port 445.
I hope these things help somebody.
Best Regards,
Jheison A. Urzola H.

Managed System Setup / Configure Diagnostics for Solution Manager itself

Hello,
I'm trying to run the "Managed System Setup" for the Solution Manager itself and
I got a problem in the step 4 (Diagnostics Configuration / Configure Diagnostics):
In the new opened window is only the ABAP stack displayed and the Java stack
is missing.
Does somebody know how to make the java stack visible?
From my point of view seems the configuration of the SMSY ok. The java stack is also
as "relevant" set.
The Solution Manger 7.0 EHP1 is on SP25.
Thanks in advance for your help!
Kind regards,
Joern

Hi Jorn,
I dont think its happening just because of your CR Content.
Still If you want to update it,then go to Administration Tab in SLD->>Import the latest CR Content from there.
As the latest CR Content is :SAP CR Content Version (sld/active): SAP_CR 7.6 (produced 11/17/2011)
And Jorn if you are stucked in the Diagnostic Agent registration then Go to Agent Candidate Administration->>In connection
Parameters Tab go to->>Custom SLD Connection Parameters->>Apply->>Mark the Diagnostic Agent you want to
connect->>Attach->>Give the password of the SMD_ADMIN->>Apply->>This way you will connect to the available Diagnostic
Agent.Hope this will help your problem.
Thanks & Regards
Ajitabh
Edited by: jitu001 on Dec 23, 2011 5:47 PM

IMPORT_PROPER error while importing patch in Solution Manager 3.2

I have a problem while importing Patch component ST and patch name SAPKITL319 in the middle of the installing patch it shows an error IMPORT_PROPER error and an red light and a message (Error stop). Please help me to sort the problem.
Satinder Lamba

Hi Saurabh,
sorry, I am not able to support you in finding the cause for the connection problem.
Anyway, my recommendation:
- Delete the SolMan 3.2 installation
- Install Solman 4.0
- Apply all Support Packages
- perform the configuration on 4.0 according the IMG
Configuring SolMan 3.2 is wasted time, if it has not been used in the past. SolMan 4.0 supports implementation / upgrade from/to SAP ERP 2004.
An upgrade in the future costs much more time and money, then to reinstall 4.0 now.
Deleting SolMan 3.2 and reinstall SolMan 4.0, this will only 2 extra days. Upgrade takes about 4-10 days.
Best regards,
Ruediger Stoecker
Message was edited by: Ruediger Stoecker
Spelling mistakes corrected, more information on days.

Error message in solution manager while importing transport using CHARM.

Hi All,
I am gettting below message while i am trying to import a change request using CHARM from solution manager
"You are not allowed to work on a CR for UNITEOPS"
"Data type-specifc customizing missinge for a data type"
But other user in our team able to do the import of change request. I checked all roles and authorization are same for both the user but still it is not working for my user-id and it is working for my team member user-id
Can you please guide? Is there any customizing missing for my userid?
Thanks

Hi,
Perhaps the info in this thread could be useful:
ChaRM roles or profile missing for Developer and Change Manager
Regards,
Srikishan

Solution Manager ChaRM Issues when Upgrading Satellite System

When upgrading a satellite system that is connected to Solution Manager's Change Request Management, is there anything that we need to be aware of?
Will Change Documents still be able to go to completion (Production status) if we modify the landscape from the time the Change Document is In Development to the time it is moved to Production?
1. Normal Correction (In Development) Development (ECC 5.0) -> Quality (ECC 5.0) -> Production (ECC 5.0)
2. Landscape is changed to Development (ECC 6.0) -> Quality (ECC 6.0) -> Production (ECC 5.0)
3. Normal Correction moved to To Be Tested -> Consolidated -> Production
Will the Normal Correction be in error because the landscape changed for the iBASE?
Are there any other lessons learned that anyone has experienced with Change Request Management or Implementation during and after an upgrade?
Thank You,
Carlen
Edited by: Carlen Yuen on Jan 13, 2009 1:50 AM
Edited by: Carlen Yuen on Jan 13, 2009 1:51 AM

Thanks Subhashini!
We had issues updating the Task List in the past. After we update the landscape and refresh the project and update the Task List, do you foresee any other problems?
Are there any additional items we should look out for? For example, we understand it is a requirement to release all transports prior to beginning the upgrade. However, since the release of the transport locks the change into the cycle for the next production move, this will present a problem if the change is not yet ready to be moved into Production. Do you have any further insight to any additional issues such as this?
Thanks again!
Carlen

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.

Evaluation system with Solution manager

has anyone added an evalaution system where a user who logged a support message can evaluate the Solution given, with Solution manager. Basically the same thing like SAP have. When you close a call you have to rank the messageeg in regards of qaulity of answer etc etc..,
Anyone that might have any ideas how to do this, could you please give me some direction to how I can implement an evaluation system.
I thought of having a URL added to confirmation message, where the user can click on to take him to some area where he could evalaute the message. This systems is then linked to Solution manager so that I can report on these messages and the evealuation received for these support answers.
I will appreciate any feedback and any ideas would be most welcome to help me to get to a method of implementing such a evaluation system or developing such a system.

Dear Johan,
Firstly the kind of scenario that you are trying to implement is not possible via the standard configuration of Support Desk.
What I can think of is probably creating an action while closing the message which generates a form for the user to be filled and saves the values into an custom table for questions based on evaluation of the solution.
Later you can generate reports based on this table.
Regards
Amit

Logical systems while implementing charm in solution manager

Similar Messages

Maybe you are looking for