Solution Manager Scenarios on transaction SOLAR_PROJECT_ADMIN

Greetings, experts:
When I'm defining a new project in transaction SOLAR_PROJECT_ADMIN, in the scope tab I only see best practices for Water Utility. Do you know how can I display other components in here? Is there a way to show the other templates in this tab?
Another question: Is there a difference between checking options in SOLAR_PROJECT_ADMIN tab "scope", for example, "Tariff Management" and choosing Scenarios in transaction SOLAR01 (Business Blueprint) and SOLAR02 (Configuration)?
Thank you
Andrés Olivera

Hi there,
regarding your first question:
you have to create a template project to create templates. after assigning scenarios to templates you can then release them and they will be displayed in the scope tab.
with regard to your second question... the answer is nes the only difference i know of is that you can define to what degree a template in the scope tab can be adjusted. this is a functionality you would use for global roll-outs.
hope this was helpful
cheers
art

Similar Messages

Where to upload test case results in SAP Solution Manager?

Hi Experts,
I am new to test management module in SAP Solution Manager. I need to know where to upload test case results in sap solution manager.
Please provide screenshots on how to upload test results.
Regards,
Sanjana

Hi Sanjan,
let me provide you some more information.
First of all you create a SAP Solution Manager Project in Transaction SOLAR_PROJECT_ADMIN. I think this should be no problem. After creating the Project, make sure that the tap "Test Cases" is switched on in this project. The tap "Test Cases" is the tap below "Project Standards".
Go to transaction "solar02" and choose your created project. Find the tap "Test Cases" and upload a sample file. Please note that the configuration structure of this project can be configured in solar01 (Business Blueprint). There are many settings you can choose in a project regarding ti your requirements. Try to find them out! :-)
In transaction Test Plan Management (STWB_2) you can choose all relevant test cases you uploaded in your project and generate Test Packages which are mapped to your choosen Testers.
In Transaction stwb_work you will see the testers workbench.
Best regrads
J.Eichner

Error accessing transaction SOLMAN_WORKCENTER in SAP Solution Manager

I get the error below when I try to access workcenters in SAP solution Manager ehp1 via transaction SOLMAN_WORKCENTER
Error while processing your query
What has happened?
The URL call http://sol.test.com:8000/sap/bc/webdynpro/sap/ags_workcenter was terminated because of an error.
Note
The followin error text was processed in smc the systm: Syntax error in program CL_POWL_UTIL==================CP .
The error occurred on the application server sol_smc_00 and in the work process. 0
The termination type was: RABAX_STATE
The ABAP call hierarchy was:
Method: GET_QUERIES of program CL_POWL_QUERY_API=============CP
Method: GET_WORKLISTS of program CL_CONTROL_CENTER_API_FOR_POWLCP
Method: IF_AGS_CONTROL_CENTER_API~GET_WORKLISTS of program CL_AGS_POWL_BASIC=============CP
Method: GET_WORK_LIST of program /1BCWDY/0ALGK7P51EY0JCPIHVQ5==CP
Method: IF_COMPONENTCONTROLLER~GET_WORK_LIST of program /1BCWDY/0ALGK7P51EY0JCPIHVQ5==CP
Method: HANDLEDEFAULT of program /1BCWDY/0ALGK7P51EY0JCPIHVQ5==CP
Method: IF_WDR_VIEW_DELEGATE~WD_INVOKE_EVENT_HANDLER of program /1BCWDY/0ALGK7P51EY0JCPIHVQ5==CP
Method: INVOKE_EVENTHANDLER of program CL_WDR_DELEGATING_VIEW========CP
Method: NAVIGATE of program CL_WDR_CLIENT_APPLICATION=====CP
Method: DO_NAVIGATION of program CL_WDR_WINDOW_PHASE_MODEL=====CP
What can you do?
With the termination type RABAX_STATE you will find in the system smc in transaction ST22 more information on the cause of the termination.
With termination type ABORT_MESSAGE_STATE you will findon the application server sol_smc_00 in transaction SM21 more information on the cause of the termination.
With termination type ERROR_MESSAGE_STATE you can scan for further information in the trace file for the work process 0 in transaction ST11 on the application server. sol_smc_00 It is possible that an analysis of the trace files for the other work processes is necessary.
If you do not yet have a user ID, contact your system adminmistrator.
Error Code: ICF-IE-http -c: 001 -u: lolli -l: E -s: smc -i: sol_smc_00 -w: 0 -d: 20110415 -t: 165748 -v: RABAX_STATE -e: SYNTAX_ERROR -X: 00235AB4EF731EE099F78539B74CB1A5_00235AB4EF731EE099F78537687251A5_1 -x: 29BC67E0BACDF16BB1A500235AB4EF73
HTTP 500 - Internal Server Error
Your SAP Internet Communication Framework Team
How do I resolve this error?

