Solution Manager create an IBase...

Hi fellows,
My question is, if in the future I must apply more satellite/backend systems in my SLD (SMSY) in Solution Manager... As you know when we want setup maintenance optimizer generally appears an error which it said that we must have to Generate an IBASE (IB51 & IB52) and so I created that Ibase entry with my all systems landscape... but imagine that I want to apply more systems in tcode SMSY (System Landscape Directory tree) when that happens I must create again on more time an Ibase, this is, I will have problems in maintenance optimizer if I apply more systems and don´t make the regenerate the IBASE ?
Best regards,
Thanks in advance,
Jmgmad

Hi Prakhar Saxena,
Thanks a lot for your quick and usefull answer... you have right!!
One more question about IBASE and the respective tcodes IB_GEN and IB52, I duplicate the systems in IBase monitor on IB52 I see in that tree of SAP solution Manager Installations I have twice systems, because when I regenerate the Ibase (in IB_GEN) I select the same systems that I have apply in past... so I want to delete the systems that are repeated... How can I do that ?! ...
Can you explain how I delete systems in that tree on IB52 (with Ext.ID: SOL_MAN_DATA_REP) ??
Thanks indeed...
I will give you a max point !
João Dimas

Similar Messages

Solution Manager Create remote monitoring entry

Hello,
I need some help or clarification please. We just upgraded our Solution Manager to EHP1 spk25 and I'm trying to setup Solman to support central system monitoring. I'm on the last step to enter the moitored ABAP system in CEN through RZ21 Techincal >Configure Central System>Create remote monitoring entry.
I can enter my own System ID but can't enter the RFC destination ? These default to *_RZ20_Collect and *_RZ20_Analyze. I want to use the RFC's already in place through Charm since these are already setup and working correctly. Can someone tell me how to change this or why we have to use the defaults.
Thanks in advance
Stephanie

Please disregard.
Thanks

Solution Manager - Create Project Directory structure

We're planning to use Solution managare for BW upgrade project and would like to maintain all the documentation (like status report, project presentation, Problem log) in SOLMAN. We would like to have directories and sub-directories so that user can select the directory to upload the document.
Could some one help me on how to create directory structure at project level? I'm familiar with business scenario option. Is it only option to load document? Can I've directory structure at project level instead of business scenario level.
Thanks,
Milind

Hi Milind,
You can create one more project for uploading and storing FS and TS.
If you don't want to use the buss scenario option.
For this new project select the components and from solar01 just create the folder manually by whatever name you want .say for e.g SD-pack1 ,pack2 etc.
Upload the files relevant to each module or so.
Please reward points if it helps.

Solution Manager: Creating test plan - no test cases uploaded show up

Hi,
I am attempting to create test plans that include all the test case documents that I uploaded to the system. Unfortunately, when I upload the documents, check them out and then in again, and then go to stwb_2 to create a test plan, the documents do not show up in the test plan structure.
Why is this and is there someway to make the documents show up?
Thank you!
Edited by: acraver on Mar 13, 2009 6:37 PM

Have u tried regenerating the Test plan by going to change mode and pressing the generate button after selecting the documents
Secondly what is the status of the doc is it change
Note whn u generate the test plan you have to chooose the Status of the Test Documents.
Hope it solve ur problem
Regards
Prakhar

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.

SSO from Solution Manager to Wily Enterprise Manager issue

Hi,
We are facing problem in SSO from Solution Manager to Wily Enterprise Manager. We have done the configuration as per the Wily Enterprise Guide- "Introscope Version 8 Installation Guide For SAP" Page 38.
Our Solution Manager system is running on AIX platform and Wily Enterprise Manager is on Windows 2008.
This is what we are trying
SOLMAN Production Client --> SOLMAN_WORKCENTER --> INTROSCOPE WORKSTATION --> this opens a new browser page and from there we click on Start Introscope -->
Result --> SSO doesn't work, still we get login window.
Introscope Enterprise Manager logs says -->
9/12/11 10:47:17 PM BST [WARN] [Manager] Single sign on failed: No SAP single sign on ticket was found in the request header.
Note: Another Solution Manager system in our landscape (on windows 2008 platform) is connected to same Wily Enterprise Manager (windows 2008) and from this solution manager SSO to Wily Enterprise Manager is working.
Please help me with your expertise to solve this problem.
Best Regards
Davinder

