Downtime Management Notification Users in Satellite Systems

Hi folks,
I'm starting to set up Solution Manager Downtime Management. It's kind of cumbersome but I realize it is new functionality and will get better over time. I'm trying to set up the notification users but when I select "Notification Settings" of a system then "Add Internal Recipients" then "from System Users" it only pulls in users in client 000 of the satellite system. Obviously we don't have our users in 000 so how do I make DT Management look in client 100 for the list of users? I know I can add business partners but don't want that right now. I've already looked through the setup guide in Work Centers in SAP Solution Manager [original link is broken] and notes 1129385 "Downtime Management with SAP Solution Manager: FAQ" & 1129052 "Downtime Management with SAP Solution Manager: a brief guide" so don't need links to those. Any help is appreciated, thanks,
David

Hi
what is your solutionn manager version?
as per the note 1129385, from SP17, downtime management sends notication to all the system users.
again review here [Notifying Users About Scheduled Downtime |http://help.sap.com/saphelp_sm70ehp1_sp23/helpdata/en/6b/575f97df0b47808ead4c1f5e2df172/frameset.htm]
regarding client, SOST(Email,sms) settings also client specific.
Have you configured Email settings on client 100 too? if not ... please configure and try.
Thanks,
Jansi

Similar Messages

Multiple Solution Manager Connectivity to 1 Satellite system

HI..
I have a requirement. There is already an existing landscape with solution manager ECC, BI etc. The solution manager is configured for EWA, Maintenance optimizer etc. I now have to install a new solution manager and connect it to the same set of satellite systems so that I receive the EWA, configure MOPZ again. Will this create any kind of a problem and technically how can we do it? I have two ideas for this scenario
1. Connect the new solution manager to the same satellite systems and do configuration as normal. Got this idea from the below link but not sure how it will work.
Re: send EWA report to more than one solution manager
2. Is it possible to push data from the existing solution manager to the new solution manager?
Would highly appreciate technical suggestions. Thx in advance for your help.

Hello,
You need the SMD Agent in order to have ABAP data going to the Solution Manager. Some RFCs are established directly from Managed System to the Solution Manager to extract E2E Change Analysis, Exception Analysis. The Workload Analysis and Host Information (SAPOSCOL) is extracted from WIly EM
Having that said, you can imagine that you cannot have only RFCs and you cannot have only data extracted from WIly EM.
I suggest you to take a look at the FWK Administration in the solman_workcenter, choose the Managed System tab, and start looking into the details of each extractor. Some have an RFC destionation, others have SOLMANDIAG. The SOLMANDIAG are coming from the Solution Manager Java stack, which is responsible to poll the Wily EM.
The reason you need two SMD Agents is because the SMD Agent connects to the ABAP stack, retrieves data, and then connects to the Wily Enterprise Manager. The Solution Manager polls data from the Wily EM and persists it in the BW.
The SMD Agent doesn't support connecting to two Wily EMs at the same time.
So it is required to have TWO SMD agents polling data from the ABAP stack, at the same time, one of them reporting to one Wily EM, and the other reporting to the other Wily EM.
Each solution manager has it's own Wily EM, and it will pull the ABAP data from the Wily EM.
It is not possible to make the two Solution Manager's connect to one Wily EM, since the setup framework needs to see a SMD Agent available to run the setup wizard and to create the destinations. So each Solution Manager needs a SMD Agent running in the physical host.
I hope it is clear for you.
Best regards,
Guilherme
Edited by: Guilherme Balbinot on Feb 6, 2012 9:44 PM
Edited by: Guilherme Balbinot on Feb 6, 2012 9:49 PM

To view the list of users in Satellite Systems from Solman

Dear Friends,
We wish to view the list of users in a satellite system (say ECC5.0) from solution manager 4.0, can anyone help us to find the same.
Regards
Senthil

Hello Senthil,
You mean the list of BP associated to the satellite users already created? If this is the case
in DSWP, choose a Solution that has your satellite as system and go to Edit->BP
Add the satellite system to the list and if I don´t remember wrong you will get the
BP for the satellite users already created in the righ chart.
Sory if I don´t get the correct question?
Best regards,
Dolores

RFC User for satellite systems

Hello Gurus,
I just wanted to ask about one issue. We are a SAP partner and using Solution Manager in VARs scenario. There are many systems of our customers connected to our Solution Manager..
Now I want to ask about RFC user(s). As I see, in our Solution Manager there are many users(communications type C) with Synthax SOLMAN<system id> or something like that. It means basically, that we have for every particular customerS system one SOLMAN user for RFC(cust_scout) in our Solution Manager. My question is if we can replace all of these users with only one RFC user for all the systems and customers?
Many thanks in advance for your help
Miloslav Pudil
IDS Scheer
Prague
Czech Republic

>
Miloslav Pudil wrote:
> I just wanted to ask about one issue. We are a SAP partner and using Solution Manager in VARs scenario. There are many systems of our customers connected to our Solution Manager..
> Now I want to ask about RFC user(s). As I see, in our Solution Manager there are many users(communications type C) with Synthax SOLMAN<system id> or something like that. It means basically, that we have for every particular customerS system one SOLMAN user for RFC(cust_scout) in our Solution Manager. My question is if we can replace all of these users with only one RFC user for all the systems and customers?
Hi Miloslav,
Technically, it will work that you define one common RFC user in your SolMan for communication (RFC BACK destination) from all connected managed systems.
BUT, I would never recommend it.
Once a managed system cause issues in your SolMan, you are not able (or at least it's much more difficult) to identify the managed system. Same happens, if a invalid password in the BACK destination leads to a locked user.
My recommendation: Spend the extra effort in creating a user per managed system. Operation will be much easier later.
See also this guide:
[Activating EarlyWatch Alert [EWA] in End Customeru2019s System |http://service.sap.com/~form/sapnet?_SHORTKEY=00200797470000089947&_OBJECT=011000358700000567342009E]
Best regards,
Ruediger

Creating Support Messages from Satellite System without SolMan user account

Hi
We are having some problems with users "creating support message" from our ECC system to SolMan, if the user does not have a user account in Solution Manager.
It is not correct, that users from Satellite systems can create support messages from these systems, without the user having an account in Solution Manager? And that the user is identified by the business partner for the user, that must exist in the Solution Manager system ?
We have set up the RFC for the supportmessages between SolMan and the ECC system as trusted RFC, with the "Current user" as the user, but how should this be set up, if the user does not have an account in the Solution Manager system. If we enter a user with the right authorizations in the RFC, will the messages that come through not just appear as created by that user, instead of the ECC user and corresponding business partner ?
Regards
Lars

Hi,
you can use the use the user for the RFC-Connection in that case. I have customizied a similar scenario. In my scenario the System from which the message was created, is the business partner (SOLD-TO-PARTY). For that you have to create a communication user (i.e SOLMAN<SYSID>). In TA SM59 in the satellite-system you assign this user for the connection. (Don't forget to assign the user to the role "SAP_SV_FDB_NOTIF_BC_ADMIN"). Now, it schould be possible to create messages from the satellite system to the solution manager. Additionally you should create business-partner for each user of the satellite system, by using TA DSWP>EDIT>CREATE BUSINESS PARTNER.
With this TA, it is easy to create BP for each satellite system.
Best regards
Marc

SMSY - Generated RFC between solution mananger and a satellite system

Hi gurus,
I would like to ask you some things about configuration of SMSY - create systems and their RFC´s between solution manager (SSM) and a satellite system (for instance the DEV system SD3 (in solution manager system)
But my problem is which of these users I must use in each RFC???
Because until this moment I have been doing without knowing very well where I must put that users in those RFC´s!!!!! And I don´t know if I have been doing well!! You understand ?!? :- /
Can somebody give me a simple explanation about this... Which user I have to put (due to the authorizations) in those RFC connections?!
And other thing, if you don´t mind take a look to other question I ask yesterday which is related with this doubt:
Help me please... :- /
Thanks in advance
Best regards,
João Dimas

Hi Joao,
As I understand, the respective RFCs and users are created autmatically when the RFCs are
generated for a satellite system in SMSY.
Furthermore, the Z roles and profiles for each of these users are also created/generated during the
generation procedure. The roles/authorization assigned to each of the generated user are as mentioned
in the below link:
http://help.sap.com/saphelp_smehp1/helpdata/en/48/647e3ddf01910fe10000000a114084/frameset.htm
The administration/customizor specific authorization objects are also provided. As you mentioned the
above helps understand the roles/authorizations required for specific user with regards to an RFC.
Apart from this, all the actual creation, generation and assignment is done - thanks to the automated
setup in SMSY
Also I suppose the above link should help you decide the auhtorization objects requested by you
in the other thread.
Hope this helps.
Regards,
Srikishan

Authorization Required in satellite system to create RFC

Dears,
In Solman 7.0 tcode SMSY i am adding satellite system(ECC6).As while creating RFCs
SM_<SID>CLNT<client>_READ
SM_<SID>CLNT<client>_TRUSTED
SM_<SID>CLNT<client>_TMW
in SMSY it askes for three times satellite system user name and password.
Now Issue is that with what authorization i should enter in satellite system so that RFCs can be created successfully as SAP_ALL can be assigned due to policy.I gave almost all basis tcodes to my user in satellite system but still RFC are generating error.
Please suggest.
Deepak

Hi,
You need to have these authorization objects. Along with your BASIS authorization add the following objects.
S_RFC
S_RFCACL
This should solve your problem.
Feel free to revert back.
--Ragu

Create Support Message from satellite system

Hi, when I create a ticket using "Help - Create support Message" the parameter SY-UNAME is not passed to Service Desk
in other word, the message is created but the field "Reported by" is not filled.
if I want to display the entire message in the form, before saving, I can see that this value is correct...
SY-SYSID             DE1
SY-MANDT             300
SY-UNAME             SOLMAN
SY-DATUM             20080410
etc.
Any suggestion ?
Regards,
Nacho.

Hi,
1) Under identification tab in external BP no. put details as
<Server short name>space<client>space<search term
(which you have maintained in address tab or employee no.
of that user in satellite system)>
2) In ID type put CRM001
3) Under identification put details as <Server short
name>space<installation no.>space<client>space<search
term (which you have maintained in address tab or
employee no. of that user in satellite system)>
4)Go to trns. BP>select BP role as "Employee"> Indentification tab--> Maintain user name same as user id of employee in satellite system or serch term you maintained while creating BP.
Try this. Reward the points for useful answer.
Regards,
Niks

Connection From Satellite System to Solution Manager for key users

Hi All,
Can anybody suggest which RFC connection/destination should be maintained in BCOS_CUST table under satellite system to connect to Solution Manager.
1. SM_SSMCLNT010_TRUSTED
2. SM_SSMCLNT010_BACK
I don't want user to Login to solution manager while creating a support message. They should create a support messsage seamlessly from satellite system.
Any help is greatly appreciated.
Thanks...

Thakur,
Sorry for the cryptic answer back there - read it myself and it didn't make much sense to me either so here we go with the seamless way to allow users to create service messages.
There are 2 ways to do this - 1 way is to use a connection like the 'BACK' connection but if you do this - all user tickets entered will have the username of the 'BACK' connection logon id as the message creator. The other way is to use the trusted connection so the userid of the person logging the message is transfered with the created ticket.
I will assume that you want to preserve the unique userid and use trusted connections. So here we go:
Step 1 - Go into BCOS_CUST on the Satelite and put in your TRUSTED RFC Connection as the detination for the Service Messages - either use the one that Solman created when generating or make your own ABAP Trusted Connection.
Step 2 - All users in Satelite and in Solution Manager need to have Authority Object S_RFCACL assigned to their userid's so they can use the Trusted RFC Connection (this is not in SAP_ALL or SAP_NEW).
Step 3 - All users that will use this method of creating service tickets need both a userID and a BP with the respective system keys to allow them to enter tickets for those Satelites.
That is all there is to it assuming that all issues with Trusted Connections have been worked through already (test this in SM59 by going to your 'TRUSTED' connection on the Satelite and execute the RemoteLogon button - you should be sent to the Solution Manager with out having to logon).
If this answers your question, please set this message to answered.
Edited by: David Milliken on Jan 25, 2008 1:55 AM

How user trace the message created in Satellite System

HI All,
I'm using Servide Desk in my company. Just wondering how user can trace the progress of the message created where email notification is not configured.
Remember when user send/save the message, there's a message number created. Just wonder any center/ transaction code user can trace the progress and have a visible view on the message ON THE SATELLITE System, not in SOLMAN.
Thanks,
NIcholas Chang

>
Nicholas Chang wrote:
> Hi All,
>
> What standard F4 help screen should i modify and from where should i start? Could you please enlighten me on what function or program that this F4 help screen bind to? I need to know the function/program in order for my abaper to work on this.
>
> Also, i just wondering is every user able to create message in Satellite System under Help -> Create Message? According to the SOLMAN Security Guide, it mention user with role SAP_SUPPDESK_CREATE are able to create message but i've and created and tested with a restricted profile user without SAP_SUPPDESK_CREATE role, and it still manage to create message.
>
> I've completed the SOLMAN SD setup and currently tryin to fine tune it.
>
> Your help is very much appreciated.
>
> Thanks!
> Nicholas
Hi Nicholas
If you are using a "Named" user instead of the Trusted Relationship in the RFC maintained in BCOS_CUST for entry OSS_MSG then this is quite possible. In this case the "Named" user will be used to call the interface to create message and the calling user ie the end user creating the ticket will only be used as "Reporter" of the message.
Regards
Amit

Create user both in the satellite system and in solman

Hi
I wonder if I need to open all my user's that are in the satellite system (ECC) in the solution manager for the purpose of create support message or I can only create them as BP?
If I don't need to open them, What is the proper way to configure the RFC?
Best regard's
Lior Grinberg

Hi,
in a normal service desk scenario you do not neet to create users in Sol Man. You just create business partners. If you want the users to logon to Sol Man and edit a document then they also need a real user there (linked via BP - employee):
For creating messages from satellite system you usually maintain RFC destinations from Sol Man (SMSY) to the connected systems. Then you use the generated *_BACK destination in your satellite system and add it to table BCOS_CUST.
All these steps and many more are described in IMG in Solution Manager.
Regards

System Monitoring for Satellite System in Solution Manager

Hi,
I configured satellite system in solution manager through SMSY,and i created solution in dswp.I want to configure system monitoring through ccms agent,how to install ccms agent,how to configure system monitoring for satellite system in solution manager .Please guide me.
Thanku

Hi,
In Solution manager I did below steps. :
1) Activated background dispatching in Rz21 (Client : 000).
2) Created CSMREG user (In RZ21)
3) Generated the configuration file for agent (CSMCONF).
I down loaded the ccmagent_35-20001346.sar file.
What are the steps i have to do in satellite system.
Thanku