Hi Mateus,
Thanks for your keen interest in assisting.
This is an excerpt from ST22....even though i am not an ABAP person.
Error in the ABAP Application Program
The current ABAP program "CL_POWL_QUERY_API===========CP" had to be terminated becuase it has come accross a statement that
unfortunately cannot be executed.
The following syntax error occured in program
"CL_POWL_UTIL===========CP" in include
"CL_POWL_UTIL===========CM007" IN
line 48:
"Incorrect logical expression: ")" without preceding "("."
The include has been created and last changed by:
Created by "SAP"
Last changed by: "BODE"
Error in the ABAP Application Program
The currect ABAP Program "CL_POWL_QUERY_API=============CP" had to be terminated becuase it has come accross
a statement that unfortunately cannot be executed.
What can you do?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "CL_POWL_UTIL===========CP".
You can also perform the syntax check from the ABAP Editor.
If the problem persists, proceed as follows:
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look at and manag termination messages.
and you can also keep them for a long time.
When i clicked on the ABAP Editor in ST22, I have the code below
method GET_QUERIES.
data: ls_authorities type powl_authorities_sty,
 lt_vistypes type powl_type_tty,
 lt_visqueries type powl_query_tty,
 ls_api_query type powl_query_asty.
field-symbols: <fs_query> type powl_query_sty.
cl_powl_util=>do_authority_checks_for_user(
 exporting
 i_applid = i_applid
 i_user = i_user
 changing
 c_authorities = ls_authorities
lt_vistypes = cl_powl_type_accessor=>get_visible_types(
 i_applid = i_applid
 i_langu = sy-langu
 i_username = i_user
lt_visqueries = cl_powl_query_accessor=>get_visible_queries(
 i_applid = i_applid
 i_authorities = ls_authorities
 i_langu = sy-langu
 i_username = i_user
 i_vistypes = lt_vistypes
loop at lt_visqueries assigning <fs_query>.
 move-corresponding <fs_query> to ls_api_query.
 insert ls_api_query into table result.
endloop.
endmethod.
The cursor is on this line containing the statement below
"cl_powl_util=>do_authority_checks_for_user("

BPH in Solution Manager

I am new to this area. Here I have 3 question:
1. How I can download one of the BPH from BPR? So that it can be seen in the Project Admin-> Scope-> Template selection.
2. I have a created a BPH in form of xls fromat, how we can upload to the system so that it can be visible in Project Admin-> Scope-> Template selection
3. Where to see Business Process Repository in SAP Solution Manager? means transaction or step to follow?
Thanks in advnace for your help

Hi Deejoy,
The BPH is how your project/solution is defined in SAP Solution Manager SOLAR01/SOLAR02.
To edit this, go to SOLAR_PROJECT_ADMIN and create a new project, in your case if you want a new template project.
Then in SOLAR01, you can begin to design your BPH and use the BPR to assist with this.
The BPH is based on Project, business scenario, business process and business steps.
You can design this manually and use the F4 function to search within the BPR against a business scenario/process.
It is not possible to import from an .xls format.
To be clear, to view the BPR, go to transaction SOLAR01 after you have defined a new project, open the project and against a scenario, choose F4 to browse the BPR.
Regards,
-Rohan

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.

Prblem Service Desk configuration in Solution Manager 4.0

Hi All,
Here I have done the configuration of Service Desk in Solution Manager 4.0 by using the document which I have for release 3.2. However I have face some problem in Step Initially create and Assign the Satellite Systems as iBase C and Manually create and Assign the Satellite Systems as iBase Co .So I exclude above mention step. But still I am able to create the support message from Satellite Systems.
So can please let me know whether it will work fine in upcoming time or Do I need to test my Service Desk configuration for same.
Moreover please let me know how to test Service Desk configuration for real time environment.
Following are the step and problem which I face while doing the Service desk configuration.
STEP 1 #Initially Create and Assign the Satellite Systems as iBase C
To be able to use the Service Desk and Change Request scenarios in SAP Solution Manager, you need to define the Installed Base (iBase). An iBase component has to be created for each satellite system from which Service Desk messages will be sent to the SAP Solution Manager system.
The iBase components for the iBase structure SOL_MAN_DATA_REP (installation 1) can be created and assigned either automatically or manually. Note that these components and the assignments can only be created once automatically for every solution. To refresh your existing iBase data execute IMG activity Manually Create and Assign the Satellite Systems as iBase Components.
Requirements:-
You have defined your system landscape in the Solution Manager System Landscapes(transaction SMSY).
Activities:-
1. In transaction SOLUTION_MANAGER, open a solution.
2. Choose Operations -> Service Desk.
3. Choose Edit -> Initial Data Transfer for iBase.
The data is copied automatically. The iBase systems for the solution are automatically assigned to SOL_MAN_DATA_REP (installation "1"). An iBase component is created for each system installation number (which can be displayed by choosing System -> Status).
For each solution repeat these steps.
Problem in STEP1 :- I am not able to check the System  Status.
STEP 2 #Manually Create and Assign the Satellite Systems as iBase Co
In this IMG activity, you define the Installed Base (iBase) manually, i.e. for refreshing existing iBases after solutions have been changed.
An iBase component has to be created for each satellite system from which Service Desk messages will be sent to the SAP Solution Manager system.
Activities:-
1. In transaction Change Installed Base (IB52), use the input help (F4) to find the Installed Base with external ID SOL_MAN_DATA_REP.
2. Continue as follows:
 If SOL_MAN_DATA_REP does not exist:
a) Call transaction Create Installed Base (IB51).
b) Choose iBase Category 01 (Installed Base).
c) Choose Enter.
d) Specify the iBase header data in the iBase section.
e) Specify the external ID SOL_MAN_DATA_REP and enter a short description.
 If SOL_MAN_DATA_REP exists:
a) Choose iBase No. 1 (SOL_MAN_DATA_REP).
b) Choose the SAP WEB AS component.
3. To assign the systems as iBase components, go to the Text item tab.
Three components are included in the standard package.
4. Add all the satellite systems as text items to the table:
o Column Short text: Description of the system
o Column Identification: System ID, space, installation number
5. Save.
After changes have been made to a solution, repeat these steps to update system landscape data for iBase.
Note:-
Every system is only listed once in the iBases. That means a system is not listed in an iBase if it has been listed in another iBase before.
Problem in STEP2:- Here I am not able to find Text item tab as per point 3 .
STEP 3 # Assign Business Partners to iBase Components
You need to assign business partners to the new iBase components.
Activities:-
1. In transaction Change iBase (IB52), choose Goto -> Partner
2. Assign business partners with the following functions to the new iBase component systems:
o Administrator
o Key User
o Sold-to Party
3. Save.
4. Repeat these steps for each iBase component.
Problem in step3 :- In IB52 t-code screen there no any menu path like goto  partner
Thanks a lot,
Harshal

Hi Harshall,
You have to enter the value as 1 in Installed base field and then press enter.
You will be taken inside and then you will be able to see the Goto - Partner screen.
Hope this will help.
Please reward points suitably.
Regards,
Naresh.

One Solution Manager for different customers

Hi Guys!!
I am configuring a Solution Manager for different customers wich have a different S-users and different users to manage the solution manager system.
My problem is that there is only one SAP-OSS RFC destination where I can fill the data only for one of the S-users. From "solution_manager" transaction you can indicate the S-user too (Edit - Global Settings) but the same problem occurs, I can fill the gap only with one S-user and I have to change this one when I want to work with different S-user.
Can i configure the system to indicate different S-users depens on the user who I use to logon to solution manager system?
Thank you very much in advanced,
Edorta.

