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

Similar Messages

Solution Manager IBASE and R/3 assets

Hi,
In R/3 we have our Assets (tcode AS02) and we are using the tables ANLA, ANLB, ANLC, ALNH, ANLP and ANLZ.
We want to setup the IBase in Solution Manager with data from the R/3 Assets. What I mean is, how can we import the Assets from R/3 in the Ibase of Solution Manager.

Hi
Check the links
[https://websmp108.sap-ag.de/~sapidb/011000358700000894082006E.sim]
[http://service.sap.com/rkt-solman] --> ur Solman version --> Overview and setup of solution manager
Hope this helps you
regards
Naveen

What is exactly a IBASE in SAP Solution manager

Dear all
I'm making the configuration of service desk on SAP Solution manager, and then i have to make a set up of IBASE. Can anyone tel me what exactly is IBASE in solution manager?
thanks
Edited by: hchabi on Apr 1, 2010 1:45 PM

Hi
In solman you have SOL_MAN_DATA_REP as main IBASE or 1 and other managed systems will be attached to it as a component.
and you can check it in IB53 by entering "1" in the initial screen
For automatic generation you can use tcode IB_GEN and all the connected systems ibase will be generated and attached to ur ibase
Morever theoretically,
An installed base can be described as a multilevel structure of installed base components for managing objects (for example, devices, machines, software) that are installed, or are going to be installed on site at the customer site. An installed base can represent the reference basis for services.
An installed base describes the hierarchical structure of these objects and their individual parts (components
In business processes, an installed base can be referred to as a general unit or as an individual element (component).
The set of installed objects at the customeru2019s can be used, for example:
·        To determine the exact object for which a problem has been reported
·        To determine in detail what the transaction (for example, visit by field service representative, repair by a service employee) refers to
·        By the service employee as information about which object is affected and the parts it consists of
·        For documenting changes made to objects
Hope it helps and doubt is cleared
Regards
Prakhar

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

Solution Manager - Error Message DSWP349 - No IBASE Components Exist ...

The subject error DSWP349 occurs when using transaction Notif_Create for a new Service Desk Message.
The error message points to the use of IB52/IB53 which has already been correctly (as far as I can tell) used to set up the IBASE components.
The error message also point to Note 824640 which I have checking out and also points to Note 1059271 from SAP Service Marketplace.
I am going to try and apply some of those notes' recommendations but as they do not seem directly relevant, am looking for any other suggestions in the meantime; for example, if anyone has an printout example of how the IBASE and its lovely components should look in IB52/IB53 that would be most appreciated !
Last point. Maybe part of the problem is that our SAP Solution Manager only links to one other internal SAP system and is not 'connected' to SAP AG (as it is an external system - this for security reasons), however we do have, for example, some external RFCs entered as part of the configuration.
Thanks all.

Hi
The issue is now resolved, this is how I did it.
1) Removed entries from BCOS_CUST from client 000 for OSS_MSG which was pointing to the RFC name
Then got another error:
No RFC connection to the central lock information management system.
The project lock functionality is active in the local system, but there is no RFC connection to the Solution Manager system.
2a) Ran the report in SA38 TMW_CONTROL_PROJECT_LOCK with selection for Deactivate the "project lock functionality".
2) Filled the "Deactivate Project Lock" field with "X" then clicked EXECUTE.
Problem got Solved.
Thanks
Ashish

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

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

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.

Service Desk Customizing in Solution Manager 4.0 SPS12

Hello,
I try to customize the service desk in solution manager SPS 12.
I follow the IMG :
1. General Settings of solution Manager (Profiles...) => OK
2. Connection to SAP => OK
3. System Landscape and Solution
    Only One system my solution Manager. => OK
4. Service Desk BC Sets => OK
5. Business Partner :
    I have created two key users (KEY_USER1 & KEY_USER2) as BPs (101 & 106)
    I have created One System Admin (ADMIN) as BPs (105)
    I have created two Message Processors (PROC1 & PROC2) as BPs (102 & 103)
    I have created one Org. as BPs 104.
=> OK
6. iBase
   I have initially created the iBase from my solution => OK
   I try to assign the partner to the iBase component => First Problem : the system do not propose the System Admin & key user function when I go to Goto->Partner. Do I miss something ?
7. Org Model
I try to create my Org. model as follow :
Service Desk (O)
         Team 1 (O)
             Processor1 (S)
                 SDUser1 (BP)
                     PROC1 (U)
         Team 2 (O)
             Processor2 (S)
                SDUser2 (BP)
                     PROC2(U)