Notifications user system GUID rather than ID Defined in XML

I've been working on creating, and sealing a set of management packs that anyone could import and use, and I've hit a bit of a snag. There are a number of things in the management pack that seem to be expressed using a system GUID rather than the ID defined
in the management pack. To give an example, inside one of the management packs there is a template named with the ID "Template_2189ec1298d647a5b971c5429e72a04e". When this template is referenced by a notification workflow, the workflow uses
a system GUID to reference it instead. It seems as though, when a management pack is imported, the system creates all of the objects within in, so these system GUIDs are not the same and cannot be predicted. I'm having the same issue with Support Groups and
other things as well.
In the definition of my Notification Channel for example, one of the workflow parameters is the TemplateID the notification should use to sent the alert (Note <Item>):
<WorkflowArrayParameter Name="TemplateIds" Type="string">
<Item>Template_2189ec1298d647a5b971c5429e72a04e</Item>
</WorkflowArrayParameter>
The alert is also dependent on Support group (note the <value>):
<Expression>
<SimpleExpression>
<ValueExpression>
<Property State="Post">$Context/Property[Type='WorkItem!System.WorkItem.Incident']/TierQueue$</Property>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>{cd712f91-a26b-8ff8-133d-36f9f4b40d46}</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
I built my management packs, and tried to move them to a new system, they imported no problems now that I've sealed them, but when I went in and looked the template for the notification channel was blank, and since the management pack is sealed now, I can't
change it. I thought it was odd, so I referenced my XML, and I used this to get the ID of all the templates, and I noted... now they all seem different now that I've imported them into the new system:
foreach ($template in (Get-SCSMObjectTemplate))
echo $template.Id
echo $template.Name
echo $template.Description
I realized, when you import the management pack the first time, it must created GUIDs for all these things... is there a way to within the management pack reference the ID I can define, rather than the system GUID that's impossible to fix? I'm going to look
into writing a script that uses smlets to correct all this information and update the MP once it's been imported the first time, but that seems like a bit of a hack, there must be a way to do this? Anyone find elegant solutions to this problem that didn't
involve writing a fancy installer script for their management packs?

