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

Similar Messages

Minimum SP level required in satellite system R/3 4.7E

Hi all,
In my landscape i am going to configure change request management. I know its possible to configure but here my doubt is that what is the minimum level required in satellite systems. Server Details are Solman7.0 level SP11 and satellite systems are R/3 4.7EE --> ST-PI 2005_1_700 13 and ST-A/PI leval is 0j1_crm500 0
Sugesstions are highly appreciated.
Regards
Madhu

Please check note 907768 - General note for Change Request Management ST 400
Markus

Move TPs in satellite system after smsy & rfc

Dear All,
We have a issue here. we did the confgn of tms & generated the rfc as well. we havent created a project yet in solman. this is charm implementation. After doing thse tms & rfc work, we tried to move the tps in satellite system from qlty to prd. we r not able to see the target client name in qlty & system is not allowing us to move the tps as well. Can anyone help us in this ?
regds,
Kallu

Hi,
1. Could you please check all the required systems are assigned to the tranport domain and the domain is consistent? You may check this by logging into the domain. there should not be any warning in the STMS.
2. Have you given permission to move TR in client settings, SCC4?
Rajeev

SOLMAN EHP1 - anyone can create support message in Satellite System's Help?

Hi,
I just curios that why everyone can create support message in satellite system-> help -> create support message?
I tested with restricted profile user and without role SAP_SUPPDESK_CREATE, NO BP created but he still manage to create support message???? Any idea??
Also, same goes to any user can process ticket in SOLMAN with no BP-Employee role and SAP_SUPPDESK_* roles assigned.
Your kind input is very much appreciated.
Thanks,
Nicholas Chang

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.
The user entered in the RFC details probably has the authorization to create Support desk messages.
Regards
Amit

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

Checking system connected to SOLMAN or Not from Satellite system

Hi ,
How to check system connected to SOLMAN or Not from Satellite system.
thanks in advance..
Rgds,
BBR.

All connections via SM and satellite system are view RFCs.
In SM, you will have 3-4 RFCs trusted/read/ etc pointing to satellite sm.
in satellite, you will have one RFC to SM called back RFC generally with name - Solution Manager created during SMSY configuration in SM.
Do a test for Connection/Authorization etc for all the RFC's which if fine then the connection is good..
Regards,
SS.

Service desk status in satellite system.

Hi All,
I have configured service desk in solution manager. I am able to create message from satellite system (Help->create support message). But i am not able to figure it out, how to check the status of my message from the satellite system (i.e. any transaction code is there).
Thanks,
Rohan

>
Rohanravindra Hardikar wrote:
> How to go to "Incident Management" through SAP solution manager.
See some general information on Work Center here
[SAP Support Portal - Work Center|http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000707406&]
It's available as of ST 400 SP15.
Run transaction solman_workcenter to access Work Center.
Required configuration steps are documented in IMG (transaction spro). See activities under node "Cross-Scenario Settings -> Work Center"
See also section "Work Center Navigation Roles" in Security Guide.
Best regards,
Ruediger

Satellite Systems - How far back can SolMan 4.0 go ?

Hi,
Can you please let me know the SAP Note which talks about the BASIS Release requirements of Satellite Systems, in order for SolMan 4.0 to be connected to them ?
I came across SAP Note 661949 - Solution Manager Component systems with Basis Release 4.6B which mentions a few facts, but I am still not clear.
In other words, if someone would like to make use of SolMan to connect to very old SAP systems (3.1H or I for instance), is it still feasible? If so, does it go by Scenario of SolMan to be implemented.
Is it a case where, for Implementation Scenario, Basis Release 4.6B is required whereas for Service Desk, it can go lower (?)
Any pointers will be gratefully acknowledged.
Thanks.
Srini