=> Second problem : it is said in the documentation and in some blogs on the sdn, that when we create the root org, and the subsequent org, the system will create and assign automatically the BPs. That doesn't work in my system. I do not understand why. So I have assigned directly the position conatining the Users Proc1 & Proc2 as BPs.
8. Partner Determination
    Then I would like to assign automatically messages created by KEY_USER1 to PROC1 and messages created by KEY_USER2 to PROC2 depending on the user group they belong (or depending on the relationship they have with the messages processors).
    => Third Problem : I don't how to do it ! and i don't know what to do with the partner function Support Team.
Could someone help me.
Thanks in advance.
Guillaume Bruyneel.

hello,
I found some interesting information concerning the automatic creation of BP from the Org. Model :
I have activated the HR integration through :
IMG->CRM->Master Data->Business Partner->Integration Business Partner-Organisation Management.
And NOW the automatic creation of the BP is working !
I'm still trying to solve the two other problems.
Guillaume.

Support desk queries on solution manager

Hi All
I have few queries on solution manager support desk functionality.
1.Is this the only way to create support desk message HELP-CREATE support desk Message from each individual system??
2.In our scenario,when we are creating the message we would like to assign component( it should be project specific component,not SAP specific component)...How to acieve this??
3.We have a requirement where the message has lot of status and fields and depending on the message processor I would like to control which status or field user should be able to view and work on...how to achieve this??
4.Need the way to send a message to the processor,as soon as his name appear as message processor.
5.I want to track all the persons involved in the message processing,how can I do this??
6.I want to use a different transaction type not the standard SLFN,so what configurations are needed??When I create a message it should automatically take properties of transaction type of newly created one??

Hello Dolores,
first of all thanks for that answer. I read it in the germany documentation help.
Here an extract:
+Anlegen von Support-Meldungen über NOTIF_CREATE
Mit der Transaktion NOTIF_CREATE können Benutzer, die in Satellitensystemen arbeiten, Meldungen anlegen und an den SAP Solution Manager versenden.
Vorgehensweise
Starten Sie Transaktion NOTIF_CREATE.
Geben Sie folgende Werte im Dialogfenster Anlegen einer Support Meldung ein:
Priorität
System/IBase-Komponente
Kurz- und Langtext
Um Anlagen anzuhängen, wählen Sie Registerkarte Anlagen.
Sichern Sie Ihre Eingaben.
Ergebnis
Sie haben eine Support-Meldung angelegt.+
Yesterday I search the internet for a note, but I didn't find one. So I'am happy now.
But now the next problem occurs. My next issue is about the SLD. The system cannot get the data from the satellites. I'am not sure, but I think our SLD isn't perfectly configuried. Do you have an "How To" or something like that?
regards
marc

Support Desk Message Creation in SOLUTION MANAGER through External Emails

Hello Experts,
 I am a ABAP Developer , as mentioned in subject, my part is to Create support desk message in solution manager,through external Emails like outlook Express . To do this task i am in need of more information about some componenets which are used in solution manager support desk Message.
 My Doubts are,
1) What is the use of Ibasecomponent in Message Creation?
2) What if the ibasecomponent is mentioned as a defaut value ' 24 ' ( i.e is the ibasecomponent for solution manager - support desk ) ?
3) To track the system from which the message is created , is ibase required or the SAP component will give those information?
 If anyone has already worked with this subject, please give me some suggestions ASAP.
Thanks in Advance,
Mohana

Hello Mohana,
Let see if I can explain this well:
1) What is the use of Ibasecomponent in Message Creation?
When you define a Solution in the SOLMAN, you need to update your Ibase
Edit->Initial Data transfer for Ibase
This create a tree structure in the ibase IB52, as you can see in the attachment.
You get a componet number for SID-Client
You can configure the SOLMAN in a way that when a message arrives from
<System ID> <Installation Number> <Client> <User Name>
this is what solman knows from a message comming from a satellite, them you
know directly from which component/ibase the message has been received.
This is important data, the component/ibase, for reporting issue, for assigning this component to a sold-to-party (being in IB52, left tree, select a system and go to Goto->Partner you can assign a Sold-to party BP there for example)
2) What if the ibasecomponent is mentioned as a defaut value ' 24 '
By default the SOLMAN system has a Intalled base 01 already created for being used and maintained "automatically":
being in dswp, solution : Edit->Initial Data transfer for Ibase
If not you msut maintain the ibase manually from IB52, this is also possible.
The Ibase 01 is a prconfigured iBase for being used for the SOLMAN application.
Tink that the SOLMAN system is built up a CRM system, so the IBase is CRM matter. SOLMAN is only using some CRM applications to build the Service Desk scenario for example.
I3) To track the system from which the message is created , is ibase required or the SAP component will give those information?
Ibase is required
Hope this helps,
Dolores