Hello Singh,
Could you check if you have maintained these parameters in instacne profile ?
From SCN post -> http://scn.sap.com/thread/969538
Hi Hector,
To configure SSO as per initial setup guide, please check your profile parameters in your Solution Manager as below:
You have set up SSO, see also:
SAP Note 817529: Checking the SSO Configuration
Installation Guide and Security Guide for SAP Solution Manager
Create the following profile parameters in the instance profile:
login/create_sso2_ticket = 2
login/accept_sso2_ticket = 1
icm/host_name_full = fully qualified server name
This parameter must be attributed to the fully qualified server name (for example wdfd002568.wdf.sap). The name must contain at least two periods. See also SAP Note 434918.
Hope this helps,
Regards,
-Rohan
BR,
kamil

No EarlyWatch Alert for Solution Manager task in SDCCN

Hello All,
We have configured SAP Solution Manager and managed system to generate EWA report.
In Solman, we have created the system, logical system and solution. We have activated the managed system in Setup EarlyWatch Alert in Solman.
In Managed system, we have activated SDCCN, assigned BACK RFC, created Maintenance package and refresh sessions.
However, after completing the Maintenance package task there is no EarlyWatch Alert for Solution Manager task created in managed system. We have reviewed the task logs and found no errors.
In Solman, when we create EWA for today's date the status is showing with an Hour glass stating that "Wait for session data: SAP EarlyWatch Alert and session number"
Kindly assist us in fixing this issue
Thanks in advance
Regards,
Satish

Hi
the task "early watch alert for solution manager" created automatically when did you perform the task "refreh session" or "Maintenance Package"
please create the relevant task, via : SDCCN -> Task -> Create ->Request session data ->Periodic -> Earlywatch Alert -> Continue.
'Schedule' the start date of the first session and - Task -- create Click on 'Refresh sessions' - Press 'Enter' - Select 'Now', to schedule the job 'immediately. once you create the relevant tasks you go by, in the Menu - Goto -> start - to activate the Earlywatch alert session Now, you can check the finished EWA task in 'done' tab.
Login to Solution Manager, goto trx. DSWP --> Select your solution, Solution Monitoring - Earlywatch alert - Click on Earlywatch alert --> start service processing --> Press 'OK' to start the background job - click 'Refresh'
Now, you can see the 'Early watch alert' in the green colour .
more further refer here [EWA guide|http://forums.sdn.sap.com/servlet/JiveServlet/download/156-1701991-9166329-1518/EWA_Activation.pdf]
jansi

Email Solution manager task report session

Good day,
I am currently tasked with generating task session reports from solution manager. Systems I am reporting on are ECC 6.0, BI, CRM & PI. I can generate reports fine, however I would like to setup solution manager to send these task session report to a list recepient vial email directly from solution manager. It should be like EWA reports send via email in this case I want to send task session report after I have completed the checks.
1) Is it possible to setup solution manager to do that?
2) I want to be able to highlight all issues that I have picked like how EWA highlights its alerts.