I'll give that a try, I tried just the MP reference and the error it gave complained it expected a GUID in a particular format.
A bunch of them are notifications that notify "affected user" or other internal references, that shouldn't need to change, the ones that go to people, or groups will have to be in an unsealed management pack. Initially, my goal was just to try
to get as much as I could into a few management packs as possible to avoid having a large amount of management packs, more it's just looking like this isn't possible.
I'm looking at breaking things down like this:
Incident Customizations
Incident Customizations Overrides
Service Request Customizations
Service Request Customizations Overrides
Work Item Customizations (storing some things common to all work items, like urgency)
Service Catalog
Notifications
So, my initial hope was to avoid splitting out ROs and SOs, putting any changes that need to be made quickly into the Override MPs. What this means, is that my solution can be implemented, and then customized without making changes to the core MPs directly
in PRD, then I have a promotion process. I dislike changing things in PRD on the fly, and would prefer a solution that forced people to use a promotion process, but it's looking like with Notifications, ROs, and SOs, it's just not possible.
Regardless of whether I'm going to seal this management pack or not, I'd like to avoid manually fixing every single Notification, or anything that references one of these internal GUIDs every time I implement this in a new system, since the possibility is
totally there for the MP name to be used instead, I'm confused why that isn't the default behavior.

No users are shown for Service Desk in SOLMAN for satellite systems