SAP Attributes of Service Desk in Solution Manager

Dear all,
We are using the Service Desk functionality of Solution Manager to create issues out of the satellite systems directly in SolMan.
When opening a SolMan msg, navigating to 'Transaction Data > SAP Attributes', you have a field called 'System Type'.
I'm trying to find out how this field is filled out. I suppose this is done by the satellite system at the moment the msg is send to SolMan.
Already did some investigation:
- in the satellite systems:
t-code: USMM - System Type
t-code: SCC4 - Client Role
- in SolMan:
t-code: IB52 - no system type attribute found in the IBase
We have one system where none of the system type is set to 'Production', but when raising an issue in SolMan system type 'Production' is choosen.
Anybody an idea where this info comes from?
Thanks a lot!
Roel

Hi Roel,
quick answer since I have been trying to find some answers about Service Desk myself.
Anyway, I would double check again the satellite system and make sure that the client you have logged on is the same like in the service desk message. Usually, the IBase number the last 3 digits will tell you, which client it was created in. There might be one client configured in SCC4 as productive client even though it is not a production server. I have that kind of situation with one customer environment. Once the sap router is up and running for this customer system, then I will see, if this actually does happen.
Otherwise, I would not have any ideas either.
Your welcome,
Markus

1 Solution Manager System - Mulitple Companies.

Hi All,
Please provide some input/information regarding one Solution Manager system with multiple companies.
Situation:
We currently have one Solution Manager system(SMP) that belongs to a main company. Under this company there are 5 separate companies. Each company including the main company has multiple SAP systems with different landscapes. Main Company - ECC6 landscape, BI 7.0, Portal, XI and HR Landscape. All other companies have their unique systems/landscapes with their own support personnel.
Issues at hand:
How do we setup Solution Manager to run multiple companies? Do we setup different Solution Landscapes and add each company systems to their own landscapes. How does this effect Service Desk/Charm setup ?
We also want to implement Service Desk / Charm / EWA and all the other functionality that is available in Solution Manager. Is there any advise on this issue and what are the potential pitfalls.
Is it possible to be setup multiple clients and have each company work in its own client.
I would appreciate any advice and information that will assist us with making an informed decision on the best way to proceed with this. I have done research and cannot find any information pertaining to this type of scenario. I'm hoping there are other customers that have a similar problem/issue.
Thanks and regards,
Ricky

Dear Ricky,
You are right. You sould create multiple solutions u2013 a solution for each company. Each solution comprises the landscape (systems) relevant.
I don't think setting up multiple clients and have each company work on its own client is a good idea. The solution manager supports monitoring and managing multipal solutions. By creating multiple clients you are loosing the advantage of one-point-of-entery. Besides, a lot of the customization in the SolMan is cross client.
Regarding the service desk:
You may create a sold-to-party business partner for each of the companies (transaction BP) and assign each sold-to-party only to the relevant system/iBase in transaction IB52. This will allow you to screen the messages in the service desk by a sold-to-party/company.
Regarding the EWA:
The EWA monitors the systems in the solutions. You may have as many solutions as you want.
Regarding the Charm:
Sorry, we didnu2019t implement it yetu2026 you should keep asking abour that.
If you would want to use Business Process Monitoring - this is solution based, so I don't see any problem there.
Hope it was helpful.
Good luck!
Adi Skutelsky

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.

Solution Manager 4.0 Optimizer

During the course configuring the Solution Manager 4.0 Optimizer from the Change Management --> Support Packages Stack; I got this error "Current IBase component is not in an active IBase".
What & where I need to config / assign the iBase component to an active iBase?
Thank you in advance for your helps...
FN

Hi Sri,
Thank you for the hint...but where within the solman landscape that I can "ACTIVATE" the iBase?
Thank you again...
Regards,
FN

IBASE in solution manager

Similar Messages

Maybe you are looking for