Hi Edorta,
you did not mention, which scenarios do you plan to use.
Functionality to use the SolMan for many customer numbers is already available or will be added in future Support Package Stacks.
It has been already added for
- Maintenance Optimizer
Note 1021275 - Maintenance Optimizer: RFC Destinations for Partners
- Forwarding SAP Messages (with different S-Users resp. customers)
IMG: Solution Manager -> Scenario-Specific Settings -> Service Desk -> Value Added Reseller
Check for SAP Notes on component SV-SMG* with key word "VAR" (as Valued Added Reseller), "Service Provider"
Best regards,
Ruediger Stoecker
SAP Notes added
Message was edited by: Ruediger Stoecker

Integrating Trex search With Solution manager

HI Guys,
Please help me with this .
Let's say the solution manager is integrated in the SAP Portal and trex is available in the SAP portal.
Can we search documents stored in the solution manager via the trex which is integrated in the SAP Portal? Is there a how-to guide available on the config?
Any thoughts are appreciated.
Dev.

Hi Dev
I'm facing a similar problem.
We have a trex server. We connected the TRex to our EP KM. Fulltext search in our Portal KM works well.
We have several project documentations on our Solution Manager. I was hoping I could connect the KM repository of the solution manager to our TREX and search the docs from EP. I was able to connect the Solution Manager repository to Trex. The index is working well.
The procedure is described in note 750623 but unfortunately the note is far away from a how to guide so I hope this helps:
Trex:
- Go to Admin Tool. Then landscape - connectivity and click on create "Connection". Enter system information of your solution manager system. Then click on Create - RFC Destination (sm59).
Solution Manager:
- Transaction srmo: Create a new Search Server Relation (DRFUZZY) and enter the RFC Destination you created in the above step and set it to default.
- Transaction spro: SAP Solution Manager - Cross-Scenario Settings - Document Management - Servers - Connect Index Server for Full Text Search. Click on "Define Index Readiness" and mark both entries for "IWBSolar" and save.
- Now go tou se38 and start the report RSTIRIDX_REINDEX. Here enter IWBSOlAR for document area and execute.
- Now go back to spro: Start the IMG activity "Schedule Asynchronous Indexing and De-indexing" and schedule the indexing job (Make sure you have executed the report RSTIRIDX_REINDEX before).
If you want to test the search go to transaction SKPR07, go to tools, select document area IWB Solar and click on "test search".
Unfortunately I don't know if there is any bether transaction for the search.
I was looking for a possibility to search from EP directly to the solman KM. But unfortunately I didnt' find a solution for this. The only way I know is to connect the solution manager over a transaction iview im EP.
Hope I could help.
Marco

Solution Manager Data Extraction for BW

Hi,
We have a Solution Manager in place for SAP Systems. Our requirement is to extract data from Solution Manager into BW and provide BW Reports for Solution Manager Reporting & analysis.
What are the standard DataSources/Extractors available in solution manager for this?
What are the Business Contents (Infosources) available in BW?
Any help will be rewarded.
Regards
Prasad

Hi Prasad,
have you already found the related IMG tree? It guides you through the setup.
Transaction SPRO -> SAP Reference IMG -> SAP Solution Manager -> Scenario-Specific Settings -> Operations -> BI Reporting
transaction: RSA5 (Installation of DataSource)
- 0SM_SMG_ROOT                   Oberster Knoten Solution Manage
-- 0SM_SMG                        Solution Manager
--- 0SM_DSWPBI_DB390
--- 0SM_DSWPBI_DB400                  DB400 Data
--- 0SM_DSWPBI_DBADA                  Adabas Data
--- 0SM_DSWPBI_DBDB2                  DB2 Data
--- 0SM_DSWPBI_DBINF                  Informix Data
--- 0SM_DSWPBI_DBMSS                  SQL Server Data
--- 0SM_DSWPBI_DBORA                  Oracle Data
--- 0SM_DSWPBI_MODUL                  Module Data
--- 0SM_DSWPBI_PERF                   Performance Data
--- 0SM_DSWPBI_SERVER                 Server Data
--- 0SM_DSWPBI_SYSDATA                System Details Data
--- 0SM_DSWPBI_SYSTEM                 System Data
Best regards,
Ruediger Stoecker