Hello!
I would like to set up the business partners for Service Desk in SAP Solution Manager.
If I choose the solution and execute "Edit --> Create Business partner" for the SAP R/3 4.7 then I get the warning no users are shown under the system.
If I log onto the satellite system and make some changes in su01 or pfcg the situation does not change.
<b>How can this problem be solved?</b>
Thank you very much!
regards
Thom

Thank you very much!
The problem is solved!
Im my case was necessary to apply SAP Note 1055630.
I have assigned the role "SAP_SM_S_USER_GRP" to the user with RFC_READ connection, refreshed the last alert in DSWP and tha is.
regards!
Thom

Solution Manager EWA - cannot create session in satellite system

"Hi,
I want to configure EWA self service using Solman 4.0. I succesfully did the following :
a. Maintained SMSY and create the required trusted RFC connections from SM to satellite system. All connection and authorization passed in SM59. I used SAP_ALL/SDCCN_ALL role and assigned objects S_RFC*.
b. Assigned the system to a logical system.
c. Created the a new solution and activate "Solutions Monitoring > Earlywatch Alert"
d. Activated and maintained required RFC in SDCCN in satallite system.
My problem is that the create EWA alert request (Red Flag with a specific session number ) coulnd be pass to the satelitte system even though all the trusted RFC and authorization is set. When i execute the SESSION_REFRESH in the satellite system, the session is not created.
Did I miss out any steps. Can any one share any help ?
FYI, there is no connection to SAPOSS yet, so i did not manage to run RTCCTOOL completed, but i doubt this is required for EWA self service."
I have the same problem as Solution Manager EWA - cannot create session in satellite system
tried all of solutions, but it does not help... Created the CM (high) for SAP, but get 1 response for 1 week from them:(

Dear Sapbcer,
Have you tried the following option :
Execute SMSY and from the Server entry Execute the "Read System Data Remote" option in change mode.
Save the data captured and then try using Refresh Session Task from SDCCN of the satellite system. Do select the RFC for Solution Manager while performing this task.
Hope this helps.
Regards
Amit

Downtime Management Notification Users in Satellite Systems

Similar Messages

Maybe you are looking for