on 06-17-2008 2:46 AM
Hi there,
We are implementing service desk and we want use this SOLUTION Manager Service desk for all NON-SAP Components as like. Like Network, tech-support, windows support, user locks/unlock? And etcu2026., when you go to t-code notif_create to create the message, you need to specify the components, as you know; now it has only SAP Components and sub-components of sap. Where does these being maintained, what tables and etc? Because I want to add all NON-SAP Components, so when I create the message, we can use that as components?
Can someone please?
Thanks in Advance!
Kumar
Kumar,
I would recommend adding a non SAP "component" as another iBase rather than adding it to the component list. Any changes to the component list will be overwritten if you ever download an updated component list from SAP by using the Fetch SAP Components feature.
regards,
Jason
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kumar,
You can group them in IB52, but they won't be grouped in the ibase drop down when you create a ticket.
In IB52, highlight SOL_MAN_DATA_REP on the left hand side tree and type Non-SAP systems on the text tab on the right hand side. Click Save.
Highlight Non-SAP systems on the left hand side tree and type Network in the text tab on the right hand side. The identification should be NSI 0000000000 (a dummy value). Click Save.
Highlight Network on the left hand side and add Lan/Wan and NT Lock and Unlock to the text tab on the right hand side. The identifications should be NSI 000000000 001 and NSI 0000000000 002. The client will make it unique and allow you to later limit which ibases people can create tickets for by adding them to the identification tab.
regards,
Jason
Thank you so much Jason.
Can I assume now. When I go to create message via NOTIF_CREATE, if I choose the Network as my iBase system, and another screen will pop up to ask me choose components between "Lock/Unlock or Wan/Lan"? , because components field is also mandatory. It has ONLY SAP Components.
Let me know about this please.
Thanks
Kumar
Thank you so much Jason. You really did clear my doubts. I got one final questions.
Now, with choosing SAP Components we can send e-mail to one BIG group. For an example. If I choose "BC" Basis as SAP Components and if I set up Rules " BC* for SAP Components" and Setup Organizational level chart with all Users in BC, it sends e-mail out to everyone that in the groupd BC. with this iBase I guess we loose this functionalities for NON-SAP sutffs? is this correct? or there is options we can set in iBase (IB52) to send an e-mail out to all Network group?
Please confirm me this as well.
I have rewarded points for you here as well.
Thanks
Kumar
Kumar,
you can still use the SAP components for Non-SAP systems if you want. For instance, you could still select BC.
However a better way would be to have a rule based on iBase. For instance you could have a rule that forwards messages to the BC team when the ibase equals NSI 0000000000 001 and NSI 0000000000 001. I would put a higher priority on these than the rules that use SAP Component.
regards,
Jason
Hi,
you might have a look at DSWPCSNCOMPTXT
/cheers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.