Solution Manager to Solution Manager connection

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

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

Configuration Guide Job Scheduling Management with SAP Solution Manager

Dear Gurus
Could you please help me with the configuration guide of the Job Scheduling Management with SAP Solution Manager
Best Regards

Hello Luis,
the configuration activities can be accessed via the "Implementatiopn Guide" by calling transaction SPRO in your SAP Solution Manager system.
In SPRO navigate to -> SAP Solution Manager -> Scenario-Specific Settings -> Job Scheduling Management -> Standard Configuration and execute the following two activities.
1. Activate Solution Manager Services
2. Set Up Work Center for Job Scheduling Management
Make sure that your user has role SAP_SM_SCHEDULER_EXE (or_ADMIN) assigned.
Afterwards you should be able to access the Job Management Work Center and to create Job Documentation or to import Jobs from a Managed System into new Job Documentations.
The following SAP notes might be usefuly as well:
1054005 - FAQ on Job Scheduling Management
1117355 - Work Center roles
Kind regards,
Martin
http://service.sap.com/jsm

Howto Close support message in Solution Manager

Hello,
Iu2019m installing and setting up the Service Desk on my Solution Monitoring system.
Iu2019m able now to create a support message in my satellite system with menu action u201CHelp  Create Support Messageu201D. The message is put in the queue and could be edited in the tr-Solution_Manager under the Item u201CService Desk  Messagesu201D. When I open a message Iu2019m able to change the status of the message form u201CNewu201D to u201C in progressu201D etc. but the item u201CConfirmedu201D is always gray!
Could anyone explain to me how I or the end user could confirm thesupport message?
I couldnu2019t find a detailed description about the process flow only a global one.
Thanks for the information.
Kind regards,
Richard Meijn

Hi Meijn,
Already solved? If no, check the following customizing.
In SPRO, SAP Solution Manager -> Scenario-Specific Settings -> Service Desk -> Service Desk -> Status Profile -> Change Status Profile for User Status, then choose status profile "SLFN0001" or your customized profile.
"Lowest status no." and "Highest status no." shows which status it can be changed to.
For example, in the following case, you can not change the status from NEW to Confirmed. Also, you can not change it from WIP to NEW. In such cases, target status which you can not change to will be shown as gray in status list.
Status Text low high
10   NEW 10 20
20...WIP    20 40
30...
40   Confirmed 40 40
I hope this could help...
Kobayashi

System Monitoring in Solution Manager 4.0

Hi all,
I want to set up system monitoring for landscape BW, ECC and SCM systems using Solution Manager 4.0 and am new to Sol Man.
So could anyone please help me with the steps.
Thanks in advance,
Sandeep.