Hi
the task "early watch alert for solution manager" created automatically when did you perform the task "refreh session" or "Maintenance Package"
please create the relevant task, via : SDCCN -> Task -> Create ->Request session data ->Periodic -> Earlywatch Alert -> Continue.
'Schedule' the start date of the first session and - Task -- create Click on 'Refresh sessions' - Press 'Enter' - Select 'Now', to schedule the job 'immediately. once you create the relevant tasks you go by, in the Menu - Goto -> start - to activate the Earlywatch alert session Now, you can check the finished EWA task in 'done' tab.
Login to Solution Manager, goto trx. DSWP --> Select your solution, Solution Monitoring - Earlywatch alert - Click on Earlywatch alert --> start service processing --> Press 'OK' to start the background job - click 'Refresh'
Now, you can see the 'Early watch alert' in the green colour .
more further refer here [EWA guide|http://forums.sdn.sap.com/servlet/JiveServlet/download/156-1701991-9166329-1518/EWA_Activation.pdf]
jansi

IBase When Creating a Request for Change in Solution Manager 7.1

Hello all,
We recenlty upgraded our sandbox system to Solution Manager 7.1 SP3 and are currently investigating the new ChaRM functionality with the new CRM UI. Our company had configured ChaRM back in 2007 and has been working very well since the initial delivery.
While I was following the Request for [Change process simulation from RKT|https://websmp208.sap-ag.de/~sapidb/011000358700000478022011E/index.htm] on our sandbox system, I had noticed that the iBase and Component that we have created in transaction IB52 prior to the upgrade were not showing in our search when we were defining the Change Request Scope section. In the documentation that I have read leading up to the upgrade, there have been no mention of the iBase/Component data becoming invalid post-upgrade nor have I found a conversion process. I have done a search here on SDN and on SAP Notes to see why the iBase and Components were not showing up.
Has anybody encountered this issue since the upgrade to 7.1 or is there something I need to do in IB52 in order for the iBase/Component in the new CRM GUI?
Your assistance in this matter would be greatly appreciated.

Hi,
yes in 7.0 it worked for me too, that is because in 7.0 ChaRM searched for projects based on the IBase you selected.
If there were more than one project where this system is involved you got a pop up where to chose your project.
In 7.1 you chose the project directly, instead of let the system search for you.
And depending on what productive-systems are in this project you get your Ibase list.
If you don't select a project at all you will still get a list of all Ibases in your system.
Iif you ask the SAP, they will allways tell you that you have to have a productive system in your project, at least as you pointed out with a virtual system.
I did not read i t though and therfore ca nnot provide any sources.
This is all based on my experiences.
Best Regards
Daniel
Edited by: Daniel Titze on Nov 23, 2011 6:16 PM

IBASE in solution manager

Hello Gurus,
I have configured ChaRM in SAP Solution Manager 7.0 EHP1, all entries in SMSY are also correct.
Now when I create a new change request, it asks for requester, approver and various other fields including IBASE/Component.
I see the only entry assailable is 1 for Ibase and component as 0.
Now the question is the documents I am following to create Change request says that there should be IBASE for DEV , QAS and PRD systems..... any help why I am not seeing them here .... or any suggestions to make this ibase available here ??
I checked in IB51 and IB52 but only one entry is there.
Cheers!!
Shobhit Garg

Hi Shobhit,
how does your IBASE entry look like?
example:
Component       13
Identifikation
e.g.                  AI0   1234567890 811
Description       AI0 Productive Client 811    (example)
Within you Change Request you specify the target system/client by the IBASE Component (e.g. 13)
The description will be displayed after saving. (e.g. "   AI0 Productive Client 811    ")
Use generic search function for field 'component':
Field "Identification":    "AI0"           (example for system "AI0" )
Best regards
Horst
Edited by: Horst Förster on Feb 10, 2012 10:06 AM
Edited by: Horst Förster on Feb 10, 2012 10:10 AM

System/Ibase for DQ0 to be added in Solution Manager SM0-010

Hi,
Question: System/Ibase for DQ0 to be added in Solution Manager SM0-010
Please let me know the process how can do this. I will really appreciate.
Regards, Nabi.

Hi Nabi,
if it is an ABAP based application, check in transaction IB52, if it has been already automatically created there. If yes, you might only need to go to transaction dswp (solution_manager) and go to the menu select edit and in the drop down menu you should have 'Initial Data Transfer for IBase´.
If it is not there, you need first to check:
- RFC connections maintained for DCQ in SMSY
- Logical Component created in SMSY for DCQ
- Assignment to Logical Components in SMSY for DCQ
- DCQ added to the Solution SMSY
Then check again in IB52. IB51 is used for creating the entries manually.
If the entries are now in IB52, you need to execute the "Initial Data Transfer for IBase" again.
I hope this helps.
Regards,
Markus

Using HR data in R/3 to create business partners in Solution Manager

Is it OK for me to setup Solution Manager to automatically download HR data from R/3 to create the Business Partners (employee role) in Solution Manager?
We have setup SAP CRM 4.0 to automatically download the HR data and create Business Partners (employee role) in CRM. Since Solution Manager has the CRM component in it, I assume we can do it as well in Solution Manager.
Regards,
Mel Calucin
Bentley Systems

We did it, i don't see the problem...

Unable to create tickt in service desk - Solution manage.

Hello,
I have implemented service desk ( Solution manager) and It is working fine for most of the system but i am getting error while creating a ticket in service desk for one system.
Due to some RFC connection problem i have regenerated the RFC ( trusted , Read and TMW) from Solman to Satellite system.
and now I am not bale to create ticket for that system.
Error message :
The URL http://cismp.cargotec.com:8014/sap/bc/bsp/sap/dswpnotifcreate/msg_new.do was not called due to an error.
Note
The following error text was processed in the system SMP : Error SYSTEM_CORE_DUMPED occured. P1=11
The error occurred on the application server cismp_SMP_14 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: MSG_SUBMIT of program CL_DSMOP_BSP_NOTI_MODEL=======CP
Method: DO_HANDLE_EVENT of program CL_DSMOP_BSP_NOTI_CTRL========CP
Method: DISPATCH_INPUT of program CL_BSP_CONTROLLER2============CP
Method: DO_REQUEST of program CL_DSMOP_BSP_NOTI_CTRL========CP
Method: DO_REQUEST of program CL_BSP_CTRL_ADAPTER===========CP
Method: ON_REQUEST of program CL_BSP_RUNTIME================CP
Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_HTTP_EXT_BSP===============CP
Method: EXECUTE_REQUEST_FROM_MEMORY of program CL_HTTP_SERVER================CP
Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
Module: %_HTTP_START of program SAPMHTTP
Can any body guide me what should be done to resolve the issue.

Hi Prakhar,
As i mentioned workcenter is working fine for all other systems. and user have all roles same as in other systems.
BP is created and we are trying to create ticket from Solman itself so there is no point to maintain bCOS_CUST table.
but still we are not able to create ticket only for one system.
Error Message :
Error when processing your request
What has happened?
The URL http://cismp.cargotec.com:8014/sap/bc/bsp/sap/dswpnotifcreate/msg_new.do was not called due to an error.
Note
The following error text was processed in the system SMP : Error SYSTEM_CORE_DUMPED occured. P1=11
The error occurred on the application server cismp_SMP_14 and in the work process 1 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: MSG_SUBMIT of program CL_DSMOP_BSP_NOTI_MODEL=======CP
Method: DO_HANDLE_EVENT of program CL_DSMOP_BSP_NOTI_CTRL========CP
Method: DISPATCH_INPUT of program CL_BSP_CONTROLLER2============CP
Method: DO_REQUEST of program CL_DSMOP_BSP_NOTI_CTRL========CP
Method: DO_REQUEST of program CL_BSP_CTRL_ADAPTER===========CP
Method: ON_REQUEST of program CL_BSP_RUNTIME================CP
Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_HTTP_EXT_BSP===============CP
Method: EXECUTE_REQUEST_FROM_MEMORY of program CL_HTTP_SERVER================CP
Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
Module: %_HTTP_START of program SAPMHTTP
What can I do?
If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system SMP in transaction ST22.
If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server cismp_SMP_14 in transaction SM21.
If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 1 in transaction ST11 on the application server cismp_SMP_14 . In some situations, you may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system administrator.
Error code: ICF-IE-http -c: 011 -u: XABHYABH -l: E -s: SMP -i: cismp_SMP_14 -w: 1 -d: 20091006 -t: 141511 -v: RABAX_STATE -e: SYSTEM_CORE_DUMPED
Regards,
Bhavesh

Job Scheduling in Solution Manager - Error creating Periodic Job

Hi all,
I am in the process of testing the Job Scheduling functionality using the Solution Manager. I have setup the criteria manager, ec. in the satellite system, and done the config in Solman as well.
I am able to successfully setup up a 'on-time' job.
it's only when I try to setup a periodic job, I end up getting following error
Any thoughts? Is there any piece of config that's missing? All the SICF services needed for this functionality are running fine.
Thanks for the help.
500 Internal Server Error
Error when processing your request
What has happened?
The URL https://fsspsm.target.com:/sap/bc/webdynpro/sap/wd_ags_ejr_job_req_gaf_app was not called due to an error.
Note
The following error text was processed in the system PSM : Message was not created
The error occurred on the application server fsspsmap01_PSM_00 and in the work process 1 .
The termination type was: ERROR_MESSAGE_STATE
The ABAP call stack was:
Function: BAPI_NOTIFICATION_CREATE of program SAPLDSWP_NOTIF
Method: MSG_SUBMIT of program CL_DSMOP_BSP_NOTI_MODEL=======CP
Method: SUBMIT_REQ_CRM_DATA of program CL_AGS_EJR_JOB_REQUEST_FACTORYCP
Method: SUBMIT of program CL_AGS_EJR_JOB_REQUEST_FACTORYCP
Method: PROCESS_SCENARIO_PERIODIC of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
Method: PROCESS_JOB_SCENARIO of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
Method: IF_AGS_EJR_JSM_PROC_FPM_CTRL~AFTER_PROCESS_EVENT of program CL_AGS_EJR_JSM_PROC_STANDARD==CP
Method: AFTER_PROCESS_EVENT of program /1BCWDY/K54G9RCMK7J4Z427H49S==CP
Method: IWCI_IF_FPM_APP_CONTROLLER~AFTER_PROCESS_EVENT of program /1BCWDY/K54G9RCMK7J4Z427H49S==CP
Method: CALL_UIBB_PROCESS_EVENT of program CL_FPM========================CP

Hello,
This is the basic Job Scheduling functionality and not the Redwood Job scheduling, correct?
Have you performed the IMG Activiteis in SPRO?
See the following Help link:
http://help.sap.com/saphelp_sm70ehp1_sp23/helpdata/en/c5/7edcbd58ce4e29bc1baf1c4761d71f/frameset.htm
Change a job
You can change the scheduling of a job as long as it has not been completed. Proceed as follows:
Make changes.
Note
When you change a periodic job, the system searches for the changeable successor and only changes this successor.
If there is more than one changeable job with the same name, the system does not change any of these jobs.
End of the note.
Save your entries.
To release the job in the target system, select Release.
You go to the transaction SM37 in the target system.
You just may want to ensure HTTP Services have been enabled. I realize you said the services workin SICF, but this needs to be verified as 500 Internal Server Error most often means the HTTP services are not activated.
Regards,
Paul

Creating a new user in solution manager?

Dear All,
How to create a new user in solution manager for creating an incident?

prathish5,
I did this in our SolMan by following the instructions provided by a SAP document called: "Service Desk VAR Setup Master Data". I got it from the Support Portal, though I can't seem to find it now so I can't provide a link at this time.
Anyway, assuming that your SolMan is already able to download your master data (and/or your customers', if you are a VAR), these are the steps suggested by the guide:
1) The message creator (aka Key User) should have the following authorization roles:
SAP_SUPPDESK_CREATE
SAP_SUPPCF_CREATE
SAP_SMWORK_BASIC
SAP_SMWORK_INCIDENT_MAN
See also SAP note 834534.
A best practice is to create a Z copy of all of these roles (use transaction PFCG), so you can manage them and change them around if you need to. Just make sure to "activate" all the authorizations of your copy of the roles:
- Open the roles in tr. PFCG;
- Select Authorizations, and choose Change authorization data;
- If you get a yellow semaphore, be sure to review the authorizations and fill them according to your security policy. You can assign global permissions for all the authorization objects by double-clicking the yellow semaphore;
- Generate the profile, then go back and save the role;
2) Following the guide, with tr. SU01 I created a Template user and called it KEY_USER (make sure the user type is actually Template) and assigned to it the Z roles you created in the step above;
3) If your SolMan is working properly, you can now use report AI_SDK_SP_GENERATE_BP (tr. SA38) to create the Business Partners and SAP users automatically. The report will log in the Support Portal and read the users which are authorized to open a SAP tickets, and create a BP and user for each of them. Use the Template user KEY_USER created in step 2 as a "Reference user" and all the new users will automatically get the correct autorizations. Also if your SAP Connect (tr. SCOT) is correctly configured, you can choose to send an automatic mail to each user, with their login and generated password.
Otherwise, you can manually create a user with transactions SU01 and BP - be sure to fill the "Identities" table here - the report AI_SDK_SP_GENERATE_BP makes all these things automatically so it's definitely your best bet.
4) Your users should now be able to log in with the SAPgui and use transaction CREATE_NOTIF to create a new message in your SolMan. Also if you have done the preparation steps correctly they should also be able to log in your Incident Manager using their browser, and open a message there and also review their past messages.
Those are just a quick insight of the steps you need to do. This is NOT an easy thing to configure, at least it wasn't for me; if you don't have a reliable guide to follow you're going to struggle: I strongly suggest you browse through the SAP documentations (also the blogs) - http://service.sap.com/xsearch is your best friend!
I hope this helps a little bit. Good luck.

Solution Manager create an IBase...

Similar Messages

Maybe you are looking for