SAP Backend Communication S-User – Required Authorizations for Solution Manager 7.2
Solution Manager executes a variety of activities that require a connection to the SAP Support website. Including opening OSS Incidents and updating maintenance licenses on managed systems. When executing the guided procedure System Preparation within SOLMAN_SETUP you must supply solution manager with an S-user that will be used for these activities. This is done in step 3.1 RFC Connectivity, screen shot below for reference.
Due to this I always recommend that a client creates a user just for solution manager. If the user is shared with anything else and the password is changed, the functionality within solution manager that relies on this S-User will be broken. This requirement always leads to the question, what authorization does the user require.
Below is a list of the authorization required at a minimum for solution manager to function properly with the SAP Back-end.
- Report an Incident
- Close Incidents
- Send Incidents to SAP
- Display System Data
- Edit My Login Data
- Edit All Login Data
- Edit System Data
- Manage Installations
- Request License Key
This is definitely really a brilliant publish, many gratitude for telling Great luck I found out about this certain website. obat penghancur batu ginjal
I really enjoy simply reading all your weblogs. Simply wanted to inform you that you have people like me who appreciate your work. Obviously a great publish. The information that you have provided is truly very beneficial. obat kanker serviks
Just keep write what you are excited about, and the visitors will come to your blog. obat herbal leukimia
Thanks for the post. I am having some issues with S-User trying to download for RCD. There seems to be 3 S-userid required in Solman 7.2
1) HUB Technical user 2.) Backend User 3) Communication User
I thought the backend user does not require any authorizations? I think there is a comment in Solman_Setup.
What is the Communication user used for and what authorizations does it need to have?
For most communication technical S-User is enough now (Which is great, because you do not have to take care of roles etc) and you can put it everywhere.
Technical S-user should be enough even for NWDC (this feature should be undergoing testing), so RCD will be covered by this as well.