Sandeep,
Trust me, there is no one resource that you can refer to and complete this system monitoring project. I recently configured this a couple of days ago. I can tell you that I haven't completed it yet. I have only completed the configuring the 'System Monitoring' part of it. I am yet to define monitors so that, I can monitor what I want of the satellite systems. So far, it took me about 4 days. Let me point out the basic steps you need to follow. Beyond that, please refer to the links I paste below:
Steps to configure 'System Monitoring' in Solution Manager:
1. Follow the 'Solution Manager Preparation' found under SPRO --> Solution Manager --> Read Me.
2. Make sure you have the latest ST-ICO and ST-SER installed in your Solution Manager (Note: 892412).
3. Make sure the Solution Manager has the latest support packages applied.
4. Prepare the 'Satellite Systems' as per note 455356:
 a. Create the role 'SAP_BC_CSMREG' (if it doesn't exist) with the following authorization objects
 --> S_CCM_RECV (with the objects and values mentioned in the above note)
 --> S_RFC (with the objects and values mentioned in the above note)
 --> S_RZL_ADM (with the objects and values mentioned in the above note)
 --> S_CUS_CMP (with the objects and values mentioned in the above note)
 b. Create a 'communication' user CSMREG (if it doesn't exist) and assign the profile S_CSMREG
5. Create the user CSMREG in Solution Manager using RZ21 transaction
 -->RZ21 --> Technical Infrastructure --> Configure Central System --> Create CSMREG user (Provide the required password and confirm).
6. An agent needs to be registered in all the satellite systems that collects the monitor statistics and pass on to the Solution Manager. Before registering the agent in the satellite system, a 'CSMCONF' file has to be generated in the Solution Manager and store it in a central location which, will be used by the CCMS agent while registration. This CSMCONF file holds the communication details for the agent to talk to the Solution Manager. To create CSMCONF file, proceed as follows:
 --> RZ21 --> Technical Infrastructure --> Configure Central System --> Create Start CSMCONF for Agents
 --> Store the file in a central location that can be accessed by the satellite system/s.
7. In the satellite system, copy the file 'CSMCONF' to the working directory of SAPCCM4X (F:\usr\sap\PD1\SYS\DVEBMGS01\log\sapccm4x - for example. If the 'sapccm4x' folder does not exist, create one).
8. Copy the downloaded 'SAPCCM4X.exe' file to the kernel directory on the satellite system.
9. Execute "sapccm4x -R pf=<path of the instance profile>". This should ask for the 'CSMREG' password and the admin user password on the solution manager system. Please input the same and confirm other questions. Upon confirmation, the CCMS agent should be registered in the satellite system.
10.Make sure you establish the trusted RFC connection on the Solution Manager to the satellite system you would want to monitor. This you can do from 'SMSY' transaction.
11.After successfully creating the RFC connections, and assigning the system to a logical component, please go to transaction, 'SOLUTION_MANAGER'. You can see the monitored system in the System Overview.
Below are the reference links:
Weblogs Related to Solution Manager
Hope this helps. Award with relevant points if my response is helpful.
Thank you.

Help about Solution Manager Maintanence Optimizer

Hi All,
I have a small confusion how to follow the configuration of Maintenance Optimizer in Solution manager.
Yesterday i installed the solution manager and assigned the ECC server to that solution manager using SMSY transaction.
Now i have to configure maintenance optimizer; what are the doubts i have:
1) I choose 001 client to configure; now i have to create any user with all roles or else can i use sap* ?
2) what are the roles i have to assign that new user?
3) Now what step i have to follow; it mean goto transaction SPRO and follow or any other configuration is required?
Please give me some suggestions...
Thanks & Regards,
Vivek N.

> 1) I choose 001 client to configure; now i have to create any user with all roles or else can i use sap* ?
just create user with profile SAP_ALL and sap_new
> 2) what are the roles i have to assign that new user?
give all authirisation sap_all
> 3) Now what step i have to follow; it mean goto transaction SPRO and follow or any other configuration is required?
check http://service.sap.com/solman-mopz and SAP Note: 1024932
Samrat

Upgrade to SAP Solution Manager 3.2 to 7.0 EHP

Dear Experts
At present I am using SAP Solution manager 3.2. Now I am planing to update SAP Solution Manager 7.0.
I am some confutation in SAP Solution Manager 7.0 and SAP Solution Manager 7.0 EHP1,
what i do please help me.
Regards
Sanjay C.

EHP1 is basically a product enhancement of 700 - i.e offers new functionality
Usually to get to Enhancement packages you need to be operating NW2004S stack based product - in this case 4.0 (now called Solution Manager 7.0)
I think this proposal will require first an upgrade from 3.2 to 4.0
then after applying Enhancement Package EHP1 and following pre-reqs for both steps
Also bearing in mind that Solution Manager is RFC dependant any change in SID, Hostname or client will require
all RFC connections will need to be adapted
There may also be special considerations depending on source configuration or the active Solution Manager scenarios and content
I would take a look at following PDF for reference - it may help in the initial 3.2-->4.0 upgrade
http://service.sap.com/~form/sapnet?_SHORTKEY=00200797470000090041&_SCENARIO=01100035870000000202&_OBJECT=011000358700000208052007E
Best wishes
Stuart

Solution Manager Scenarios on transaction SOLAR_PROJECT_ADMIN

Similar Messages

Maybe you are looking for