Hi Ruben,
Thanks for your reply. I was already in that section, somehow, this information was not very clear from Config Guides since it differed by Scenario.
It confirms the data I have tried to compile from a Config Guide PDF and SAP Note:
Satellite System's Requirements for Implementation scenario, using SolMan 4.0, as of SP15
Satellite Systems (Basis Release)
4.6C: SAP_BASIS and SAP_ABA: SP 56 (SP 58, if ChaRM is required)
4.6D: SAP_BASIS and SAP_ABA: SP 29 (SP42, -
6.10: SAP_BASIS and SAP_ABA: SP 18 (SP43, -
6.20: SAP_BASIS and SAP_ABA: SP 00 (SP51, -
6.40: SAP_BASIS and SAP_ABA: SP 00 (SP12, -
7.00: SAP_BASIS and SAP_ABA: SP 00 (SP06, -
Also, for those with SolMan SP below 15, SAP Note 907768 mentions a few other SP levels required in Satellite Systems.
Many thanks again.
Best wishes,
Srini

Authorization Required for RFC user in R/3-APO system.

Could you please help regarding one authorization issue. I want to know the authorization required for one RFC user. Now this RFC user used for RFC connection of SAP R/3 - SAP APO system. user type is given dialog type and SAP_ALL profile has been given to this user id. Now I have to remove SAP_ALL from this user id in R/3 and APO system and provide the required the authorization in R/3 and APO system.
Regard
Auroshikha

The RFC authorisation depends completely on what the user is doing (ALEREMOTE?). We can't tell you what RFC auths your connection requires.
There is a guide to doing this here: https://wiki.sdn.sap.com/wiki/display/Security/BestPractice-HowtoanalyzeandsecureRFC+connections

Roles required to create support message from satellite system

Hi Team,
I am trying to create support message from satellite system. i have assigned S_RFC and S_RFCACL to the Zrole. Apart from that, is there any other roles to be assined in satelite system to create support message?
Regards
Kumar

I think that's it.
Of course they roles in the central system too: SAP_SV_FDB_NOTIF_BC_ADMIN and SAP_SUPPDESK_CREATE (or copies thereof).
Regards,
Sean

Error while creating a support message in satellite system

Hi,
I am facing an error while sending a support message to solman form the satellite system
(( Error Description : Error in Local Message System: Error when opening
an RFC connection Message was Not Created ))
1) I gone through various threads and set the required authorizations like
SAP_SUPPDESK_CREATE and
SAP_SV_FDB_NOTIF_BC_ADMIN ,
SAP_SUPPDESK_ADMIN
for the user in the solman .
2) I checked the RFC connection and it is working fine.
Anyone pls help me to resolve this issue

hi rohit,
thanks for u r immmediate response
do i have to assign the roles to the user in the satellite system or the solman.
some roles in those 4 roles are not in the satellite system.
thanks
Rahul

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

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

Create single-roles in satellite-system

Hello everybody,
I want to create Single-role´s in a satellite-system over RFC but the Fm´s in the Functiongroup PRGN are not remotable. Is there an alternative way to create these single-roles in a satellite-system? Up-/download and transport function isn't a alternative because my requirement is to create the single-roles an from excel-import. I considered that one way could be to copy the roles in the satellite.
Regards,
Christian

You can create an RFC-able FM that is a wrapper for that FM.
Neal

Early watch alert task not created on satellite system via SDCCN

The task about EWA is not created on satellite system via SDCCN.
The RFC back was created on Solution Manager and the user assigned to it has the following profiles:
S_CUS_CMP (SAP_S_CUS_CMP) Read data
S_CMSREG (SAP_S_CSMREG) -> Central system repository data
S_BDLSM_READ (SAP_S_BDLSM_READ) -> SDCCN data
SAP_SV_FDB_NOTIF_BC_ADMIN -> Service Desk messages
SAP_SUPPDESK_CREATE -> Service Desk messages
I have checked the RFC authorizations and Connection nothing is wrong.
Do you folks have any clue about that issue?
tks,
Re

Hello,
Not really much information to go on. The Maintenance package tasks is intended to schedule the Refresh defintion and services SDCCN tasks. So is this tasks scheduled? Is this taks gettign any errors/warnings in the logs?
The EWA task is created when the refresh service task runs and gets a list of the serivce sessions that need to be
populated.
You can run a refresh services task to see if there are any sessions to pull. If ther are no sessions, it could be a problem in SMSY defintions for the system. if the system is not delared 100% correctly in SMSY you will not get an EWA session populated.
In DSWP in the SOlution is the EWA for the SID red flagged? If so this means the data still needs to be colelcted from the satellite/managed sysetm. Does the installation number of the SID match the one in SMSY? If not you willnot get any sessions.
Is the refresh session actually using the *BACK RFC to the intended Solution Manager ssystem and is it defined as the master in SDCCN RFC destinations?
If you go to SE37 and run TH_SERVER and specify the SM_SIDCLNTnnn_BACK RFC, does it pull the server list?
If so your back RFC is functioning properly and a logon is successful.
Are the service defintions being replaced successfully when the Maintenance Package runs? Are they replaced when an upgrade was done? It could be the service defintions need to be replaced.
But really more information is needed. I have covered off just some of the issues possible.
Regards,
Paul

Authorization Required in satellite system to create RFC

Similar Messages

Maybe you are looking for